June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-673) Use of java.util.Timer recently added and not set to daemon, so applications not exiting

by Tom Elrod (JIRA)

Use of java.util.Timer recently added and not set to daemon, so applications not exiting ---------------------------------------------------------------------------------------- Key: JBREM-673 URL: http://jira.jboss.com/jira/browse/JBREM-673 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.0.Alpha5 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Critical Fix For: 2.2.0.Alpha6 -- 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
5
0 / 0

[JBoss JIRA] Created: (JBREM-700) NPE in AbstractDetector

by Tom Elrod (JIRA)

NPE in AbstractDetector ----------------------- Key: JBREM-700 URL: http://jira.jboss.com/jira/browse/JBREM-700 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: detection Affects Versions: 2.2.0.Alpha6 Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Within method: protected boolean isRemoteDetection(Detection detection) will check for String domain = detection.getIdentity().getDomain(); -- 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-656) Creating a client inside a ConnectionListener might lead into Lease reference counting problems

by Clebert Suconic (JIRA)

Creating a client inside a ConnectionListener might lead into Lease reference counting problems ----------------------------------------------------------------------------------------------- Key: JBREM-656 URL: http://jira.jboss.com/jira/browse/JBREM-656 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha4, 2.2.0.Alpha3 (Bluto) Reporter: Clebert Suconic Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Look at the duplicate issue on Messaging for more information. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBREM-660) create local transport

by Tom Elrod (JIRA)

create local transport ---------------------- Key: JBREM-660 URL: http://jira.jboss.com/jira/browse/JBREM-660 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4 Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Need to create an explicit local transport that does not create any network 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-659) Java 6 and ClassLoader.loadClass()

by Jan Bares (JIRA)

Java 6 and ClassLoader.loadClass() ---------------------------------- Key: JBREM-659 URL: http://jira.jboss.com/jira/browse/JBREM-659 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: Java 1.6.0-b105 Reporter: Jan Bares Assigned To: Tom Elrod The ClassLoader.loadClass() should be used only for plain classes, not for arrays etc. In ObjectInputStreamWithClassLoader.resolveClass() call: return Class.forName(v.getName(), false, cl); The problem is described at: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500212 http://forums.java.net/jive/thread.jspa?threadID=15823&tstart=0 The bug was found in JBoss AS 4.0.5.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

18 years, 10 months

6
13
0 / 0

[JBoss JIRA] Created: (JBREM-655) rename server thread when new socket connection comes in

by Tom Elrod (JIRA)

rename server thread when new socket connection comes in -------------------------------------------------------- Key: JBREM-655 URL: http://jira.jboss.com/jira/browse/JBREM-655 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4, 1.4.5.GA, 2.0.0.GA (Boon), 1.4.4.GA, 1.4.3.GA Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The ServerThread used to process incoming client requests for the socket server invoker will name the thread based on client address associated with socket connection. However, this address is not updated after the initial client request, so if the server thread is woken up and given a different client socket connection, will not re-name to the client address of for the new socket connection. -- 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-648) Client.disconnect without clearing ConnectionListeners will cause NPEs

by Clebert Suconic (JIRA)

Client.disconnect without clearing ConnectionListeners will cause NPEs ---------------------------------------------------------------------- Key: JBREM-648 URL: http://jira.jboss.com/jira/browse/JBREM-648 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Clebert Suconic Assigned To: Tom Elrod ConnectionValidator should be stoped when disconnected is called. ConnectionValidator::run will fail at this line if ConnectionValidator is not stopped: public void run() { try { boolean isValid = checkConnection(client.getInvoker().getLocator(), client.getConfiguration()); The fix should be simple though: public void disconnect() { if (invoker != null) { if(enableLease) { invoker.terminateLease(sessionId); enableLease = false; } if (validator!=null) // /this is the fix..... { validator.stop(); } -- 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
10
0 / 0

[JBoss JIRA] Created: (JBREM-638) 2.2.0.Alpha4 release

by Ron Sigal (JIRA)

2.2.0.Alpha4 release -------------------- Key: JBREM-638 URL: http://jira.jboss.com/jira/browse/JBREM-638 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha4 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Alpha4 Release 2.2.0.Alpha4 represents just a few changes from 2.2.0.Alpha3. 1. JBREM-635: affects org.jboss.remoting.marshal.http.HTTPUnMarshaller (Remove warning message in read().) 2. JBREM-636: affects org.jboss.remoting.callback.ServerInvokerCallbackHandler (init() stores the sessionId and listenerId for future reference, so that getId() does not have to refer to the initial InvocationRequest.) 3. JBREM-605: affects org.jboss.remoting.Client (Added test for consistency of listenerIds in acknowledgeCallbacks().) -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-626) Allow unmarshalling of HTTP response with error code 500

by Thomas Diesler (JIRA)

Allow unmarshalling of HTTP response with error code 500 -------------------------------------------------------- Key: JBREM-626 URL: http://jira.jboss.com/jira/browse/JBREM-626 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Tom Elrod >From the BasicProfile // R1126 An INSTANCE MUST return a "500 Internal Server Error" HTTP status code // if the response envelope is a Fault. Caused by: org.jboss.remoting.transport.http.WebServerError: Error received when calling on web server. Error returned was 500 at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:272) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:94) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125) at org.jboss.remoting.Client.invoke(Client.java:589) at org.jboss.remoting.Client.invoke(Client.java:581) at org.jboss.ws.soap.SOAPConnectionImpl.callInternal(SOAPConnectionImpl.java:201) /home/tdiesler/svn/jbossws/trunk/src/test [tdiesler@tddell test]$ ant -Dtest=jaxws/jsr181/webmethod test tests-main: [junit] Running org.jboss.test.ws.jaxws.jsr181.webmethod.JSR181WebMethodTestCase [junit] Tests run: 4, Failures: 0, Errors: 2, Time elapsed: 4.094 sec [junit] Test org.jboss.test.ws.jaxws.jsr181.webmethod.JSR181WebMethodTestCase FAILED -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-637) add tomcat jar to component-info.xml for remoting release

by Tom Elrod (JIRA)

add tomcat jar to component-info.xml for remoting release --------------------------------------------------------- Key: JBREM-637 URL: http://jira.jboss.com/jira/browse/JBREM-637 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: external Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The current remoting releases in repository.jboss.com don't include tomcat jars in their component-info.xml files. This is mainly because they are not required for all remoting transports (i.e. only http remoting server requres these jars). However, probably good to list them in some form or another. The current tomcat jar version are Tomcat 5.5.15. -- 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
3
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