JEE app startup

[Former Member]

Hello,

unfortunately I didnt get response to this question in another place so Im looking for someone with JEE engine knowledge:

Global [startInitiallyApp] operation of application [...] failed with errors on server process [8206750].

I can not find any further logs on this error

the developer trace only yields

Global [startInitiallyApp] operation of application [...] finished with errors for [259] ms on server process [8206750] [
>>> without errors <<<] [
>>> without warnings <<<].

Has anyone run into this error before? Im just looking for useful logs, not necessarily a solution

thank you

[Former Member]

Hi,

I had similar symptoms, when after deploy of java schedulers to NW 7.3 AS Java.

After "successful" deployment in NWDS, following error message occurred in server logs without any details:

Global [startInitiallyApp] operation of application [sap.com/...] finished with errors for [145] ms on server process [3189150] [
 >>> without errors <<<] [
 >>> without warnings <<<].

Also no additional error details found, when collecting traces using "Security Troubleshooting Wizard" for location "com.sap.engine.services.deploy.server".

In my case issue was solved by changing application-j2ee-engine.xml file in EAR project (not EJB project!) to following one.

See details in tutorial "Hello job" Editing the application-j2ee-engine.xml -  Using Central Development Services - SAP Library

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xml>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <provider-name>sap.com</provider-name>
  <reference reference-type="hard">
  <reference-target provider-name="sap.com"
  target-type="service">  
           scheduler~runtime  
    </reference-target>
  </reference>
  <modules-additional>
  <module>
  <entry-name>MyEjbProject.jar</entry-name>
  <container-type>scheduler~container</container-type>
  </module>
  </modules-additional>
</application-j2ee-engine>

Regards,

Andrzej

[Former Member]

Hi Stefan,

Did you get any response from SAP? I'm currently getting the exact same error, with no further information on the logs, and I have no idea how to proceed...

Regards

[blanca_serrano]

Hi Alain,

Please, proceed as I suggested to Stefan in my reply above.

I hope this helps oyu.

Regards,

Blanca

[Former Member]

Hi,

I'm not sure which files you've checked already. For this purpose <instance>/work and <instance>/j2ee/log directories are your friends. Try to find the files called

- defaultTrace.trc

- server.log

- dev_server0

- std_server0.out

- applications.0.log

- dev_disp

If you are working on a UNIX-based operating system, you can try to use a recursive find (in the server log folder) to select all files changed today:

find . -mtime +1

The current logs should be among them. In Windows you can use advanced search functionality as well.

By the way: if this is urgent, I would recommend to create a SAP customer message in parallel. Just for the case it's a software bug.

Regards,

Peter

[Former Member]

Hey Peter,

thanks for your input. Unfortunately I didnt find any further information inside the log files. I fear its more a symptom not the cause of the issue. Opened a SAP ticket as well. But it seems kinda strange to me that nobody has come across this so far 🙂

many thanks

[Former Member]

Hi Stefan,

if we assume that logs should contain information but actually they don't, then this leads us to two other topics:

- authorization of sidadm to write to the log directories

- free space in log directory mounts (or volumes) (e.g. /usr/sap/<instance>)

May this be a problem in your environment?

Regards,

Peter

[Former Member]

Hello,

the log files contain other error messages and warnings (not related to the problem, like Login Failed messages and so on). Its just the root cause of the startInitiallyApp error thats missing

best regards

[Former Member]

Hi,

I was afraid this will be the case..

I have to admit, I can't imagine how to proceed here. In your position I would wait for SAP now, hopefully they have more possibilities to analyze.

But it would be interesting what they find out, so please let us know.

Regards,

Peter

[Former Member]

Any reply from SAP on this issue ?

[blanca_serrano]

Hello Stefan,

I saw this error several times and normally this is produced if the AS Java is started in safe mode. Please, check if this is the case. For that:

Please start the configtool and in the menu go to 'File'-> 'Safe Mode'.

Select 'NO' option for 'Safe Mode Enabled' property.  Restart the system.

After that, pleae check if all applications run correctly.

I hope this helps you.

Kind regards,

Blanca

[raktim_banerjee]

Hi Frederik,

Did you find any response? I am getting same error when I am trying to deploy any developed Enterprise Application.

Thanks

Raktim

[Former Member]

Please start the configtool and in the menu go to 'File'-> 'Safe Mode'.
Select 'NO' option for 'Safe Mode Enabled' property.  Restart the system.

Safe Mode "off" did not make any difference here.

The "false error" is still logged and the application is running perfect.

regards

[ErvinSzolke]

Hi Stefan,

I moved this question to the corresponding forum:

http://scn.sap.com/community/netweaver-as

Best REgards,

Ervin