June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-642) Socket.setReuseAddress() in MicroSocketClientInvoker invocation is ignored

by Dejan Predovic (JIRA)

Socket.setReuseAddress() in MicroSocketClientInvoker invocation is ignored -------------------------------------------------------------------------- Key: JBREM-642 URL: http://jira.jboss.com/jira/browse/JBREM-642 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Reporter: Dejan Predovic Assigned To: Tom Elrod For Socket.setReuseAddress() to do anything it needs to be invoked before the socket is bound. Creating a socket with new Socket(host, port) automatically binds it, so there is no way to do it protected Socket createSocket(String address, int port) throws IOException { return new Socket(address, port); } needs to be changed to use the default constructor, invoke setReuseAddress() and then bind(). -- 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

18 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBREM-629) NPE in sending notification of lost client

by Tom Elrod (JIRA)

NPE in sending notification of lost client ------------------------------------------ Key: JBREM-629 URL: http://jira.jboss.com/jira/browse/JBREM-629 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Alpha3 (Bluto) Is possible to sometimes get null pointer exception when calling notifier to alert of lost client when leasing. 10:47:10,508 ERROR [STDERR] Exception in thread "Timer-2" 10:47:10,509 ERROR [STDERR] java.lang.NullPointerException 10:47:10,513 ERROR [STDERR] at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) 10:47:10,513 ERROR [STDERR] at org.jboss.remoting.Lease.access$300(Lease.java:39) 10:47:10,513 ERROR [STDERR] at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242) 10:47:10,513 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:527) 10:47:10,513 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:477) -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-607) Add idle timeout setting for invoker threads

by Galder Zamarreno (JIRA)

Add idle timeout setting for invoker threads -------------------------------------------- Key: JBREM-607 URL: http://jira.jboss.com/jira/browse/JBREM-607 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Tom Elrod An idle timeout minutes setting so that any unused threads are removed. It needs to have the possibility of disabling 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

18 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBREM-624) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBREM-624 URL: http://jira.jboss.com/jira/browse/JBREM-624 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Tom Elrod Fix For: 2.2.0.Alpha3 (Bluto) Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

18 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBREM-606) patch to 1.4.4.GA to include fix for socket server thread leak

by Tom Elrod (JIRA)

patch to 1.4.4.GA to include fix for socket server thread leak -------------------------------------------------------------- Key: JBREM-606 URL: http://jira.jboss.com/jira/browse/JBREM-606 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 1.4.4.GA Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 1.4.5.GA Need to back port fix for JBREM-409. -- 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

18 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-614) Client.invoke() should check isConnected().

by Ron Sigal (JIRA)

Client.invoke() should check isConnected(). ------------------------------------------- Key: JBREM-614 URL: http://jira.jboss.com/jira/browse/JBREM-614 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) This changed due to a leasing bug that Clebert found within messaging. The problem was that the isConnected() calls on it's invoker to see if it is connected (assuming the invoker is not null). So is possible that another Client is using the same client invoker and that invoker is already connected. This would cause the new Client to not set up leasing (which it would need to do). I guess the isConnected() call could be added back in, but would need to change the Client.isConnected() to use an member variable keeping track of state (connect or not connected) instead of calling on the invoker to see if it's connect. Ron Sigal wrote: > Hi Tom, > > I noticed something about Client.connect() and CallbackPoller.start(). In particular, CallbackPoller.start() calls Client.connect(), as it should. If leasing is configured, the Client will be registered with the LeasePinger. When the application calls Client.connect(), the Client will be re-registered with the LeasePinger. It doesn't cause an error, but it's a bit redundant. Looks like Client.connect() should start with > > if (isConnected()) > return; > > ?? > > -Ron -- 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

18 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBREM-604) allow socket server invoker to accept third party requests

by Tom Elrod (JIRA)

allow socket server invoker to accept third party requests ---------------------------------------------------------- Key: JBREM-604 URL: http://jira.jboss.com/jira/browse/JBREM-604 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The http server invoker (i.e. CoyoteInvoker) allows thirdparty clients to make requests and process those requests and return raw response from handler. Really no reason that the socket server invoker could not do this as well so that someone could write their own socket client and send raw data to the socket server invoker. -- 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

18 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-622) InvokerLocator already exists for listener

by Galen Dunkleberger (JIRA)

InvokerLocator already exists for listener ------------------------------------------ Key: JBREM-622 URL: http://jira.jboss.com/jira/browse/JBREM-622 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.0.5.GA JBoss Messaging 1.0.1.GA Linux BEA Jrockit R26.0.0-jdk1.5.0_04_x86_64 Reporter: Galen Dunkleberger Assigned To: Tom Elrod When trying to send many small messsages very quickly through JBoss messaging I was getting the following error javax.jms.IllegalStateException: InvokerLocator already exists for listener id 1436420135. Remove t his listener before adding again. at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:91) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe legate_N6840474864420126404.java:???) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe legate_N6840474864420126404.java:???) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(Lj ava.lang.String;Ljava.lang.String;)Lorg.jboss.jms.delegate.ConnectionDelegate;(ClientConnectionFacto ryDelegate.java:???) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFacto ry.java:202) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory. java:108) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory. java:103) -- 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

18 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBREM-590) SSL client socket invoker does not use configuration map for SSLSocketBuilder

by Tom Elrod (JIRA)

SSL client socket invoker does not use configuration map for SSLSocketBuilder ----------------------------------------------------------------------------- Key: JBREM-590 URL: http://jira.jboss.com/jira/browse/JBREM-590 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: security Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) When SSLSocketClientInvoker creates its socket factory (see SSLSocketClientInvoker.createSocketFactory(Map configuration)), it does not pass the configuration map to the SSLSocketBuilder. Therefore the SSLSocketBuilder is not able to create custom socket factory based on configuration. -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-586) socket client invoker connection pooling not bounded

by Tom Elrod (JIRA)

socket client invoker connection pooling not bounded ---------------------------------------------------- Key: JBREM-586 URL: http://jira.jboss.com/jira/browse/JBREM-586 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Due to code change for JBREM-576, the socket client invoker's bounded connection pooling was broken and the pool became unbounded (due to reducing the scope of the pool being sychronized within MicroSocketClientInvoker.getConnection(). The fix for JBREM-576 needs to remain (so do not get dealock on disconnect of one client invoker while another is still in use). However, will also need to synchronize the increase/decrease of number of pooled connections in use. -- 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

18 years, 10 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007