TransactionRolledbackException

[Torben Norling]

Hi,
We 're creating a Swingbased admin-client that calls our WAS 3.5.3 server
and we get a strange CORBA_TRANSACTION_ROLLEDBACK error at some occasions
(Yes it works some times). Sometimes a certain method fails for reasons
unknown. We can see in our logs that all SQL related stuff works out ok.

The error log is rather strange, the ###### is actually some unprintable
character...

Has anyone experienced this???

Thanks in advace // Torben Norling - Mind AB

javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: Ê######## code: 0 completed: No
org.omg.CORBA.TRANSACTION_ROLLEDBACK: Ê######## r code: 0 completed: No
at java.lang.RuntimeException.<init>(RuntimeException.java:49)
at org.omg.CORBA.SystemException.<init>(SystemException.java:51)
at
org.omg.CORBA.TRANSACTION_ROLLEDBACK.<init>(TRANSACTION_ROLLEDBACK.java:71)
at
org.omg.CORBA.TRANSACTION_ROLLEDBACK.<init>(TRANSACTION_ROLLEDBACK.java:50)
at java.lang.reflect.Constructor.newInstance(Native Method)
at
com.ibm.CORBA.iiop.ReplyMessage.getSystemException(ReplyMessage.java(Compile
d Code))
at
com.ibm.rmi.iiop.ClientResponseImpl.getSystemException(ClientResponseImpl.ja
va:86)
at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:427)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:250)
at
com.xxxxxxxxxx.admin._AdminServiceSF_Stub.createArea(_AdminServiceSF_Stub.ja
va:526)
at com.xxxxxxxxxx.admin.BLManager.createArea(BLManager.java:343)
at com.xxxxxxxxxx.portfolio.AreaDlg$6.construct(AreaDlg.java:448)
at com.xxxxxxxxxx.admin.SwingWorker$2.run(SwingWorker.java:108)
at java.lang.Thread.run(Thread.java:481)

[Tony Wang]

Hi, Torben.

I got the same problems as you. Let me know if you get this solved.

Thanks

Tony

"Torben Norling" <torben....@mind.com> wrote in message
news:9akf4q$6t6$1...@news.boulder.ibm.com...

[Jacques Desmazieres]

The last time I had such an exception, this was due to a Session Stateless timeout. Actually, my application was handling a
reference on the Remote interface, but the Session bean had timed out. I do not remember if the stack was the same, but i sorted my
problem by increasing the Session bean time out

Hope that will help

Jacques Desmazieres
"Torben Norling" <torben....@mind.com> a écrit dans le message news: 9akf4q$6t6$1...@news.boulder.ibm.com...