Transaction timed out with oracle 9i

Hi,
I am working with weblogic6.1.
Sometimes (very seldom) I have a problem which I don't undserstand.
The transaction stops and and after some time I get TimedOutException.
This time it happend in the findByPrimaryKey of a CMP Entity bean.
I have this problem only with Oracle 9i. with oracle8i everything works
fine.
I'm using oracle thin driver (I put oracle12.zip at the begin of weblogic
classpath)
Is this problem of oracle?
Does WLS 6.1 support Oracle9i?
Thanks for any hints
Szymon
stack trace:
javax.ejb.FinderException: Problem in findByPrimaryKey while preparing or
execut
ing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@197155':
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
at
weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:498)
at weblogic.jdbc.jts.Statement.setInt(Statement.java:606)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.setInt(PreparedState
mentImpl.java:104)
at
weblogic.jdbc.rmi.SerialPreparedStatement.setInt(SerialPreparedStatem
ent.java:137)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1531)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1715)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
com.verdisoft.datasource.exception.DataNotFoundException: Object not found:
data
source://private_addressbook/ejbcontact/john1025100151518/12770
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:876)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)

Irene Ho wrote:
Dear all,
When the java application program tries to insert the data (around 300
records). Sometimes, the error occurs as "EJB Exception:
weblogic.transaction.internal.TimedOutException: Transaction timed out after
95 seconds".
When the error occurred, only one java application was running. Furthermore,
I set the JTA-->Timeout Seconds to 30 in the thr the Weblogic console. The
configuration of the server is WebLogic 7.0 with SP2 and Oracle 8.1.7.
Anyone know what happen and how to resolve the problem? The error is due to
the entity bean, Weblogic or Oracle?
Thanks a lot.
IreneOr configuration. You can set your timeout to a different value. It is likely
to be an oracle problem. We don't do anything unnecessary to delay your application
code. You may be able to check the jdbc log or jta log to see when the tx starts and
how long it takes to progress. If you note a delay, you could take a server
thread dump to see what weblogic is doing. Typically it will be waiting for
Oracle to respond from a jdbc call.
Joe

Similar Messages

  • The transaction is no longer active - Transaction timed out after 30 second

    We have an intermittent error here, and I'm a rookie. The error results in a 500 being sent to the customer every 10th-20th POST and only occurs under heavy load. The heavy loading is over the for the day, but it'll be back.
    My first suspicion was the app code doing transaction work and having database performance problems. But the app is non-transactional and the database is fine. The server farm nodes (4) are all experiencing the problems at equal rates, and the other apps on the farm are fine, so it appears to be app-specific rather than rooted in server state or database state.
    I looked at the stack a little more closely and it appears to be some kind of internal persistence issue, but a completely foreign one to me. We have no Persistent Stores configured, so I don't know where to even start on this puppy.
    EJB Exception occurred during invocation from home: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw exception: <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
    BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
    <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
    BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
    at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
    at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
    at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
    at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
    at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
    at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
    at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
    at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
    at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy365.performAction(Unknown Source)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
    at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
    at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
    at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
    at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
    at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
    at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
    BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
    at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
    at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
    at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
    at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
    at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
    at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
    at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.nextInternal(SelectImpl.java:2209)
    at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
    at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
    at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:35)
    at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
    at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
    at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
    at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
    at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
    at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy365.performAction(Unknown Source)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
    at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
    at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
    at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
    at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
    at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
    at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

    This was actually my first conclusion as well. But when I went to the Data Source for this connection, I found it's a non-transactional driver. That's what made me go back and give the trace a second look. I don't see any references to the Data Source in question. It's OpenJPA stuff and Session persistence stuff.Non-XA drivers can still participate in an XA transaction via a variety of JDBC data source options - for example, labeled "1PC" and "LLR" on the console. (If you want to understand the particulars search for "JTS" or "LLR" in the JDBC edocs).
    You seem to be suggesting maybe the setting can be made in a config doc, possibly of the app itself, right? Right. EJBs have a transaction-timeout attribute.
    As opposed to setting it in the console. WebLogic has a domain wide default transaction-timeout setting that can be set on the console, but I tend not to recommend using it. In addition, there's something called a "deployment plan" which can be used to override some of the common EJB attributes via configuration, but I'm not personally familiar with its usage.
    But isn't the setting vapor if we're using a nonXA driver?No.
    I wonder if this thing couldn't be telling me it's waiting on the persistence subsystem to come available to store simple session data? Sometimes the problem is that there are periodic app requests that are more complex/larger than others. Sometimes the system is simply overloaded, and takes 30 seconds to honor a request that might normally take 10 seconds.
    That other app is all about persistence. What if app2 is sucking some persistence subsystem dry and app 1 is waiting just to store session data? Could be.
    If the nonXA thing really does kill the quick timeout workaround, how could I health-check the persistence subsystem?Don't know. At a wild guess I'd check for CPU's at 100% on all involved serves, and examine database stats.

  • Update operation transaction timing out

    Hello,
    I have a large data structure that needs to be updated atomically (i.e. within a transaction). I am calling the logical service via a web service map, so I presume the transaction starts when the logical service is invoked. It is receiving a transaction timeout on the server, which I suspect is set to 30 seconds at the WebLogic level by our middleware team. (See stack trace below).
    The update operation SDO XML is at least 2MB.
    1. Is there any way to override this transaction timeout at the service or data space level?
    2. Is there any more efficient way to do this update? Sending a big wad of xml is inefficient, and I am not aware of another format supported by ODSI web services. I cannot use mediator API straight from my client to ODSI.
    3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
    Any advice would be much appreciated.
    Thanks,
    Jeff
    weblogic.xml.query.exceptions.XQuerySystemException: {bea-err}SYS003: Unexpected exception
         at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:96)
         at weblogic.xml.query.transaction.TransactionManager.teardownOnSuccess(TransactionManager.java:178)
         at com.bea.ld.EJBRequestHandler.handleProcessingComplete(EJBRequestHandler.java:1020)
         at com.bea.ld.EJBRequestHandler.handlePusher(EJBRequestHandler.java:979)
         at com.bea.ld.EJBRequestHandler.invokeOperation(EJBRequestHandler.java:323)
         at com.bea.ld.ServerWrapperBean.invoke(ServerWrapperBean.java:153)
         at com.bea.ld.ServerWrapperBean.invokeOperation(ServerWrapperBean.java:80)
         at com.bea.ld.ServerWrapper_s9smk0_ELOImpl.invokeOperation(ServerWrapper_s9smk0_ELOImpl.java:141)
         at com.bea.dsp.ws.RoutingHandler$PriviledgedRunner.run(RoutingHandler.java:96)
         at com.bea.dsp.ws.RoutingHandler.handleResponse(RoutingHandler.java:217)
         at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
         at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
         at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:176)
         at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
         at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
         at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
         at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
         at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.transaction.RollbackException: Transaction timed out after 33 seconds
    BEA1-460E808DE23C779E385F
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
         at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1708)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:255)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
         at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:94)
         ... 30 more
    Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
    BEA1-460E808DE23C779E385F
         at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1734)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1607)
         at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1879)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
         at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         ... 2 more

    1. Is there any way to override this transaction timeout at the service or data space level?
    You can set trans-timeout-seconds in the weblogic-ejb-jar.xml for your dataspace. You'll find it in <dataspaceName>dspejb.jar in <domain>/dsp/dataSpaces/<dataspaceName>request_handlers.ear. I've include a complete weblogic-ejb-jar.xml (at the end of the post) so you can see where to add it. Just copy-paste the <transaction-descriptor>...</>
    the request handlers ear is created when the dataspace is deployed the first time and during a full-deploy (i.e. you don't have to go back and edit it after incremental deploys)
    2a. Is there any more efficient way to do this update?
    If you described it in painful detail, we might be able to think of something. You might find mutators helpful - http://download.oracle.com/docs/cd/E13167_01/aldsp/docs32/dsp32wiki/Mutators%20for%20Updates.html
    3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
    You could write/host your own webservice on the ODSI server which would call ODSI via the java api. Your ws would expose operations to the following calls from your client
    contextId = myWsStartUserTransaction()
    while( moreChunks)
    myWsUpdate(contextId, chunk)
    myWSEndUserTransaction(contextId)
    Just a heads-up, WLS has an anti-denial-of-service attack setting that rejects input messages over a certain size. I believe the default is 10MB. You can set it in the WLS console.
    - Mike
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>Server</ejb-name>
    <stateless-session-descriptor>
    <stateless-clustering>
    <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
    <stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
    <!-- random | round-robin | weight-based -->
    <!--
    <stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
    class-name> -->
    <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
    tent>
    </stateless-clustering>
    </stateless-session-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>com.bea.ld.apps.dataservicesapp.server</jndi-name>
    <local-jndi-name>com.bea.ld.apps.dataservicesapp.localserver</local-jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>300</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>ServerTxRequired</ejb-name>
    <stateless-session-descriptor>
    <stateless-clustering>
    <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
    <stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
    <!-- random | round-robin | weight-based -->
    <!--
    <stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
    class-name> -->
    <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
    tent>
    </stateless-clustering>
    </stateless-session-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>com.bea.ld.apps.dataservicesapp.serverTxRequired</jndi-name>
    <local-jndi-name>com.bea.ld.apps.dataservicesapp.localserverTxRequired</local-
    jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>300</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>Metadata</ejb-name>
    <stateless-session-descriptor>
    <stateless-clustering>
    <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
    <stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>
    <!-- random | round-robin | weight-based -->
    <!--
    <stateless-bean-call-router-class-name>beanRouter</stateless-bean-call-router-
    class-name> -->
    <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
    tent>
    </stateless-clustering>
    </stateless-session-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>com.bea.ld.apps.dataservicesapp.metadata</jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>300</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

  • Cannot remove stateful session bean when transaction timed out

    The transaction timeout is set to 5 minutes. After several operations on the transactional
    stateful session bean(implements SessionSynchronization), the transaction timed out
    after 5 minutes and I got the IllegalStateException when calling another business
    method. After the transaction rolled back, weblogic.ejb20.locks.LockTimedOutException
    was thrown when attempting to remove the bean. It seems the lock on the bean was
    not released even though the transaction had been rolled back. Does anyone know how
    to remove the bean in this kind of situation?
    Here is the stacktrace:
    ####<Jun 11, 2002 2:39:35 PM PDT> <Notice> <EJB> <app1x.zaplet.cc> <server25044server>
    <ExecuteThread: '11' for queue: 'default'> <> <23168:7b09681c532dc7e3> <010015> <Error
    marking transaction for rollback: java.lang.IllegalStateException: Cannot mark the
    transaction for rollback. xid=23168:7b09681c532dc7e3, status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 299 seconds
    Xid=23168:7b09681c532dc7e3(3203140),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=299,seconds left=60,activeThread=Thread[ExecuteThread: '11' for queue:
    'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[server25044+server25044server]=(state=active),properties=({weblogic.jdbc=t3://10.0.100.93:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server25044server+10.0.100.93:7001+server25044+,
    Resources={})],CoordinatorURL=server25044server+10.0.100.93:7001+server25044+)]>
    java.lang.IllegalStateException: Cannot mark the transaction for rollback. xid=23168:7b09681c532dc7e3,
    status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
    timed out after 299 seconds
    Xid=23168:7b09681c532dc7e3(3203140),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=299,seconds left=60,activeThread=Thread[ExecuteThread: '11' for queue:
    'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[server25044+server25044server]=(state=active),properties=({weblogic.jdbc=t3://10.0.100.93:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server25044server+10.0.100.93:7001+server25044+,
    Resources={})],CoordinatorURL=server25044server+10.0.100.93:7001+server25044+)]
         at weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(TransactionImpl.java:1486)
         at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:466)
         at weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.java:255)
         at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:215)
         at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:371)
         at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
         at weblogic.ejb20.internal.StatefulEJBObject.preInvoke(StatefulEJBObject.java:169)
         at mypackage.MyBean_wbr3eg_EOImpl.addRecipients(MyBean_wbr3eg_EOImpl.java:450)
    ####<Jun 11, 2002 2:39:37 PM PDT> <Info> <EJB> <app1x.zaplet.cc> <server25044server>
    <ExecuteThread: '11' for queue: 'default'> <> <> <010049> <EJB Exception in method:
    remove: weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:AppmailBean
    with primary key:21,775,960,933,010,237 timed-out after waiting 0 ms. The transaction
    or thread requesting the lock was:Thread[ExecuteThread: '11' for queue: 'default',5,Thread
    Group for Queue: 'default'].>
    weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:AppmailBean
    with primary key:21,775,960,933,010,237 timed-out after waiting 0 ms. The transaction
    or thread requesting the lock was:Thread[ExecuteThread: '11' for queue: 'default',5,Thread
    Group for Queue: 'default'].
         at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:448)
         at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
         at weblogic.ejb20.manager.StatefulSessionManager.acquireLock(StatefulSessionManager.java:226)
         at weblogic.ejb20.manager.StatefulSessionManager.acquireLock(StatefulSessionManager.java:216)
         at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:310)
         at weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.java:754)
         at weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:86)
         at mypackage.MyBean_wbr3eg_EOImpl.remove(MyBean_wbr3eg_EOImpl.java:7308)

    If a stateful session throws a RuntimeException (your rollback) the container destroys the instance of the bean and all
    associated state information is lost, as required by the EJB specification.
    If you want to maintain client state it is generally best to use HttpSession objects (if you have a web application)
    for short-lived, client-specific data and JPA entities or other database backed storage for long-lived data.

  • Transaction timed out

    When the java program tries to insert the data (around 300 records), the error occurs as "EJB Exception: weblogic.transaction.internal.TimedOutException: Transaction timed out after 95 seconds"
    Anyone know what happen and how to resolve the problem?
    Furthermore, any method to record such an error into the Oracle log?
    Thanks a lot.

    Judging from the exception, it would appear that this is something that WebLogic is taking upon itself to throw. I'm assuming that somewhere in your WebLogic configuration, you have configured a timeout of 95 seconds. If that's the case, you would need to modify your WebLogic configuration to increase that timeout.
    Oracle has no limit on the amount of time a transaction can be open, so this error has to be caused by the application server. As such, I don't see any way to get this sort of error into any of the Oracle logs (I assume we're talking about trace files and alert logs on the Oracle server here). If your code caught this error, you could insert the error into an error log table in the Oracle database.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Transaction timed out after 29seconds

              hi,
              I am using 2pc with XA, for MQ and Sybase
              I am getting following exception.
              [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
              after 29seconds
              can somebody help me on this ?
              TIA
              Chidambar
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             

    default value of transaction timeout is 30 secs.
              Your tx may be running more than the default tx timeout.
              Either increase your tx timeout or re-consider your
              design.
              Kumar
              chidambar wrote:
              > hi,
              > I am using 2pc with XA, for MQ and Sybase
              > I am getting following exception.
              > ................................................................
              >
              > [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
              > after 29seconds
              >
              > ................................................................
              > can somebody help me on this ?
              > TIA
              > Chidambar
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         

  • Transaction timing out

    I have a problem with transaction timing out and I know how to increase the time out interval but I would just like to learn as to what exactly is going on and how I can fix the problem without increasing the timeout.
    class RequestProcessor {
    public void do() {
    // very long process
    doSomeWhereLongProcess()
    // retrieve another session bean
    persistence = (IPersistence) ctx.lookup( IPersistence.JNDI_NAME );
    persistence.insert()
    doSomeProcess();
    public class PersistenceFacade implements IPersistence {
         @PersistenceContext
         private EntityManager em;
    // calls an entityManager to retrieve
    public void retrieve()
    RequestProcessor is a session bean that is being called remotely. In ejb-jar.xml transaction type is set to Bean.
    It calls another session bean called PeristenceFacade that contains entity manager to insert entity beans. The transaction type in PersistenceFace
    is set to Container.
    While still executing a doSomeWhereLongProcess I get notification in log that transaction timed out and when it tries to called PersistenceFacade
    I get an exception. Why would it start a transaction even before I looked up a PersistenceFacade?
    I tried setting transaction type to Bean in PersistenceFacade but it is complaining that EntityManager must have a transaction.
    What is the proper way of handling this type of scenario? Is is simply increasing the timeout or can I handle this differently?
    Thanks

    Yes, it's perfectly legal to define a bean with bean-managed transaction management that doesn't actually start a transaction. In that case, the question is where the transaction is getting started. Even for beans with container-managed transactions, @PostContruct for a session bean is never a transactional method, so it seems odd that a new transaction would be started there unless some piece of application code is starting it.
    You might want to post to a JBoss forum to get more info. You can try running your application on the Java EE SDK or using the verifier in the Java EE SDK to see if it detects any issues.
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Users timing out in Oracle AS 10.1.3

    I am trying to figure out why the load tests running in the target environment (large and very secure corporate network) against a Spring MVC/EJB3 application running in Orcale AS 10.1.3 fail. The application is deployed on a server running on a Solaris Sparc 440 machine.
    The tests are run from LoadRunner application, which simulates multiple users sending HTTP requests to perform a use case in the system under test. The use case involves transitioning between 4 different pages with the application sending a number (relatively small, 5-6 pr use case) of queries to the Oracle database running on a different machine (using JPA/TopLink) and doing a single insert.
    The LoadRunner shows that after a few minutes after the test starts the users start timing out. The HTTP request sent to the application server (with timeout value of two minutes) do not get fulfilled.
    I have looked at various performance metrics: CPU and memory utilization on the Solaris machine, metrics provided by the Oracle AS admin console (JVM Heap memory usage, number of EJB methods per second, number of servlet requests per second and request processing time. Nothing indicates a bottleneck. The application uses much less memory than is allocated (100MB out of 2GB allowed), the CPU and memory utilization on the machine are within norm. The EJB methods execute in a fraction of a second (nothing to justify a two-minute delay).
    An interesting aspect of the test is the effect of the static resources on the performance. About two thirds of HTTP request in the test are for static resources (GIFs and CSS). They are not being cached by the HTTP server. Two similar LoadRunner tests were performed. In one, all HTTP requests were submitted (20 users running 10 iterations each). In the second, LoadRunner itself cached the static resources, thus submitting only the requests processed by Spring MVC portion of the Java application (the same number of users and iterations). The second tests produced a much lower timeout rate. (Out of 218 transactions, 34 timed out in the first test and 2 in the second).
    I am trying to understand what may cause the timeouts in these tests. The most obvious culprit is the Java application being tested, but if the bottleneck was in Java, then caching static resources would have almost no effect on the performance results (since static resources do not go to the Java application).
    I tested the same application using Apache JMeter in the development environment (a small company network) with Oracle AS running on Solaris VM (itself running on a Windows machine, which is less powerful than the Sparc 440 machine). The test running exactly the same use case with 20 users running 200 iterations each went without a single hiccup. Not a single HTTP request timed out and the mean request time was 69 ms.
    I am looking for help in finding the causes for the performance issues in the target environment and why they cannot be replicated in the development environment. What may be causing the simulated users to time out?
    Thank you,
    Michael

    Yes OHS (Oracle HTTP Server) comes with PHP pre-installed and ready to use. Refer following for details:
    http://download.oracle.com/docs/cd/B32110_01/web.1013/b28948/php.htm#BABIGCFB
    Thanks
    Shail

  • TNS-12535: TNS:operation timed out with ORA-609

    Hi All,
    In 11gR2 Database on Linux ,I am getting the below error for one client only -
    This is a c++ application which is accessing database from different linux machines with Oracle Client installed on each machine(OCI).
    C++ application is working fine from all linux machines except the one which in mentioned in the below alert log error.
    But from this client I can connect to the database using sql*client -
    The Error is
    ====================================
    Fatal NI connect error 12170.
       VERSION INFORMATION:
             TNS for Linux: Version 11.2.0.3.0 - Production
             Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
             TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
       Time: 07-AUG-2013 18:19:51
       Tracing not turned on.
       Tns error struct:
         ns main err code: 12535
    TNS-12535: TNS:operation timed out
         ns secondary err code: 12606
         nt main err code: 0
         nt secondary err code: 0
         nt OS err code: 0
       Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.xxx.55)(PORT=57181))
    Wed Aug 07 18:22:02 2013
    piodr aborting process unknown ospid (29122) as a result of ORA-609
    Port Number in client address is keep changing.
    ====================================
    C++ application captures below error messages on client -
    Error - ORA-03135: connection lost con
    Error - ORA-12636: Packet send failed
    =======================================
    I have tried to increase the
    SQLNET.INBOUND_CONNECT_TIMEOUT and
    Listener.ora: INBOUND_CONNECT_TIMEOUT_listener_name
    But it is not working.
    I have also tried the steps mentioned in the document id  Doc ID 119706.1 and Doc ID 1116960.1 but no luck.
    Please suggest any other things that I can check.
    Thanks,
    Abhijit

    please, refer to:
    https://forums.oracle.com/thread/2434970

  • Get "connect timed out" with twitter4j api

    modified HelloWorldAdapter.java to call " unauthenticatedTwitter.getPublicTimeline();".
    add following code before calling twitter api
    System.setProperty("twitter4j.http.proxyHost", "www-proxy.us.oracle.com"); System.setProperty("twitter4j.http.proxyPort", "80");
    the CEP HelloWorld CEP fails with "connect timed out"
    If I use similar code (testwitter.java) outside CEP. works fine.
    I am using eclipse to test the code.
    --- here is part of the testtwitter.java
    Twitter unauthenticatedTwitter = new TwitterFactory().getInstance();
         System.out.println("Showing public timeline.");
         System.setProperty("twitter4j.http.proxyHost", "www-proxy.us.oracle.com");
         System.setProperty("twitter4j.http.proxyPort", "80");
         try {
         List<Status> statuses = unauthenticatedTwitter.getPublicTimeline();
         for (Status status : statuses) {
         System.out.println(status.getUser().getName() + ":" +
         status.getText());
    --- here is the part of the generateTwitterMessage() at HelloWorld CEP
         Twitter unauthenticatedTwitter = new TwitterFactory().getInstance();
         System.setProperty("twitter4j.http.proxyHost", "www-proxy.us.oracle.com");
         System.setProperty("twitter4j.http.proxyPort", "80");
         System.out.println("---- after seting proxyhost, call generateTwitterMessage");
         System.out.println("---Showing public timeline.");
    try {
         List<Status> statuses = unauthenticatedTwitter.getPublicTimeline();
    for (Status status : statuses) {
         String twitterMsg = status.getUser().getName() + ":" +status.getText();
    System.out.println("msg--"+twitterMsg);
    String message = this.message + dateFormat.format(new Date()) + twitterMsg ;
    HelloWorldEvent event = new HelloWorldEvent();
    event.setMessage(message);
    eventSender.sendInsertEvent(event);
    }catch ....
    Please help me on proxy host/port setup inside CEP

    yatin002 wrote:
    Any ideas/suggestions to solve this issue ???Catch the Exception?
    static boolean checkURL(URL url){
        HttpURLConnection httpCon = null;
        try {
            httpCon = (HttpURLConnection)url.openConnection();
            return httpCon.getResponseCode() == HttpURLConnection.HTTP_OK;
        catch(Exception ex){
            ex.printStackTrace();
            return false;
        finally {
            if( httpCon != null ){
                httpCon.disconnect();
        }

  • Issue implemeting Implicit Transactions using TransactionScope with Oracle

    I’m implementing Transaction support in an application using Transactionscope (have done this for other providers with no issue’s ) , for Oracle 10g Database , with Oracle Client 11g installed on my system . The Code is as simple as below . But the instant the Oracle connection attempts to Open , I get different errors , for different Oracle Providers , for the same action (Opening the Oracle connection within a Transactionscope ) . Googling for the error returned a lot of people who have faced the isssues but no solution.
    System config :
    1)Oracle 10g databse
    2)Oracle Client 11g
    3)MSDTC enabled
    4)OraMTS.dll registered
    5)OS; Windows XP
    Am I missing out any configuration settings .Please help
    Any idea what could be the reason . has it got to do with some kind of settings/ configurations.
    DbProviderFactory factory =DbProviderFactories.GetFactory("System.Data.OracleClient");
    //DbProviderFactory factory = DbProviderFactories.GetFactory("Oracle.DataAccess.Client");
    string constr =@"Data Source=(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = ind-mhp1w3s0015)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = XE)));User Id=refapp;Password=refapp;enlist=true";
    using (TransactionScope scope =newTransactionScope(TransactionScopeOption.RequiresNew))
    //using (DbConnection conn1 = factory.CreateConnection())
    using(OracleConnection oraconn =newOracleConnection(constr))
    oraconn.Open();
    Error encountered :
    1) Data provider internal error(-3000) [System.String] :-Provider :Oracle.DataAccess.Client
    2) "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." Provider:- System.Data.OracleClient
    Thanks & Regards
    Girija

    hi,
    do not have access to an 11g database ..else would have tried it . Can you please let me know what are the settings that you have done on ur sytem.
    Regards
    Girija

  • Inbound connection timed out and TNS:operation timed out in Oracle 11g

    Hello All,
    We are getting the below messages in alert log since yesterday... And we could not see any other messages other than this...Users also complaining slow response from DB,
    Could any one please help me to resolve this ...? I believe in 11g inbound connection time out is deprecated ..isn't it ...?
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.2.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    Time: 18-NOV-2011 01:54:50
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 110
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.21.0.159)(PORT=4789))
    Fri Nov 18 09:43:04 2011
    Fatal NI connect error 12170.
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.2.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    Time: 18-NOV-2011 09:43:04
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.25.1.65)(PORT=50839))
    WARNING: inbound connection timed out (ORA-3136)

    889828 wrote:
    Hello All,
    We are getting the below messages in alert log since yesterday... And we could not see any other messages other than this...Users also complaining slow response from DB,
    Could any one please help me to resolve this ...? I believe in 11g inbound connection time out is deprecated ..isn't it ...?
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.2.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    Time: 18-NOV-2011 01:54:50
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 110
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.21.0.159)(PORT=4789))
    Fri Nov 18 09:43:04 2011
    Fatal NI connect error 12170.
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.2.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
    Time: 18-NOV-2011 09:43:04
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.25.1.65)(PORT=50839))
    WARNING: inbound connection timed out (ORA-3136)The most common cause for this error is a firewall between clint & DB Server;
    which allows packets on port #1521, but does not allow DB Server to use new high random port.

  • "Connection timed out" with HttpClient.

    Hi,
    My goal is to consume a web service using Apache AXIS. This web service uses Integrated Windows Authentication.
    I use IE have configured Proxy server address and Proxy server port using IE's Tools -> Internet Options -> Connections Tab -> LAN Settings -> Proxy serer.
    If type the webservice endpoint address of the form http://239.271.380.120/serveme/WS.asmx in my browser then I see in my browser "You are not authorized to view this page .. HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration. Internet Information Services (IIS)" but there is another client in another network who is getting a login dialog to enter domain\\username and password when he types the web service endpoint address in the browser. This makes me think that either the so called another client is in the same domain as the web service provider and I am not.
    Anway, I tried to write standalone HttpClient (I use commons-httpclient-3.0-rc3, commons-codec-1.3, commons-logging-1.0.4) program NTCredentialsClient.java like below :
    NTCredentialsClient.java
    import org.apache.commons.httpclient.*;
    import org.apache.commons.httpclient.auth.*;
    import org.apache.commons.httpclient.methods.*;
    public class NTCredentialsClient {
         public static void main(String args[]) {
              HttpClient client = new HttpClient();
              NTCredentials credentials = new NTCredentials("user1", "password1", "MYDESKTOP", "domain1");
              AuthScope authScope = new AuthScope("20.222.335.37", 3128);
              client.getState().setCredentials(authScope, credentials);
              //client.getState().setCredentials(AuthScope.ANY, credentials);
              GetMethod get = new GetMethod("http://239.271.380.120/serveme/WS.asmx");
              get.setDoAuthentication(true);
              try {
                   int status = client.executeMethod(get);
                   System.out.println(status);
                   get.getResponseBodyAsStream();
                   // print the status and response
                    System.out.println(status + "\n" + get.getResponseBodyAsString());
              catch (Exception e) {
                   e.printStackTrace();
              finally {
                   get.releaseConnection();
    ------------------------------------------------------------------In the above program, user1, password1, domain1 are details given by my service provider and
    MYDESKTOP is my local machine name from which I am running the above program. 20.222.335.37
    is my proxy server address and 3128 is my proxy server port. Now when I run the above
    program I get this exception :
    Aug 16, 2005 12:43:45 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: I/O exception caught when processing request: Connection timed out: connect
    Aug 16, 2005 12:43:46 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: Retrying request
    Aug 16, 2005 12:44:11 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: I/O exception caught when processing request: Connection timed out: connect
    Aug 16, 2005 12:44:11 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: Retrying request
    Aug 16, 2005 12:44:37 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: I/O exception caught when processing request: Connection timed out: connect
    Aug 16, 2005 12:44:37 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
    INFO: Retrying request
    java.net.ConnectException: Connection timed out: connect
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(Unknown Source)
            at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
            at java.net.PlainSocketImpl.connect(Unknown Source)
            at java.net.SocksSocketImpl.connect(Unknown Source)
            at java.net.Socket.connect(Unknown Source)
            at java.net.Socket.connect(Unknown Source)
            at java.net.Socket.<init>(Unknown Source)
            at java.net.Socket.<init>(Unknown Source)
            at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:79)
            at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:121)
            at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:704)
            at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:382)
            at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:168)
            at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
            at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
            at NTCredentialsClient.main(NTCredentialsClient.java:28)
    ------------------------------------------------------------------Can anyone please tell me whether the configurations I have made in my above client program are correct or is there anything that I am overlooking. Also, in the above program for AuthScope constructor, do I need to pass web service server adderss and port OR my local proxy address and local proxy port as constructor arguments ?
    Please suggest ...
    Thanks & Regards,
    Kr.

    You will need to define your proxy settings. In java, these are provided as system properties:
    System.setProperty("http.proxyHost", "<proxy>");
    System.setProperty("http.proxyPort", "<port>");
    If your proxy uses HTTP authentication, you will need to define a few more system properties, which I don't know off the top of my head. This should actually get you connected with the web server, but as for the 302 error, you'll probably need to contact the system administrator.
    Cheers
    Todd.

  • Tns timed out in oracle apps server

    Hi ,
    I am receiving the following error in the alert log.
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 145
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.121)(PORT=3092))
    Mon Apr 18 09:57:18 2011
    Developer are complaing that they are receving Ora 03113-End of File on communication channel.
    please advise.
    With Regards,
    Srini

    Hi;
    Please see:
    ‘Fatal NI connect error 12170', 'TNS-12535: TNS:operation timed out' Reported in 11g Alert Log [ID 1286376.1]
    Troubleshooting Guide TNS-12535 or ORA-12535 or ORA-12170 Errors [ID 12535.1]
    Concurrent Processing - R12 Concurrent Managers Not Starting After Patching or Upgrade Changes [ID 811093.1]
    OERR: TNS 505 "Operation timed out" [ID 21996.1]
    Regard
    Helios

  • Facebook timed out with new Ios 4

    Hi,
    When I use my 3GS with wifi disabled, I can't access to facebook, Safari and other apps. I see the wheel turning and Then I have a message saying "timed out". I restore my 3GS, reinstall all the applications but nothing. All is working in wifi mode. Could you help me? Thanks

    Exactly the same happened to my iPhone 3GS. While Apple Service proposed to send the iPhone to repair centre I´ve found that the problem only happened with activated SIM card pin security check. Switching pin checking off and re-installing software again helped. There are other threads discussing similiar problems; maybe, it is a matter of the service provider (Vodafone in my case).

Maybe you are looking for