May 2008 - jboss-remoting-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBREM-860) Eliminate delay in MicroSocketClientInvoker.getConnection()

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-860?page=all ] Ron Sigal reopened JBREM-860: ----------------------------- > Eliminate delay in MicroSocketClientInvoker.getConnection() > ----------------------------------------------------------- > > Key: JBREM-860 > URL: http://jira.jboss.com/jira/browse/JBREM-860 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection() currently calls Thread.sleep(1000) after each unsuccessful attempt to retrieve a connection from the connection pool. This introduced an unnecessary delay in general, and, in particular, makes the use of a connection pool of size one impractical. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal closed JBREM-858. --------------------------- Resolution: Done > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal reopened JBREM-858: ----------------------------- > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-855) Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-855?page=all ] Ron Sigal closed JBREM-855. --------------------------- Resolution: Done > Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4 > -------------------------------------------------------------------- > > Key: JBREM-855 > URL: http://jira.jboss.com/jira/browse/JBREM-855 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP4 > > > Fernando has suggested updating build.xml so that the *-brew scripts can use the jdk 1.5 compiler to generate code that is compatible with a 1.4 JVM. This way we have a single version of jboss-remoting.jar in the repository which is (1) appropriate in the current versions of the Application Server, which are compiled with jdk 1.5, and (2) usable in a standalone context by clients built with a jdk 1.4 compiler. > The changes should be applied to the following branches: > - remoting_2_2_0_GA (for community AS) > - remoting_2_2_2_GA_CP (for EAP 4.2 and 4.3) > - remoting_2_x (for Remoting 2.4.0) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal updated JBREM-858: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-870. > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-855) Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-855?page=all ] Ron Sigal reopened JBREM-855: ----------------------------- > Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4 > -------------------------------------------------------------------- > > Key: JBREM-855 > URL: http://jira.jboss.com/jira/browse/JBREM-855 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > Fernando has suggested updating build.xml so that the *-brew scripts can use the jdk 1.5 compiler to generate code that is compatible with a 1.4 JVM. This way we have a single version of jboss-remoting.jar in the repository which is (1) appropriate in the current versions of the Application Server, which are compiled with jdk 1.5, and (2) usable in a standalone context by clients built with a jdk 1.4 compiler. > The changes should be applied to the following branches: > - remoting_2_2_0_GA (for community AS) > - remoting_2_2_2_GA_CP (for EAP 4.2 and 4.3) > - remoting_2_x (for Remoting 2.4.0) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-855) Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-855?page=all ] Ron Sigal updated JBREM-855: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-868. > Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4 > -------------------------------------------------------------------- > > Key: JBREM-855 > URL: http://jira.jboss.com/jira/browse/JBREM-855 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP4 > > > Fernando has suggested updating build.xml so that the *-brew scripts can use the jdk 1.5 compiler to generate code that is compatible with a 1.4 JVM. This way we have a single version of jboss-remoting.jar in the repository which is (1) appropriate in the current versions of the Application Server, which are compiled with jdk 1.5, and (2) usable in a standalone context by clients built with a jdk 1.4 compiler. > The changes should be applied to the following branches: > - remoting_2_2_0_GA (for community AS) > - remoting_2_2_2_GA_CP (for EAP 4.2 and 4.3) > - remoting_2_x (for Remoting 2.4.0) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-852) Verify IPv6 addresses are handled correctly

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-852?page=all ] Ron Sigal updated JBREM-852: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-865. > Verify IPv6 addresses are handled correctly > ------------------------------------------- > > Key: JBREM-852 > URL: http://jira.jboss.com/jira/browse/JBREM-852 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > Need to make sure that Remoting can bind ServerSockets to IPv6 addresses. This issue is related to http://jira.jboss.com/jira/browse/JBREM-645. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-845) Infinite loop in BisocketClientInvoker.createSocket

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-845?page=all ] Ron Sigal closed JBREM-845. --------------------------- Resolution: Done > Infinite loop in BisocketClientInvoker.createSocket > --------------------------------------------------- > > Key: JBREM-845 > URL: http://jira.jboss.com/jira/browse/JBREM-845 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 > Reporter: Carlo de Wolf > Assigned To: Ron Sigal > Priority: Blocker > Fix For: 2.2.2.SP4 > > Attachments: console.log-4.txt, jboss-remoting.jar, jboss-remoting.jar, JBREM-845-3.txt, JBREM-845-4.txt, JBREM-845-5.txt, server-5.log, strictpool-shutdown-EAP-4.3.hang.txt > > > The following piece of code constitutes an infinite loop when timeout = 0: > while (timeout == 0 || wait > 0) > { > try > { > sockets.wait(wait); > break; > } > catch (InterruptedException e) > { > log.debug("unexpected interrupt"); > if (timeout > 0) > wait = timeout - (System.currentTimeMillis() - start); > } > } > "Thread-41" prio=1 tid=0x00002aaaac3cd0b0 nid=0x2e87 in Object.wait() [0x0000000048fe3000..0x0000000048fe3d80] > at java.lang.Object.wait(Native Method) > - waiting on <0x00002b7156e2f410> (a java.util.HashSet) > at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:458) > - locked <0x00002b7156e2f410> (a java.util.HashSet) > at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815) > at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525) > at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413) > at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) > at org.jboss.remoting.Client.invoke(Client.java:1634) > at org.jboss.remoting.Client.invoke(Client.java:548) > at org.jboss.remoting.Client.invokeOneway(Client.java:598) > at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815) > at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686) > at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1490) > - locked <0x00002b71569e25e8> (a org.jboss.remoting.transport.bisocket.BisocketClientInvoker) > at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1375) > - locked <0x00002b71569dfd40> (a org.jboss.jms.server.endpoint.ServerSessionEndpoint) > at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:307) > - locked <0x00002b71569ed6b0> (a java.lang.Object) > at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119) > at org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.java:582) > at org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistributor.java:79) > at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:476) > at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:505) > at org.jboss.messaging.core.impl.ChannelSupport.deliver(ChannelSupport.java:226) > - locked <0x00002b71565d3d50> (a java.lang.Object) > at org.jboss.jms.server.endpoint.ServerSessionEndpoint$2.run(ServerSessionEndpoint.java:1598) > at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) > at java.lang.Thread.run(Thread.java:595) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-852) Verify IPv6 addresses are handled correctly

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-852?page=all ] Ron Sigal closed JBREM-852. --------------------------- Resolution: Done > Verify IPv6 addresses are handled correctly > ------------------------------------------- > > Key: JBREM-852 > URL: http://jira.jboss.com/jira/browse/JBREM-852 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4 > > > Need to make sure that Remoting can bind ServerSockets to IPv6 addresses. This issue is related to http://jira.jboss.com/jira/browse/JBREM-645. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues May 2008