[JBoss JIRA] Created: (JGRP-1338) MERGE2: ConcurrentModificationException
by Bela Ban (JIRA)
MERGE2: ConcurrentModificationException
---------------------------------------
Key: JGRP-1338
URL: https://issues.jboss.org/browse/JGRP-1338
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.12.2, 3.1
2011-06-23 16:54:04,826 DEBUG [org.jgroups.protocols.pbcast.GMS] (testng-.SyncDistLockingTest) exception=java.util.ConcurrentModificationException, retrying
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:810)
at java.util.HashMap$KeyIterator.next(HashMap.java:845)
at java.util.AbstractSet.removeAll(AbstractSet.java:174)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:163)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:343)
at org.jgroups.protocols.FD.down(FD.java:285)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:70)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:634)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:443)
at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:309)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:599)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:519)
at org.jgroups.protocols.pbcast.ClientGmsImpl.installView(ClientGmsImpl.java:246)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:180)
at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:38)
at org.jgroups.protocols.pbcast.GMS.down(GMS.java:925)
at org.jgroups.protocols.FC.down(FC.java:435)
at org.jgroups.protocols.FRAG2.down(FRAG2.java:155)
at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:324)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1081)
at org.jgroups.JChannel.downcall(JChannel.java:1680)
at org.jgroups.JChannel.connect(JChannel.java:425)
at org.jgroups.JChannel.connect(JChannel.java:388)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:158)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:149)
at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:911)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:709)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:611)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:176)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:171)
at org.infinispan.CacheImpl.start(CacheImpl.java:366)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:559)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:455)
at org.infinispan.test.MultipleCacheManagersTest.createClusteredCaches(MultipleCacheManagersTest.java:277)
at org.infinispan.replication.SyncReplLockingTest.createCacheManagers(SyncReplLockingTest.java:64)
at org.infinispan.test.MultipleCacheManagersTest.callCreateCacheManagers(MultipleCacheManagersTest.java:95)
at org.infinispan.test.MultipleCacheManagersTest.createBeforeMethod(MultipleCacheManagersTest.java:104)
at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:494)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121)
at org.testng.TestRunner.runWorkers(TestRunner.java:909)
at org.testng.TestRunner.privateRun(TestRunner.java:618)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] (JGRP-1372) RELAY tag on UDP Stack
by Vítor Corrêa (Created) (JIRA)
RELAY tag on UDP Stack
-----------------------
Key: JGRP-1372
URL: https://issues.jboss.org/browse/JGRP-1372
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1, 2.12
Environment: SO: redhat enterprise linux 6
JBoss 6.0.0-Final
Reporter: Vítor Corrêa
Assignee: Bela Ban
When i try to start a cluster with <RELAY /> tag on <UDP> stack it doesnt create a channel, and i get the following message.
13:17:51,977 ERROR [JGroupsTransport] Errors instantiating [org.jboss.ha.ispn.DefaultCacheContainerFactory$ChannelFactoryChannelLookup]! Not using a channel lookup.
13:17:51,984 INFO [JGroupsTransport] Unable to use any JGroups configuration mechanisms provided in properties {channelLookup=org.jboss.ha.ispn.DefaultCacheContainerFactory$ChannelFactoryChannelLookup, stack=udp, channelFactory=org.jboss.ha.framework.server.JChannelFactory@47dce809, channelId=defaultGroup-HAPartition}. Using default JGroups configuration!
13:17:52,115 INFO [JChannel] JGroups version: 2.12.1.Final
--
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
14 years, 9 months
[JBoss JIRA] Created: (JBAS-9264) BoundedQueueThreadPoolService provides Executor instead of ExecutorService
by Paul Ferraro (JIRA)
BoundedQueueThreadPoolService provides Executor instead of ExecutorService
--------------------------------------------------------------------------
Key: JBAS-9264
URL: https://issues.jboss.org/browse/JBAS-9264
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Ferraro
Currently, there is no thread service that provides a j.u.c.ExecutorService using a bounded queue thread pool.
The existing BoundedQueueThreadPoolService only provides a j.u.c.Executor, instead of the far more useful j.u.c.ExecutorService. The exposed j.u.c.Executor cannot even be cast to an j.u.c.ExecutorService, since the underlying QueueExecutor is wrapped by a decorator that does not implement j.u.c.ExecutorService.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-3205) Add 'name' and 'description' attributes to <Resource> element in change-sets
by Esteban Aliverti (JIRA)
Add 'name' and 'description' attributes to <Resource> element in change-sets
----------------------------------------------------------------------------
Key: JBRULES-3205
URL: https://issues.jboss.org/browse/JBRULES-3205
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Esteban Aliverti
Assignee: Esteban Aliverti
Priority: Optional
Fix For: 5.4.0.Beta1
It would be good the possibility to add (a optional) 'name' and 'description' to each Resource in change-set. These attribute should be exposed by org.drools.io.Resource
Even if these attributes don't have any effect in Resource's behavior and functionality, they will server as documentation of the change-set.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-3197) simple declaration flagged in RHS code, dialect "mvel"
by Wolfgang Laun (JIRA)
simple declaration flagged in RHS code, dialect "mvel"
------------------------------------------------------
Key: JBRULES-3197
URL: https://issues.jboss.org/browse/JBRULES-3197
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.3.0.Beta1
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.3.0.CR1
The declaration of variable i is flagged as an error, with
a funny error message: variable defined within scope: i,
as if there ever were a variable that is *not* defined
within its scope!
Expected behaviour is to accept this declaration.
rule KickOff
dialect "mvel"
when
then
int i;
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months