Skip to Content

Java application not starting

Hello Experts,

I am trying to start my first Java application as given in the tutorials by clicking the start button beside my Java application. After pressing the start button, the status is showing as starting. It is not changing to 'Started'. I have kept for more than two hours and it is showing the same status. Can you please tell me what might be wrong?

Regards,

Ritam Banerjee

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Mar 03 at 08:32 PM

    Hi Ritam,

    Do you see anything recorded in the Default Trace files (Logging menu)?

    Are you deploying in which landscape? There were maintenance activities in some landscapes earlier (see https://sapcp.statuspage.io)

    Regards,
    Lucas

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 19 at 05:05 PM

    Hi Ritam,

    Application logs should tell you what's going wrong. Click on the application and navigate to Monitoring -> Logging section.

    Configure the logger to show you all the logs and try to see what's going wrong with the help of logs.

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 19 at 05:41 PM

    Hi Ritam,

    Usually what I do is first test my application on-premise. All you need is to have NEO SDK (corresponding to the runtime you want to use. i.e: Tomcat 8) installed on your machine and the SCP plugins installed on your Eclipse for development. Once you have all these tools in place, create a local server runtime for Tomcat 8 and add your web module to it. This runtime is almost 100% similar to the runtime you will find on SCP. Make sure your application runs on this local server runtime. There are many different requirements for libraries, java versions, etc that make you Java App behave errant on SCP. Once you figure out what the issue is, than you are safe to publish it to the cloud.

    Common mistakes are:

    1) Adding libraries manually onto the lib folder

    2) Not using maven to build your the war file. You could use ant, but maven is more fail-safe in regards to building up an war file and packaging libraries. I really don't see a reason to use ant these days. I have seen huge and complex ant scripts that do exactly the same as maven and still fail to build a safe package because of point (1).

    3) EJB support is not available on some runtime environments and other do have. Have a look at this comprehensive list of Java APIs supported by each runtime.

    4) Supported Java version x Supported Neo SDK

    5) Proper database binding not available for JPA projects

    Regards,
    Ivan

    Add comment
    10|10000 characters needed characters exceeded