cancel
Showing results for 
Search instead for 
Did you mean: 

EAServer6.3.1 JMS Issue(org.omg.CORBA.MARSHAL)

Former Member
0 Kudos

Hi,

We have window\web application recently configured and running  on EAS6 & PB 12.5.2.

As a part of configuration we have configured JMS for component logging and other mail services.

At some point of time where there are not much components run for JMS, the logging goes well but when there are lot more components are running through JMS the service fails to log\print logs on separate log files configured .i.e JMS is not responding properly and I could see some repeated errors in the server log file(stated below).

I googled first and found a similar issue (Corba Marshal - message size exceeded error - sybase.easerver) faced by someone earlier in old EAS <5 and verified all the suggestions and found OK in my setup.

I am more concerned about the error text :org.omg.CORBA.MARSHAL: offset (28) + size (1685290622) > buffer length (76) from which I am not able to make out what is missing is configuration or accessing the components for JMS.

Please let me know if someone has come across any such issue or have some suggestions to try.

Error from server.log

2014-12-30 10:17:36.981 INFO  Thread-34 [SystemException] javax.ejb.EJBException was thrown by method ejb.components.jmsqueue.MessageListener.onMessage(javax.jms.Message)

2014-12-30 10:17:36.981 INFO  Thread-34     javax.ejb.EJBException: nested exception is: org.omg.CORBA.MARSHAL: offset (28) + size (1685290622) > buffer length (76)  vmcid: 0x0  minor code: 0  completed: No

2014-12-30 10:17:36.981 INFO  Thread-34     org.omg.CORBA.MARSHAL: offset (28) + size (1685290622) > buffer length (76)  vmcid: 0x0  minor code: 0  completed: No

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.rmi.iiop.CdrInputStream.alignAndCheck(CdrInputStream.java:298)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.rmi.iiop.CdrInputStream.read_string(CdrInputStream.java:1060)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.rmi.iiop.CdrInputStream_DJC.read_string(CdrInputStream_DJC.java:1776)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.jaguar.server.JaguarStream.getUserException(JaguarStream.java:94)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.jaguar.server.JaguarStream.checkRemoteException(JaguarStream.java:55)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_EJB.onMessage(MessageListener_EJB.java:84)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener.onMessage(MessageListener.java:41)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC.access$001(MessageListener_DJC.java:4)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC$1.invoke(MessageListener_DJC.java:91)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC.onMessage(MessageListener_DJC.java:105)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListener.$runTopicSubscriber(MessageListener.java:637)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListener.$run(MessageListener.java:224)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListenerThread.run(MessageListenerThread.java:31)

2014-12-30 10:17:36.981 INFO  Thread-34         at java.lang.Thread.run(Thread.java:722)

2014-12-30 10:17:36.981 INFO  Thread-34     javax.ejb.EJBException: nested exception is: org.omg.CORBA.MARSHAL: offset (28) + size (1685290622) > buffer length (76)  vmcid: 0x0  minor code: 0  completed: No

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.ExceptionFactory.getEJBException(ExceptionFactory.java:55)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener.onMessage(MessageListener.java:48)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC.access$001(MessageListener_DJC.java:4)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC$1.invoke(MessageListener_DJC.java:91)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)

2014-12-30 10:17:36.981 INFO  Thread-34         at ejb.components.jmsqueue.MessageListener_DJC.onMessage(MessageListener_DJC.java:105)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListener.$runTopicSubscriber(MessageListener.java:637)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListener.$run(MessageListener.java:224)

2014-12-30 10:17:36.981 INFO  Thread-34         at com.sybase.ejb.server.MessageListenerThread.run(MessageListenerThread.java:31)

2014-12-30 10:17:36.981 INFO  Thread-34         at java.lang.Thread.run(Thread.java:722)

Thanks,

Kunal

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kunal,

Have you applied any EBF/patches to EAServer 6.3.1?  If so, what patches.

Thank you.
Beverly Duquette

Former Member
0 Kudos

Hi Beverly,

It has been a year running EAServer6 with build  6.3.1.07 Build 63107.19926.

Last patch I applied was EBF 20852 6.3.1 ESD #6 Support jdk1.7.

Regards,

Kunal

Former Member
0 Kudos

Hi Kunal,

Can you open a support Incident (support.sap.com) as this issue will need more investigation.

Thank you.
Beverly Duquette

Former Member
0 Kudos

Hi Beverly,


It seems this is only the last option now. I am trying couple of  suggestions my own way, if goes well I would be fortunate else will raise case with support team.


Thanks once again for your valuable time .


Thanks,

Kunal