cancel
Showing results for 
Search instead for 
Did you mean: 

XI-J2EE server Down

Former Member
0 Kudos

Hello community,

1) We have installed XI 3.0 SR1 on WAS 6.40 (ABAP + J2EE).

It was working successfully.

We even tried scenarios having IDOC Adapter FILE adpeter.

2) When we created a web service on same server, as part of configuration

transaction "wsadmin" GOTO> administration> gave URL for J2EE Engine.

Web service also worked fine.

3) after this we all developers were getting authentication errors, so restarted the server.

4) But J2EE server didnt come up after that.

5) In SAP MANAGEMENT CONSOLE all instances are started.

6) In SMICM transaction GO TO -->HTTP SERVER -->DISPLAY DATA shows following

Application ServerState

HTTP Application Server Handler

ABAP Server operational = TRUE

J2EE Server configured = true

J2EE HTTP port=

J2EE HTTPS port =

J2EE Server operational = false

Default root access handler = ABAP

URL Prefix Table loaded = TRUE

URL Prefix Table

URL Prefix Virtual Host Case Sensitive Part

/sap/bw/xml/soap/queryview/ :;

/sap/public/formgraphics/ :;

/sap/ :;

7) SM 21 LOG shows

operating system call recv failed

What can be the problem that J2EE server is not coming up?

Can some one give some clue?

Deepti patil

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi

It was the instance profile parameters that was causing problem. J2EE server was not starting, and thereby we could not connect to it in our case. SAP has sent us required instance profile parameters and our problem got resolved after that. Let me know if you need further help.

Nagesh

Former Member
0 Kudos

Hi,

Even i am facing the same problem. should i reset all the password. Pls help to fix the problem.

Thnx and regards,

Anup

Former Member
0 Kudos

Hi Deepti

I am getting exactly same errors but in a different context. Unable to connect to J2EE Visual administrator though, instances are running in SAP Console. Can you tell which database userid/passwords were changed to get over the error messages and startup J2EE server? Thanks in advance.

Nagesh

former_member189324
Contributor
0 Kudos

Hi deepti,

I would suggest the J2ee server logs on the file system. It could be many reasons why your j2ee server is down.

Check the following logs:

1. usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log -


> Applications.log

2. usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log\applications\com.sap.xi----


> xi.log

Thanks

Prasad

Former Member
0 Kudos

Hi Prasad,

in this log usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log -


> Applications.log

we are getting exceptions like

MESSAGE ID: com.sap.aii.utilxi.misc.api.BaseRuntimeException

com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)

com.sap.engine.lib.xml.parser.NestedSAXParseException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)

<b>JMS internal error at ServerClientAdapter! JMS Service is not started!#</b>

<b>2)</b> And the log of usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log\applications\com.sap.xi----


> xi.log

#1.5#000D5671444300310000001400000D800003F39917C59EC8#1112263784562#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######fda79940a1cc11d9a6b4000d56714443#SAPEngine_System_Thread[impl:5]_81##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#465a01a09aa711d98511000d56714443# #1.5#000D56714443003B0000032600000D800003F3991B4C2B18#1112263843703#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0##EXI#IC001669 #3297C768BF734E3C900FBC02C3594ACD#output##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#<null>#

Can you interpret those erros? will be grateful!!

Thanks a lot..

Deepti

former_member189324
Contributor
0 Kudos

Hi Deepti,

1. This error is related to Mapping error.

2. Are you using any JMS Adapter for your scenarios????

Prasad

Former Member
0 Kudos

Hi,

As i had mentioned earlier, both the intances are coming up(J2EE +ABAP).

But we can not login to Visual administrator, DEFAULT login name throws the error as "UNABLE TO LOOK UP CONNECTION TO DEFAULT.http://servername:8101

returned empty list of parameters

And other logins we create throws the error as can not open connection to http://servername:50004

we never used JMS adapter for any scenario.

Configtool is giving error as error in DB connectivity..

Thanks

Deepti

Former Member
0 Kudos

Hey,

I could solve the problem

Database passwords were changed , so Configtool could not logon to database.

We reset all passwords, and now its working fine.

Thanks prasad for all replys

it helped a lot..

Deepti Patil