• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

One phase commit error on Websphere 4.0

 
Fred Marques
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I have a big trouble on my hands for a time, and i am not bein able to solve it. Althoug I�m using diferent datasources in my project, and all drivers supporting 1pc, sometimes this problem appears:
{2003-07-11 14:05:44.223} [STACK]at *.data.Trace.error(Trace.java:133 - javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: com.ibm.websphere.csi.CSITransactionRolledbackException
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:80)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:443)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:1894)
at com.bkb.framework.smf.EJSRemoteStatelessSMF.execute(EJSRemoteStatelessSMF.java:36)
at com.bkb.framework.smf._SMF_Stub.execute(_SMF_Stub.java:256)
at com.bkb.framework.smf.SMFAccessBean.execute(SMFAccessBean.java:85)
at com.bkb.framework.servlet.ServiceServlet.action(ServiceServlet.java:93)
at com.bkb.framework.servlet.ServiceServlet.doGet(ServiceServlet.java:176)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:721)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:374)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:118)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:154)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:317)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:391)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:274)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:144)
I am only using stateless beans... Stdout.txt file has the following message:
[7/11/03 13:55:25:492 BRT] 31b549 ConnectO W CONM6000W: A resource was unable to process the two phase commit prepare request as it only supports the one phase commit protocol. The datasource was: fwkOracle
Some considerations:
- The application works fine most of times, but rarely the error occurs.
- The error appears in diferent parts of the application(features/EJB�s).
- I am not using 2 datasources in one transaction (not that i know).
I have read some answers for this problem, but none of them match wiyh my case. I hope somebody can help me with that...
Regards...
Fred
 
Louie Barroso
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are currently experiencing the exact same problem. The strange thing is that the application experiencing this issue works in our Production environment but not in our Acceptance and Development environments. Hopefully someone can shed some light on this issue.
 
Diana Iv
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, we have the same problem with application running on WebSphere 4.0 application server. Have you found any solution?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic