[JBoss JIRA] (ISPN-1824) Cross-datacentre distribution
by Manik Surtani (JIRA)
Manik Surtani created ISPN-1824:
-----------------------------------
Summary: Cross-datacentre distribution
Key: ISPN-1824
URL: https://issues.jboss.org/browse/ISPN-1824
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.1.0.FINAL
Reporter: Manik Surtani
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
There are currently two designs for this:
1. Use JGroups' RELAY for master/master.
2. Use an Infinispan-only setup using Hot Rod and an async RemoteCacheStore
Both design patterns should be documented, tested, benchmarked. Should survive failures in relaying node, on either datacentre.
Initially test on 2 datacentres, and if possible on 3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (ISPN-2290) MBeans should be registered even if JMX statistics gathering is disabled
by Manik Surtani (JIRA)
Manik Surtani created ISPN-2290:
-----------------------------------
Summary: MBeans should be registered even if JMX statistics gathering is disabled
Key: ISPN-2290
URL: https://issues.jboss.org/browse/ISPN-2290
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 5.1.7.Final
Environment: JMX MBeans should still be registered with an MBean server even if statistics gathering is disabled, to allow for operations on a running grid. If an MBean server is not available though, this should be short-circuited.
Reporter: Manik Surtani
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4, 5.2.0.Final
--
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, 4 months
[JBoss JIRA] (ISPN-2305) ConcurrentCacheManagerTest might never finish
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2305:
--------------------------------------
Summary: ConcurrentCacheManagerTest might never finish
Key: ISPN-2305
URL: https://issues.jboss.org/browse/ISPN-2305
Project: Infinispan
Issue Type: Bug
Components: Core API
Reporter: Galder Zamarreño
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Alpha4
Most likely related to ISPN-2256 whose fix is already in...
{code}"testng-ConcurrentCacheManagerTest" prio=5 tid=7fb8ca077800 nid=0x115b97000 waiting on condition [115b95000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <7d5d373b8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.CyclicBarrier.dowait(CyclicBarrier.java:199)
at java.util.concurrent.CyclicBarrier.await(CyclicBarrier.java:327)
at org.infinispan.manager.ConcurrentCacheManagerTest.testConcurrentGetCacheCalls(ConcurrentCacheManagerTest.java:94){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, 4 months
[JBoss JIRA] (ISPN-2282) Custom Externalizers cause NotSerializableException
by Erik Salter (JIRA)
Erik Salter created ISPN-2282:
---------------------------------
Summary: Custom Externalizers cause NotSerializableException
Key: ISPN-2282
URL: https://issues.jboss.org/browse/ISPN-2282
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Since org.infinispan.marshall.Externalizer no longer extends Serializable, my custom Externalizers throw NotSerialazbleExceptions.
Example:
Caused by: org.infinispan.marshall.NotSerializableException: net.beaumaris.odrm.resmanagement.type.ODRMSessionData$ODRMSessionDataExternalizer
Caused by: an exception which occurred:
in field externalizer
in object org.infinispan.marshall.jboss.JBossExternalizerAdapter@2c370555
-> toString = org.infinispan.marshall.jboss.JBossExternalizerAdapter@2c370555
in object net.beaumaris.odrm.resmanagement.type.ODRMSessionData@62c91115
-> toString = ODRMSessionData [sopId=999991, segmentIndex=0, streamerId=99999]
in object org.infinispan.commands.write.PutKeyValueCommand@cf4d21f7
-> toString = PutKeyValueCommand{key=9d3d0a41-4d2a-4320-aa38-64a5203c49bf, value=ODRMSessionData [sopId=999991, segmentIndex=0, streamerId=99999], flags=[SKIP_REMOTE_LOOKUP], putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}
in object org.infinispan.commands.remote.SingleRpcCommand@280f4ad0
-> toString = SingleRpcCommand{cacheName='ODRM_SESSION', command=PutKeyValueCommand{key=9d3d0a41-4d2a-4320-aa38-64a5203c49bf, value=ODRMSessionData [sopId=999991, segmentIndex=0, streamerId=99999], flags=[SKIP_REMOTE_LOOKUP], putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}}
--
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, 4 months