January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1270) Commit messages to be broadcast as out-of-band messages so they are not blocked on the receiver's end

by Manik Surtani (JIRA)

Commit messages to be broadcast as out-of-band messages so they are not blocked on the receiver's end ----------------------------------------------------------------------------------------------------- Key: JBCACHE-1270 URL: http://jira.jboss.com/jira/browse/JBCACHE-1270 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Replication Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Would require a new method in RPCManager to be able to callRemoteMethods() with an OOB parameter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1269) Sample buddy replication configuration file should use TCP+MPING, not UDP.

by Manik Surtani (JIRA)

Sample buddy replication configuration file should use TCP+MPING, not UDP. -------------------------------------------------------------------------- Key: JBCACHE-1269 URL: http://jira.jboss.com/jira/browse/JBCACHE-1269 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-227) BaseClassLoaderDomain.getResource() should look at local classloader first before searching the repository

by Adrian Brock (JIRA)

BaseClassLoaderDomain.getResource() should look at local classloader first before searching the repository ---------------------------------------------------------------------------------------------------------- Key: JBMICROCONT-227 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-227 Project: JBoss MicroContainer Issue Type: Bug Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.Beta10 Currently the BaseClassLoaderDomain searches the domain before seeing whether the resource is available in the requesting classloader. This is not backwards compatible with the UnifiedClassLoader and it is obviously preferable to use local resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5101) Re-enable JGroups message bundling

by Brian Stansberry (JIRA)

Re-enable JGroups message bundling ---------------------------------- Key: JBAS-5101 URL: http://jira.jboss.com/jira/browse/JBAS-5101 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should re-enable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor

by Jacek Halat (JIRA)

Endless loop in PessimisticLockInterceptor ------------------------------------------ Key: JBCACHE-1165 URL: http://jira.jboss.com/jira/browse/JBCACHE-1165 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP4 Environment: Windows XP, Sun jdk150_06 Solaris 10 Reporter: Jacek Halat Assigned To: Manik Surtani When 2 Threads are simulatanous putting/removing values from this same node TreeCache hang's up and goes into endless loop. Main loop looks like: for (int x = 0; x < 1000; x++) { tm.begin(); System.out.println("R" + Thread.currentThread().getName()); //inside transaction cache.remove("/a"); System.out.println("AR" + Thread.currentThread().getName()); tm.commit(); //outside transaction System.out.println("P" + Thread.currentThread().getName()); cache.put("/a/b/c/d", "text"+x,"b"); System.out.println("AP" + Thread.currentThread().getName()); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

5
19
0 / 0

[JBoss JIRA] Created: (JBAS-5164) Generic ProxyFactoryHA leaves proxy in JNDI after undeploy

by Brian Stansberry (JIRA)

Generic ProxyFactoryHA leaves proxy in JNDI after undeploy ---------------------------------------------------------- Key: JBAS-5164 URL: http://jira.jboss.com/jira/browse/JBAS-5164 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta4 An HA proxy created using org.jboss.proxy.generic.ProxyFactoryHA will get left in JNDI following undeploy of the target service (and of the proxy factory itself). This is because after the factory removes the proxy in stopService(), it remains as a listener for DRM events. When it then destroys the HATarget, the target notifies the DRM, which calls back into the proxy via it's listener. The listener rebinds the proxy into JNDI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4997) Package StatefulPassivationActivationUnitTestCase with its own HAPartition

by Brian Stansberry (JIRA)

Package StatefulPassivationActivationUnitTestCase with its own HAPartition -------------------------------------------------------------------------- Key: JBAS-4997 URL: http://jira.jboss.com/jira/browse/JBAS-4997 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor This test does thousands of invocations from a single thread. This makes it prone to timeout if nagling or JGroups message bundling are enabled on the HAPartition channel, since the single thread doesn't generate enough *concurrent* load to trigger prompt message transmission. We should deploy the test with a partition with its own channel so we don't have to factor this test into whether or not we want nagling/bundling on the standard channel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBRULES-46) Backward Chaining

by kk Kailasam (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-46?page=comments#action_12396173 ] kk Kailasam commented on JBRULES-46: ------------------------------------ Will this feature be available in 5.0? Thanks. > Backward Chaining > ----------------- > > Key: JBRULES-46 > URL: http://jira.jboss.com/jira/browse/JBRULES-46 > Project: JBoss Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Mark Proctor > > Forward Chaining means that facts are asserted and propgated forward throughout the network, during forward propagation matching takes place which results in rules being fired - the rules are event based, in that they are fired in response to changed in the working memory. > Backward chaining is query based. Rules attempt to fire first but do not have the necessary matched facts, so facts are pulled in from an external source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1231) Implicit use of MarshalledValues in the cache

by Manik Surtani (JIRA)

Implicit use of MarshalledValues in the cache --------------------------------------------- Key: JBCACHE-1231 URL: http://jira.jboss.com/jira/browse/JBCACHE-1231 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA, 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Do not use region-based marshalling in the CacheMarshaller; instead, allow for implicit MarshalledValues in the cache which capture the thread's context class loader when an object is inserted into the cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-664) CopyOnWrite collections should be synchronized

by Bela Ban (JIRA)

CopyOnWrite collections should be synchronized ---------------------------------------------- Key: JGRP-664 URL: http://jira.jboss.com/jira/browse/JGRP-664 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.2, 2.6.2, 2.7 [email from Rick Pike] Sometimes when we have nodes start suspecting each other we see intermittent: 2008-01-14 06:49:37,464 [ERROR] UDP failed handling incoming message java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.concurrent.CopyOnWriteArrayList.rangeCheck(CopyOnWriteArrayList.java:708) at java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:328) at org.jgroups.protocols.FD.getPingDest(FD.java:151) at org.jgroups.protocols.FD.up(FD.java:305) at org.jgroups.protocols.FD_ICMP.up(FD_ICMP.java:108) at org.jgroups.protocols.MERGE3.up(MERGE3.java:126) at org.jgroups.protocols.Discovery.up(Discovery.java:246) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1535) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1484) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) It looks like there's 4 places in FD that modify the pingable_mbrs list: 1. up(HEARTBEAT_ACK) 2. up(SUSPECT) 3. down(VIEW_CHANGE) 4. down(UNSUSPECT) Only #1 and #3 appear to synchronize{} around the edits, and I believe that a concurrent (UN)SUSPECT message is emptying that list whille the HEARTBEAT_ACK is looping and repeatedly reading - inside getPingDest(). Every so often, it calls get(0) on an empty list. We just started seeing this when we started testing with FD_ICMP, but I imagine this would happen with any flavor, and we're seeing it due to the high volume of SUSPECT messages happening in our tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008