XI 7.0 NW 2004s install - JMS Errors in applications.log & defaultTrace

[Former Member]

We just installed XI 7.0 NW 2004s. The installation of XI 7.0 NW 2004s is a lot simpler than XI 3.0 NW 2004 since the Template installer runs most of the post installation steps.

However, there are a few issues that I am encountering that i did not see with XI 3.0 installations. The installation is on Windows 2003 server and SQL server 2005.

Checking the applications.log file through Visual Administrator LogViewer, I see that the Applications log is filing up every few seconds with the following repeating errors:

Message -

Exception on server occured! Internal error.

Additional Information -

Category : /Applications/JMS

Message ID : 001422B146E800750000070D0000013000041A845FCB659B

Source Name : /Applications/JMS

Thread : SAPEngine_Application_Thread[impl:3]_26

Application :

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : d16ec30026fd11dbb450001422b146e8

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : com.sap.jms.client.session.Session

Resource Bundlename :

Session : 0

Source : /Applications/JMS

ThreadObject : SAPEngine_Application_Thread[impl:3]_26

Transaction :

User : J2EE_GUEST

Message -

Exception on server occured! Cannot write to transaction log TXf48.tx.

Additional Information -

Category : /Applications/JMS

Message ID : 001422B146E800750000070A0000013000041A845FCB4CC8

Source Name : /Applications/JMS

Thread : SAPEngine_Application_Thread[impl:3]_26

Application :

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : d16ec30026fd11dbb450001422b146e8

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : com.sap.jms.client.session.Session

Resource Bundlename :

Session : 0

Source : /Applications/JMS

ThreadObject : SAPEngine_Application_Thread[impl:3]_26

Transaction :

User : J2EE_GUEST

In the defaultTrace.trc file, i see the JMS error too:

Message -

Error From List = javax.jms.JMSException: Internal error.

at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)

at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:1808)

at com.sap.jms.client.session.Session.rollback(Session.java:300)

at com.sap.jms.client.session.Session.close(Session.java:158)

at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)

at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)

at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)

at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:262)

at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:361)

at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Additional Information -

Category : /Version

Message ID : 001422B146E8008B000007340000013000041A847A0F6CB9

Source Name : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession

Thread : SAPEngine_Application_Thread[impl:3]_98

Application :

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : d815880126fe11db9edc001422b146e8

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : /Version

Resource Bundlename :

Session : 0

Source : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession

ThreadObject : SAPEngine_Application_Thread[impl:3]_98

Transaction :

User : J2EE_GUEST

This is filing up both the applications.log and defaultTrace files. I cannot find any information through Service Marketplace. Has anyone encountered this issue? This is new installation - no messages are running on it so I am not sure why there is a JMS error.

Regards,

Jay

[former_member199535 · Accepted solution]

Hi Jay,

The exception means that the JMS Provider is not able to write to the transaction log file upon close of a transacted session. In NW04s, JMS transactions are stored as files on the local file system. The location of the root folder where the transactions are persisted is configured by the JMS service property "transactionStorePath". You can check its value through the Visual Administrator -> Services-> JMS Provider -> Properties. Please check if it contains a correct directory path and that nothing prevents the server from writing to this path - access rights, enough disk space, etc. If there is something wrong with the path, you can change it, save the change and restart the JMS provider service for the change to become effective.

You can also have a closer look at the server trace file: the root cause of the above exception is some other exception, probably I/O one, and it should be logged somewhere in adjacency to the JMS exception.

There is ongoing JMS communication even in a new server installation - in this case (judging from the stack trace) the component that performs this JMS activity is the timeout service.

Hope this helps,

Stoyan

[Former Member · Accepted solution]

Hi Stoyan,

Thanks. That did resolve the continuous flow of errors in the applications.log and defaultTrace.trc.

I did have to restart the J2EE engine for the change to take place though. Stopping and starting the JMS Provider was not enough.

Regards,

Jay