[JCA/JBoss] - Re: HELP:CMP entity beans accessing encrypted datasource
by achu.prav
Hi Adrian ,
As suggested by you I enabled the trace.
The summary of the trace log is below:
---------------------------------------------------------
javax.security.auth.login.LoginException: Failed to decode password: java.lang.NullPointerException
at org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule.commit(JaasSecurityDomainIdentityLoginModule.java:130)
----------------------------------------------------------
>From a servlet I am able to access the encrypted datasource without problems.This problem happens only if the CMP entity bean accesses the datasource.
Is it failing due to any security restrictions on accessing server.password file ?
Please help.
Following is the entire error stack trace:
---------------------------------------------------------
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.plugins.SecurityConfig] Creating jboss.security:service=SecurityConfig
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.plugins.SecurityConfig] Created jboss.security:service=SecurityConfig
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Creating jboss.security:service=XMLLoginConfig
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Created jboss.security:service=XMLLoginConfig
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Creating jboss.security:service=JaasSecurityManager
2008-06-02 19:00:59,765 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Created jboss.security:service=JaasSecurityManager
2008-06-02 19:00:59,843 DEBUG [org.jboss.security.plugins.JaasSecurityDomain] Creating jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword
2008-06-02 19:00:59,843 DEBUG [org.jboss.security.plugins.JaasSecurityDomain] Created jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword
2008-06-02 19:01:00,015 DEBUG [org.jboss.security.plugins.SecurityConfig] Starting jboss.security:service=SecurityConfig
2008-06-02 19:01:00,015 DEBUG [org.jboss.security.plugins.SecurityConfig] Installed JAAS Configuration service=jboss.security:service=XMLLoginConfig, config=org.jboss.security.auth.login.XMLLoginConfigImpl@1a9d1b
2008-06-02 19:01:00,015 DEBUG [org.jboss.security.plugins.SecurityConfig] Started jboss.security:service=SecurityConfig
2008-06-02 19:01:00,015 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Starting jboss.security:service=XMLLoginConfig
2008-06-02 19:01:00,015 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Begin loadConfig, loginConfigURL=file:/C:/jboss-3.2.6/server/default/conf/login-config.xml
2008-06-02 19:01:00,015 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/C:/jboss-3.2.6/server/default/conf/login-config.xml
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=client-login
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=jbossmq
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=HsqlDbRealm
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=FirebirdDBRealm
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=JmsXARealm
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=jmx-console
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=web-console
2008-06-02 19:01:00,031 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=other
2008-06-02 19:01:00,046 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Parsing application-policy=EncryptedPPMEMSDbRealm
2008-06-02 19:01:00,046 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] End loadConfig, loginConfigURL=file:/C:/jboss-3.2.6/server/default/conf/login-config.xml
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Started jboss.security:service=XMLLoginConfig
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Starting jboss.security:service=JaasSecurityManager
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] securityMgrCtxPath=java:/jaas
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] cachePolicyCtxPath=java:/timedCacheFactory
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] SecurityProxyFactory=org.jboss.security.SubjectSecurityProxyFactory@afa68a
2008-06-02 19:01:00,046 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Started jboss.security:service=JaasSecurityManager
2008-06-02 19:01:17,328 TRACE [org.jboss.security.plugins.JaasSecurityManager] Constructing
2008-06-02 19:01:17,328 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityManager@1978933
2008-06-02 19:01:17,328 DEBUG [org.jboss.security.plugins.JaasSecurityManager.JmsXARealm] CachePolicy set to: org.jboss.util.TimedCachePolicy@16d64c5
2008-06-02 19:01:17,328 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] setCachePolicy, c=org.jboss.util.TimedCachePolicy@16d64c5
2008-06-02 19:01:17,328 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Added JmsXARealm, org.jboss.security.plugins.SecurityDomainContext@f2c96c to map
2008-06-02 19:01:17,359 TRACE [org.jboss.security.plugins.JaasSecurityManager] Constructing
2008-06-02 19:01:17,359 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityManager@ea443f
2008-06-02 19:01:17,359 DEBUG [org.jboss.security.plugins.JaasSecurityManager.EncryptedPPMEMSDbRealm] CachePolicy set to: org.jboss.util.TimedCachePolicy@268cc6
2008-06-02 19:01:17,359 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] setCachePolicy, c=org.jboss.util.TimedCachePolicy@268cc6
2008-06-02 19:01:17,359 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Added EncryptedPPMEMSDbRealm, org.jboss.security.plugins.SecurityDomainContext@e41d4a to map
2008-06-02 19:02:46,671 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] Begin getAppConfigurationEntry(EncryptedPPMEMSDbRealm), size=9
2008-06-02 19:02:46,671 TRACE [org.jboss.security.auth.login.XMLLoginConfigImpl] End getAppConfigurationEntry(EncryptedPPMEMSDbRealm), authInfo=AppConfigurationEntry[]:
[0]
LoginModule Class: org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
ControlFlag: LoginModuleControlFlag: required
Options:name=managedConnectionFactoryName, value=jboss.jca:service=LocalTxCM,name=EntityMedia
name=password, value=2F1yKmeLvC7m6CTT3XHDyh
name=username, value=ppmapp
name=principal, value=ppmapp
name=jaasSecurityDomain, value=jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword
2008-06-02 19:02:46,921 TRACE [org.jboss.security.plugins.JaasSecurityManager.EncryptedPPMEMSDbRealm] Login failure
javax.security.auth.login.LoginException: Failed to decode password: java.lang.NullPointerException
at org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule.commit(JaasSecurityDomainIdentityLoginModule.java:130)
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:324)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:535)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:480)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:431)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:246)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:664)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:495)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:887)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:159)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:143)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:420)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:155)
at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:337)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:884)
at $Proxy19.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:414)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy42.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:367)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:884)
at $Proxy19.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:414)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy15.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:570)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:821)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:884)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:414)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
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:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:145)
at org.jboss.Main$1.run(Main.java:399)
at java.lang.Thread.run(Thread.java:534)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155193#4155193
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155193
17 years, 10 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
nak(a)technodom.kz
17 years, 10 months
[JBoss Cache: Core Edition] - Problem using Non-JTA Transaction Manager
by mlamdin
We are seeking advice for sharing 2nd-level cache between cluster nodes using Tomcat, Spring, and Hibernate. If you have been successful doing this, we'd appreciate hearing from you.
We'd also appreciate learning about dead-ends we might avoid.
Our configuration:
-- Tomcat 6.0.14
-- Spring 2.0.4
-- Hibernate 3.2.5
-- Spring-supplied HibernateTransactionManager
-- JBoss Cache 1.4.1.SP9 (JBC)
Our experiences to date:
-- pessimistic locking and replication sync work well, except under
moderate load where we get ReplicationException's and missing
updates to the database.
-- async and invalidation_sync did not replicate our caches correctly
Specific questions we have:
Will it be possible to use JBC reliably using a non-JTA transaction manager such as HibernateTransactionManager?
If a JTA transaction manager should be used, which one would you recommend?
Thanks in advance for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155186#4155186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155186
17 years, 10 months
[Remoting] - Remoting 2.4.0.GA is now available
by ron.sigal＠jboss.com
JBossRemoting 2.4.0.GA is now available. This is a major incremental release, that resolves about 160 JIRA issues, including 76 bug fix issues and 28 feature issues. It is meant to be binary compatible with the previous major release, currently at 2.2.2.SP7, and configurably wire compatible with any release back to 1.4.3.GA.
Among the new features are:
- Support for multihome servers [JBREM-643]
- Safe to run with installed security manager [JBREM-934],[JBREM-977],[JBREM-978],
- Better support for IPv6 addresses [JBREM-864], [JBREM-865]
- Improved connection monitoring [JBREM-888], [JBREM-891]
- Server gets client address in invocations [JBREM-758]
- Support for server configuration by microcontainer injection [JBREM-63]
Support for multihome servers requires an extension of the InvokerLocator syntax. For example,
socket://multihome:6500/?homes=10.32.4.2!192.168.4.2
will create a server bound to 10.32.4.2 and 192.168.4.2.
The jboss-remoting.jar file is available at http://repository.jboss.com/jboss/remoting/
The complete distribution zip file is available at http://www.jboss.org/jbossremoting/downloads/ .
Feedback is welcome on the Remoting user forum: http://www.jboss.com/index.html?module=bb&op=viewforum&f=222.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155185#4155185
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155185
17 years, 10 months
[JBoss Cache: Core Edition] - Re: No transactionality in caches
by duncow
The comment above about making sure a transaction hasn't already started intrigues me.
We're using *pessimistic* locking, but we are also using Spring's HibernateTransactionManager (specifically, annotation-based declarative transaction management).
If we are not using HibernateTransactionManager to support optimistic locking, should we still be able to use HibernateTransactionManager with JBoss Cache in a clustered environment, for pessimistic locking? If JBoss Cache throws a ReplicationException, for example, shouldn't HibernateTransactionManager still roll back the transaction?
Because we are seeing ReplicationExceptions and cache inconsistency, even with pessimistic locking and replication sync, I am also wondering if we are on the wrong road entirely by attempting to use JBoss Cache without JTA, even with pessimistic locking.
We are running on
-- Tomcat 6.0.14
-- Spring 2.0.4
-- Hibernate 3.2.5
-- JBoss Cache 1.4.1.SP9
Thanks in advance for any insights.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155177#4155177
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155177
17 years, 10 months
