[JBoss JIRA] (ISPN-3954) Use Hibernate's StatelessSession for the JPACacheStore
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-3954?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-3954:
-----------------------------------
>From Hibernate docs:
{quote}
Collections are ignored by a stateless session
{quote}
Doesn't this mean that if I have entity with @ElementCollection, the collection won't get loaded/updated?
> Use Hibernate's StatelessSession for the JPACacheStore
> ------------------------------------------------------
>
> Key: ISPN-3954
> URL: https://issues.jboss.org/browse/ISPN-3954
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Reporter: Emmanuel Bernard
> Assignee: Radim Vansa
> Labels: 630
>
> The current model uses the regular session even though operations are tailored toward actions (insert, update, delete).
> It would be better to make use of the Hibernate StatelessSession API which has been designed for these use cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4176) Forcing a commit via recovery RecoveryAdminOperations may create a duplicate GlobalTransaction
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4176:
----------------------------------
Summary: Forcing a commit via recovery RecoveryAdminOperations may create a duplicate GlobalTransaction
Key: ISPN-4176
URL: https://issues.jboss.org/browse/ISPN-4176
Project: Infinispan
Issue Type: Bug
Components: Core, Transactions
Affects Versions: 6.0.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.0.0.Alpha3
{{RecoveryManagerImpl.forceTransactionCompletion()}} modifies the {{GlobalTransaction.address}} of the transaction being committed so that the local node is the originator. But the {{GlobalTransaction.id}} stays the same, we could have two transactions with the same {{GlobalTransaction}} - which shouldn't be possible.
We can't remove the code that changes the {{GlobalTransaction.address}}, because we use it as the originator in other parts of the code. So the only option is to generate a new id as well.
But there is another problem: RecoveryAwareTransactionTable.cleanupStaleTransactions() doesn't release the locks acquired by that transaction on the primary node. So forcing a commit with a different GlobalTransaction will not be able to acquire the locks that were held by the original transaction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4175) Initialisation of remote query module fails randomly due to ClusterRegistry not bein initialised
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-4175:
-----------------------------------
Summary: Initialisation of remote query module fails randomly due to ClusterRegistry not bein initialised
Key: ISPN-4175
URL: https://issues.jboss.org/browse/ISPN-4175
Project: Infinispan
Issue Type: Bug
Components: Remote Querying
Affects Versions: 6.0.0.Final
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 7.0.0.Final
{code}
11:47:01,852 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.infinispan.clustered.memcachedCache: org.jboss.msc.service.StartException in service jboss.infinispan.clustered.memcachedCache: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: No registered default factory for component 'interface org.infinispan.registry.ClusterRegistry' found!. To get more detail set the system property infinispan.debugDependencies to true
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:241)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:546)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:517)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:399)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:413)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
... 3 more
Caused by: org.infinispan.commons.CacheConfigurationException: No registered default factory for component 'interface org.infinispan.registry.ClusterRegistry' found!. To get more detail set the system property infinispan.debugDependencies to true
at org.infinispan.factories.AbstractComponentRegistry.throwStackAwareConfigurationException(AbstractComponentRegistry.java:884)
at org.infinispan.factories.AbstractComponentRegistry.getFactory(AbstractComponentRegistry.java:299)
at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:270)
at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:227)
at org.infinispan.factories.AbstractComponentRegistry.access$000(AbstractComponentRegistry.java:65)
at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:797)
at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:201)
at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:156)
at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:148)
at org.infinispan.query.remote.LifecycleManager.initProtobufMetadataManager(LifecycleManager.java:56)
at org.infinispan.query.remote.LifecycleManager.cacheManagerStarted(LifecycleManager.java:70)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:228)
... 12 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years