[JBossCache] - Re: JBCache 2.0.0 / Weblogic 9: Exception while trying to ro
by manik.surtani＠jboss.com
Hmm, assuming the "client" java program does not have an instance of JBoss Cache, the exceptions must be on the server side.
Here is the code that triggers this rollback:
| ...
| try
| {
| .....
| }
| catch (Throwable t)
| {
| try
| {
| tx.setRollbackOnly();
| }
| catch (SystemException se)
| {
| throw new RuntimeException("setting tx rollback failed ", se);
| }
| if (t instanceof RuntimeException)
| throw (RuntimeException) t;
| else
| throw new RuntimeException("", t);
| }
|
So the exception should be thrown on the server as well. From your logs though, it seems as though tx.setRollbackOnly() triggers an exception and the code above never gets to the point of throwing or even logging the REAL problem.
This is clearly a weblogic-specific issue since this does work correctly on other tested transaction managers.
As a workaround, we would have to log the error before setting the tx to rollback-only to ensure it is logged in such a case. Could you raise a feature request in JIRA for this?
In the meanwhile (if you are happy compiling your own version of JBoss Cache) I'd suggest getting the src code for 2.0.0.GA and making the change yourself to help try and find the problem you're experiencing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122635#4122635
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122635
18 years, 6 months
[JBossCache] - Re: Config Question
by lovelyliatroim
Right, in the quest for higher throughput using my cache and the JDBCCacheLoader im experiencing what to me is strange behaviour.
Here is my config for the record
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Sample TreeCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
| <mbean code="org.jboss.cache.jmx.CacheJmxWrapper"
| name="jboss.cache:service=CMDSPersistentCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
| <depends>
| jboss.jca:service=DataSourceBinding,name=cmdsDB
| </depends>
|
| <!--
| Configure the TransactionManager
| -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.transaction.GenericTransactionManagerLookup
| </attribute>
|
|
|
|
| <!--
| Node locking level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">LOCAL</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">CMDS-Cluster</attribute>
|
| <!-- JGroups protocol stack properties NOT NEEDED since CacheMode is LOCAL -->
|
| <attribute name="LockAcquisitionTimeout">15000</attribute>
|
| <attribute name="StateRetrievalTimeout">6000</attribute>
| <attribute name="SyncReplTimeout">6000</attribute>
| <!--<attribute name="NodeLockingScheme">OPTIMISTIC</attribute>
| -->
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <attribute name="wakeUpIntervalSeconds">30</attribute>
| <attribute name="eventQueueSize">200000</attribute>
| <attribute name="policyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
|
| <region name="/_default_">
| <attribute name="maxNodes">5000</attribute>
| <attribute name="timeToLiveSeconds">1000</attribute>
| </region>
| <region name="/quotes">
| <attribute name="maxNodes">1</attribute>
| <attribute name="timeToLiveSeconds">10000</attribute>
| </region>
| </config>
| </attribute>
|
| <attribute name="CacheLoaderConfig" replace="false">
| <config>
| <!-- are the cache loaders shared in a cluster? -->
| <shared>false</shared>
| <async>true</async>
| <fetchPersistentState>false</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
| <purgeOnStartup>false</purgeOnStartup>
|
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
|
| <properties>
| cache.jdbc.datasource=java:/cmdsDB
| </properties>
|
| </cacheloader>
|
| </config>
| </attribute>
|
| </mbean>
|
|
| </server>
|
|
The way i was thinking was this, i wanted to see could i get a higher throughput for my cache and thought maybe if i switched the NodeLockingScheme from the default pessimistic to optimistic that i might be more throughput. Now here is where the strange thing happened or maybe it is my mis-understanding along the way. The throughput is higher alright in OPTIMISTIC mode but the reason its higher is because it aint making any writes to the DB any more!! There are no entries in the DB at all!! If i look at the jmx-console i see the record in the caches memory but it aint in the DB. Records are written with PESSIMISTIC mode but not with OPTIMISTIC, any ideas why im seeing this behaviour?.
Log entries in OPTIMISTIC mode are as follows
| 2008-01-23 14:21:18,690 INFO [STDOUT] 2008-01-23 14:21:18,690 DEBUG [at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-23 14:21:18,690 DEBUG [at.sit.cdms.web.actions.ActionFactory] Looking for bean addItem
|
| 2008-01-23 14:21:18,690 DEBUG [org.springframework.beans.factory.support.DefaultListableBeanFactory] Returning cached instance of singleton bean 'addItem'
|
| 2008-01-23 14:21:18,690 DEBUG [org.jboss.cache.interceptors.TxInterceptor] local transaction exists - registering global tx if not present for Thread[http-127.0.0.1-8080-1,5,jboss]
|
| 2008-01-23 14:21:18,690 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/2)
|
| 2008-01-23 14:21:18,706 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Running commit phase. One phase? false
|
| 2008-01-23 14:21:18,706 DEBUG [org.jboss.cache.interceptors.OptimisticValidatorInterceptor] Commiting successfully validated changes for GlobalTransaction GlobalTransaction:<null>:2
|
| 2008-01-23 14:21:18,706 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished local commit/rollback method for GlobalTransaction:<null>:2
|
| 2008-01-23 14:21:18,706 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished commit phase
|
| 2008-01-23 14:21:18,706 INFO [STDOUT] 2008-01-23 14:21:18,706 DEBUG [at.sit.cdms.web.actions.test.AddItem] - Added item with index of 2
|
| 2008-01-23 14:21:18,706 DEBUG [at.sit.cdms.web.actions.test.AddItem] Added item with index of 2
|
| 2008-01-23 14:21:19,330 INFO [STDOUT] 2008-01-23 14:21:19,330 DEBUG [at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-23 14:21:19,330 DEBUG [at.sit.cdms.web.actions.ActionFactory] Looking for bean addItem
|
| 2008-01-23 14:21:19,330 DEBUG [org.springframework.beans.factory.support.DefaultListableBeanFactory] Returning cached instance of singleton bean 'addItem'
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.interceptors.TxInterceptor] local transaction exists - registering global tx if not present for Thread[http-127.0.0.1-8080-1,5,jboss]
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/3)
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Running commit phase. One phase? false
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.interceptors.OptimisticValidatorInterceptor] Commiting successfully validated changes for GlobalTransaction GlobalTransaction:<null>:3
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished local commit/rollback method for GlobalTransaction:<null>:3
|
| 2008-01-23 14:21:19,330 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished commit phase
|
| 2008-01-23 14:21:19,330 INFO [STDOUT] 2008-01-23 14:21:19,330 DEBUG [at.sit.cdms.web.actions.test.AddItem] - Added item with index of 3
|
| 2008-01-23 14:21:19,330 DEBUG [at.sit.cdms.web.actions.test.AddItem] Added item with index of 3
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.TxInterceptor] local transaction exists - registering global tx if not present for Thread[EvictionTimer-0,5,jboss]
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Running commit phase. One phase? false
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.OptimisticValidatorInterceptor] Commiting successfully validated changes for GlobalTransaction GlobalTransaction:<null>:4
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished local commit/rollback method for GlobalTransaction:<null>:4
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished commit phase
|
| 2008-01-23 14:21:26,563 DEBUG [org.jboss.cache.interceptors.TxInterceptor] local transaction exists - registering global tx if not present for Thread[EvictionTimer-0,5,jboss]
|
| 2008-01-23 14:21:26,579 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Running commit phase. One phase? false
|
| 2008-01-23 14:21:26,579 DEBUG [org.jboss.cache.interceptors.OptimisticValidatorInterceptor] Commiting successfully validated changes for GlobalTransaction GlobalTransaction:<null>:5
|
| 2008-01-23 14:21:26,579 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished local commit/rollback method for GlobalTransaction:<null>:5
|
| 2008-01-23 14:21:26,579 DEBUG [org.jboss.cache.interceptors.TxInterceptor] Finished commit phase
|
|
|
I dont see any "inserts" like i normally see when in pessimistic mode!!
Another thing i noticed with the pessimictic log, was the number of selects going on.
Log looks like this for pessimistic
| 2008-01-23 13:43:10,554 DEBUG [at.sit.cdms.web.actions.ActionFactory] Looking for bean addItem
|
| 2008-01-23 13:43:10,554 DEBUG [org.springframework.beans.factory.support.DefaultListableBeanFactory] Returning cached instance of singleton bean 'addItem'
|
| 2008-01-23 13:43:10,554 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/2)
|
| 2008-01-23 13:43:10,554 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/2)
|
| 2008-01-23 13:43:10,554 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/2)
|
| 2008-01-23 13:43:10,554 INFO [STDOUT] 2008-01-23 13:43:10,554 DEBUG [at.sit.cdms.web.actions.test.AddItem] - Added item with index of 2
|
| 2008-01-23 13:43:10,554 DEBUG [at.sit.cdms.web.actions.test.AddItem] Added item with index of 2
|
| 2008-01-23 13:43:10,554 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: insert into jbosscache (fqn, node, parent) values (?, ?, ?) (/quotes/2)
|
| 2008-01-23 13:43:10,601 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes)
|
| 2008-01-23 13:44:20,226 INFO [STDOUT] 2008-01-23 13:44:20,226 DEBUG [at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-23 13:44:20,226 DEBUG [at.sit.cdms.web.actions.ActionFactory] Looking for bean addItem
|
| 2008-01-23 13:44:20,226 DEBUG [org.springframework.beans.factory.support.DefaultListableBeanFactory] Returning cached instance of singleton bean 'addItem'
|
| 2008-01-23 13:44:20,226 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/3)
|
| 2008-01-23 13:44:20,226 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/3)
|
| 2008-01-23 13:44:20,242 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes/3)
|
| 2008-01-23 13:44:20,242 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: insert into jbosscache (fqn, node, parent) values (?, ?, ?) (/quotes/3)
|
| 2008-01-23 13:44:20,258 DEBUG [org.jboss.cache.loader.JDBCCacheLoader] executing sql: select node from jbosscache where fqn=? (/quotes)
|
| 2008-01-23 13:44:20,258 INFO [STDOUT] 2008-01-23 13:44:20,242 DEBUG [at.sit.cdms.web.actions.test.AddItem] - Added item with index of 3
|
| 2008-01-23 13:44:20,242 DEBUG [at.sit.cdms.web.actions.test.AddItem] Added item with index of 3
|
|
Im seeing 3 selects and then a write, surely thats overhead!! Ok I have now seen http://jira.jboss.org/jira/browse/JBCACHE-1261. That relates to what im seeing with in pessimistic mode.
Any thoughts on whats going on with the OPTIMISTIC mode or am i missing the big picture??
Cheers,
LL
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122633#4122633
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122633
18 years, 6 months
[JBoss jBPM] - Re: problem when traversing to end state
by twiceknightly
As an experiment I set the TransactionAttribute on my EJB to NotSupported. Surprizingly it worked without any problems. What really worries me is I have the hibernate config given below tying hibernate into JTA!
| <jbpm-context>
| <service name="persistence" factory="org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory" />
| <factory>
| <bean class="org.jbpm.persistence.db.DBPersistenceServiceFactory">
| <field name="isCurrentSessionEnabled">
| <false/>
| </field>
| <field name="isTransactionEnabled">
| <false/>
| </field>
| </bean>
| </factory>
| </service>
| <service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
| <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory" />
| <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
| <service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory" />
| <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" />
| </jbpm-context>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122631#4122631
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122631
18 years, 6 months
[JBossCache] - JBCache 2.0.0 / Weblogic 9: Exception while trying to rollba
by spennec
I'm experiencing a strange problem, with TreeCache seemingly trying to rollback a Weblogic transaction.
Here's the setup:
- Two weblogic 9 servers, running a clustered application.
- Each night, the cached data must be refreshed. Since this process requires other external processes to succeed before running, it is triggered by an external client. It's a simple Java app that calls two methods in a stateless session bean.
The cache reloader client calls one instance. This instance reloads its cache. When a specific event occurs, the second instances catches it thanks to a CacheListener and starts its own reload. We do not use replication for this reloading process since the data that would be transfered at commit-time is too big. While the cache normally uses replications, for daily operations, the reloading puts the cache in LOCAL mode, only for the reloading duration.
The following exception was encountered on the client app that triggered the reloading of the cache. On the servers, there were absolutely no exceptions, and everything went smoothly. All logs show that the two instances reloaded their cached data successfully.
Here is the stacktrace:
| ###### CLIENT APPLICATION
| com.myCompany.commons.exception.SystemException: See nested for more details.
| at com.myCompany.dac.ejb.DacRemoteExceptionInterceptor.handleRemote(DacRemoteExceptionInterceptor.java:55)
| at com.myCompany.dac.ejb.DacRemoteExceptionInterceptor.execute(DacRemoteExceptionInterceptor.java:22)
| at com.myCompany.util.bizdel.BusinessDelegateInvocationContext.proceed(BusinessDelegateInvocationContext.java:46)
| at com.myCompany.util.bizdel.BusinessDelegate$1.invoke(BusinessDelegate.java:286)
| at $Proxy6.resetAndLoadCache(Unknown Source)
| at com.myCompany.dac.cache.DacCacheReloader.main(DacCacheReloader.java:24)
|
| ###### CAUGHT EXCEPTION
| Caused by: javax.transaction.TransactionRolledbackException: BEA1-2AB0DCA982790F4DB46C: weblogic.transaction.internal.AppSetRollbackOnlyException
| at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:524)
| at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1172)
| at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:84)
| at weblogic.transaction.internal.ServerSCInfo.doBeforeCompletion(ServerSCInfo.java:1150)
| at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1128)
| at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
| at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1288)
| at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2098)
| at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:259)
| at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
| at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:539)
| at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
| at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
| at com.myCompany.dac.svc.ejb.session.DacAdmin_accoim_EOImpl.resetAndLoadCache(DacAdmin_accoim_EOImpl.java:191)
| at com.myCompany.dac.svc.ejb.session.DacAdmin_accoim_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundRequest;
| Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object;)Lweblogic.rmi.spi.OutboundResponse;(Unknown Source)
| at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
| at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
| at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
| at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
| at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
| at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:388)
| at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
| at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
| at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
| at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
| ; nested exception is:
| weblogic.transaction.internal.AppSetRollbackOnlyException
| at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)
| at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
| at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
| at com.myCompany.myProject.svc.ejb.session.myProjectAdmin_accoim_EOImpl_921_WLStub.resetAndLoadCache(Unknown Source)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.myCompany.util.bizdel.BusinessDelegateInvocationContext.proceed(BusinessDelegateInvocationContext.java:49)
| at com.myCompany.dac.ejb.DacRemoteExceptionInterceptor.execute(DacRemoteExceptionInterceptor.java:20)
| ... 4 more
| Caused by: weblogic.transaction.internal.AppSetRollbackOnlyException
| at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:524)
| at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1172)
| at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:84)
| at weblogic.transaction.internal.ServerSCInfo.doBeforeCompletion(ServerSCInfo.java:1150)
| at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1128)
| at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
| at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1288)
| at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2098)
| at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:259)
| at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
| at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:539)
| at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
| at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
| at com.myCompany.dac.svc.ejb.session.DacAdmin_accoim_EOImpl.resetAndLoadCache(DacAdmin_accoim_EOImpl.java:191)
| at com.myCompany.dac.svc.ejb.session.DacAdmin_accoim_EOImpl_WLSkel.invoke(Unknown Source)
| at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
| at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
| at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
| at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
| at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
| at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:388)
| at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
| at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
| at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
| at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
|
The org.jboss lines seem to show that some JBossCache component provoked an Exception while trying to trigger the rollback. Unfortunately there is no message explaining the reason of the problem.
I am also very confused by the fact that there are absolutely no Exceptions on the servers.
- Is is correct to say that JBossCache was trying to mark the weblogic transaction as rollbacked but didn't succeed?
- How can I know which problem lead JBossCache to trigger the rollback?
- Is that a JBossCache bug?
- What is the state of the cache after such an Exception?
- Why is this exception not caused by an Exception on one of the servers? (or at least: why is there no trace of this exception on any of the servers?)
Thanks for your answers,
Sebastien
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122628#4122628
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122628
18 years, 6 months