June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate

by Brian Stansberry (JIRA)

Remove EJBTHREE-798 workaround once issue is fixed in Hibernate --------------------------------------------------------------- Key: EJBTHREE-799 URL: http://jira.jboss.com/jira/browse/EJBTHREE-799 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-20) Map the jboss TRACE level logging to log4j TRACE

by Dimitris Andreadis (JIRA)

Map the jboss TRACE level logging to log4j TRACE ------------------------------------------------ Key: JBCOMMON-20 URL: http://jira.jboss.com/jira/browse/JBCOMMON-20 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-old, logging-log4j Affects Versions: 1.0.4.GA, 2.0.1.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA, 2.0.4.GA See JBAS-4163 -- 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
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-22) Revert JBCOMMON-20 for JBossCommon 1.0.x

by Dimitris Andreadis (JIRA)

Revert JBCOMMON-20 for JBossCommon 1.0.x ---------------------------------------- Key: JBCOMMON-22 URL: http://jira.jboss.com/jira/browse/JBCOMMON-22 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Components: common-old Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA JBCOMMON-20 needs to be reverted so that jboss common 1.0.5 can still be a drop-in-replacement that doesn't require a log4j upgrade. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4237) mail-ra should support encrypted connections

by Pete Muir (JIRA)

mail-ra should support encrypted connections -------------------------------------------- Key: JBAS-4237 URL: http://jira.jboss.com/jira/browse/JBAS-4237 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.0.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Javamail supports pop3s, imaps and imap/tls -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-761) NPE in BisocketServerInvoker$ControlConnectionThread

by Ron Sigal (JIRA)

NPE in BisocketServerInvoker$ControlConnectionThread ---------------------------------------------------- Key: JBREM-761 URL: http://jira.jboss.com/jira/browse/JBREM-761 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) >From Tim Fox: Here's one I saw today: @main 18:11:54,129 INFO [FailoverTest] tearing down Exception in thread "control: Socket[addr=/127.0.0.1,port=3243,localport=55075]" java.lang.NullPointerException at org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(BisocketServerInvoker.java:669) It seems pretty harmless, but nevertheless I thought I'd inform you. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBREM-757) Implement quick Client.removeListener() for polled callbacks.

by Ron Sigal (JIRA)

Implement quick Client.removeListener() for polled callbacks. ------------------------------------------------------------- Key: JBREM-757 URL: http://jira.jboss.com/jira/browse/JBREM-757 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) For JBREM-657, quick org.jboss.remoting.Client.disconnect() and quick Client.removeListener() facilities were implemented which impose a per invocation timeout on any network i/o that occurs during these methods. The per invocation timeout is set by calling Client.setDisconnectTimeout(). When the disconnect timeout is set to 0, network i/o is avoided entirely. However, the quick version of Client.removeListener() was implemented only for push callbacks. It should also be implemented for pull callbacks. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBREM-751) Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker

by Ron Sigal (JIRA)

Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker ------------------------------------------------------------------------------------------------ Key: JBREM-751 URL: http://jira.jboss.com/jira/browse/JBREM-751 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) In org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(), there is a try/catch block that catches IOExceptions. If the IOException is caused by a closed socket, then the thread quietly shuts down, instead of logging an error. However, the test "socket closed".equals(e.getMessage()) should have been "Socket closed".equals(e.getMessage()), and so an error is sometimes logged unnecessarily. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBREM-750) Logger in HTTPClientInvoker should be static.

by Ron Sigal (JIRA)

Logger in HTTPClientInvoker should be static. --------------------------------------------- Key: JBREM-750 URL: http://jira.jboss.com/jira/browse/JBREM-750 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized. The log variable should be static. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBREM-653) allow user to set content-type for http responses

by Tom Elrod (JIRA)

allow user to set content-type for http responses ------------------------------------------------- Key: JBREM-653 URL: http://jira.jboss.com/jira/browse/JBREM-653 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: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client. Should allow this to be overriden by the user in the same way the response code/message can be (using the response map). -- 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

3
13
0 / 0

[JBoss JIRA] Created: (JBREM-748) BisocketClientInvoker should guard agains scheduling on an expired Timer

by Ron Sigal (JIRA)

BisocketClientInvoker should guard agains scheduling on an expired Timer ------------------------------------------------------------------------ Key: JBREM-748 URL: http://jira.jboss.com/jira/browse/JBREM-748 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) In two places, org.jboss.remoting.transport.bisocket.BisocketClientInvoker schedules a PingTimerTask on the Timer referenced by the static variable timer. The problem is that if the Timer has been around for a while and all of its tasks have completed, it could have entered a state in which in can no longer schedule new tasks. -- 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
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007