Hi,
  The stack trace posted here points to no OpenJPAException. A
OpenJPAException often carry the nested throwables. But in a long JEE stack
who knows who is swallowing whose exceptions? 
   Going by the javadoc of the application-visible
weblogic.transaction.RollbackException, there are two methods of interest
      i) Throwable getNested();
and ii) void superPrintStackTrace(PrintStream). 
   If your application invokes these two methods on the caught exception,
what is the result?

   If you can recurse through getNested().getCause() -- does it let you
reach a OpenJPAException?

 


kurt_cobain wrote:
> 
> Yeah I saw those; but in tracing down into the code, I can see that an
> exception actually never gets thrown. What I get is an exception from
> weblogic like this:
> 
> Feb 23, 2009 5:00:01 PM CST> <Error> <EJB> <BEA-010026> <Exception
> occurred during commit of transaction Name=[EJB
> com....(com...EntityName)],Xid=BEA1-0064C38439F43057A4BD(1453943),Status=Rolled
> back. [Reason=<1.0.0 fatal store error>
> org.apache.openjpa.util.StoreException: The transaction has been rolled
> back.  See the nested exceptions for details on the errors that
> occurred.],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
> begin=0,seconds
> left=30,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=AdminServer),xar=weblogic.jdbc.wrapper.jtsxaresourcei...@866d46,re-Registered
> =
> false),SCInfo[base_domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
> com...sessionBean.methodName(package.Class)],
> weblogic.jdbc=t3://10.200.10.89:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+10.200.10.89:7001+base_domain+t3+,
> XAResources={TagStore, LEGACYHOSTDS, VPS,
> weblogic.jdbc.wrapper.JTSXAResourceImpl,
> CSCUD1},NonXAResources={})],CoordinatorURL=AdminServer+10.200.10.89:7001+base_domain+t3+):
> weblogic.transaction.RollbackException: The transaction has been rolled
> back.  See the nested exceptions for details on the errors that occurred.
>       at
> weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
>       at
> weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:333)
>       at
> weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
>       at
> weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:607)
>       at
> weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:57)
>       at
> weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:427)
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/How-to-get-beter-stacktraces-----tp2375022p2375475.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Reply via email to