Long running session bean method produces exception

[Pradeep Shekade]

Hello,

I have a stateless session bean (to execute a batch process)which has a method which can take a long time to execute. This bean's method is invoked from a remote client.

Sometimes the method throws a remote exception as follows -

java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:92)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
at com.arc.taskBeans._BigTaskSession_Stub.performTask(Unknown Source)
at com.arc.threadedclient.Task1.run(Task1.java:40)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(IIOPConnection.java:438)
at com.sun.corba.se.internal.iiop.MessageMediator.handleInput(MessageMediator.java:156)
at com.sun.corba.se.internal.iiop.messages.MessageBase.callback(MessageBase.java:707)
at com.sun.corba.se.internal.iiop.MessageMediator.processRequest(MessageMediator.java:142)
at com.sun.corba.se.internal.iiop.IIOPConnection.processInput(IIOPConnection.java:336)
at com.sun.corba.se.internal.iiop.ReaderThread.run(ReaderThread.java:60)

After this exception is thrown at the clients side, the server seems to keep running still executing the method.

What could be the reason for such an exception ?

We are using Weblogic 8.1.

There are no exceptions when the time taken to complete the method is less.

Thank You

[Amit Mujawar]

Have you tried setting the transaction-timeout parameter set to the needs of your applications. Default is 30 seconds I guess. You can set it at the bean level.

[Pradeep Shekade]

Hi,

Yes I did that. I set it to -
<trans-timeout-seconds>1000</trans-timeout-seconds>
Also I have tried higher numbers.

The problem is the same....

[robert berrez]

Hi,

I have also the same problem with a stateful EJB and WebLogic 8.1 sp4 .
My EJB lauches a SQL query on a DB2 table, if this query
elapsed timne exceeds 300s, the exception :

org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
is raised

Adding trans-timeout-seconds in weblogic-ejb-jar with
a higher value than 300s has no effect.

any idea ?, is trans-timeout-seconds really effecting using IIOP with a client packaged with wlclient.jar?

[jirey]

Try to change the
Stuck Thread Max Time in the configuration of WLS server.


Jin