January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-1166) Possible race condition in ConnectionValidator

by Takayoshi Kimura (JIRA)

Possible race condition in ConnectionValidator ---------------------------------------------- Key: JBREM-1166 URL: https://jira.jboss.org/jira/browse/JBREM-1166 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP1, 2.2.3 Reporter: Takayoshi Kimura Fix For: 2.2.3.SP2 The 2.2.3 has a minor regression. The ConnectionValidator#start() has been moved outside of synchronized block in this release, this leads a race condition problem. ConnectionValidator#start(): TimerUtil.schedule(this, pingPeriod); // will call ConnectionValidator.run() timer = new Timer(true); // is used in ConnectionValidator.run() These 2 lines looks odd, because it initializes the timer for new thread after spawn the thread. In 2.2.2-SP11 the timer variable is protected by synchronized blocks, so it's not the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-6886) Upgrade to Remoting 2.5.2

by Ron Sigal (JIRA)

Upgrade to Remoting 2.5.2 ------------------------- Key: JBAS-6886 URL: https://jira.jboss.org/jira/browse/JBAS-6886 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Ron Sigal Will have some important changes to support JBossMessaging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
14
0 / 0

[JBoss JIRA] Created: (JBREM-1176) Fix classloader leak caused by client invoker destruction delay facility

by Ron Sigal (JIRA)

Fix classloader leak caused by client invoker destruction delay facility ------------------------------------------------------------------------ Key: JBREM-1176 URL: https://jira.jboss.org/jira/browse/JBREM-1176 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2.SP1 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2, 2.5.2.SP2 (Flounder) This issue was turned up by https://jira.jboss.org/jira/browse/JBPAPP-3193 "Regression in EAP 4.x testsuite in Ejb3ClassloaderLeakUnitTestCase". The problem is that org.jboss.remoting.Client creates a static java.util.Timer which is never deleted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-1175) URL-component-based InvokerLocator constructor generates incorrect locator string under IPv6

by Richard Achmatowicz (JIRA)

URL-component-based InvokerLocator constructor generates incorrect locator string under IPv6 --------------------------------------------------------------------------------------------- Key: JBREM-1175 URL: https://jira.jboss.org/jira/browse/JBREM-1175 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: unifiedinvoker Affects Versions: 2.2.3.SP1 Reporter: Richard Achmatowicz The constructor public InvokerLocator(String protocol, String host, int port, String path, Map parameters) creates a uri and originalURI from the component parts of the URL passed into it. This uri is incorrectly formed when the host is an IPv6 IP address literal, as square brackets need to be added to IPv6 URLs. NOTE: the other constructor public InvokerLocator(String uri) does work correctly in the non-lagacy parsing case as the method URIParse will parse a valid IPv6 URL into component parts using the URI constructor. This constructor parses an input URI string into component parts in such a way that the hostname will retain its square brackets if the URI represents a well formed IPv6 URL - and these square brackets do not need to be added when the string uri is reconstructed later on oin the method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-7450) Message consumer closing due to error in listening thread & Also message is not delete from the queue.

by Jay Prakash Dutta (JIRA)

Message consumer closing due to error in listening thread & Also message is not delete from the queue. ------------------------------------------------------------------------------------------------------ Key: JBAS-7450 URL: https://jira.jboss.org/jira/browse/JBAS-7450 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (JBossMQ) Affects Versions: JBossAS-4.2.2.GA Environment: Linux Reporter: Jay Prakash Dutta Assignee: Adrian Brock Hi, I have a process which puts a message on a queue and then reading message from queue and insert in DB. When it inserted to DB, it tries to close the queue, which it does successfully, but I quickly get: 16:19:26,429 WARN [SpyMessageConsumer] Message consumer closing due to error in listening thread. javax.jms.IllegalStateException: The session is closed at org.jboss.mq.SpySession.checkClosed(SpySession.java:1149) at org.jboss.mq.SpySession.doAcknowledge(SpySession.java:175) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:353) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:704) at java.lang.Thread.run(Thread.java:595) When I close the queue, I do a finally { if(qConnection!=null){ try { qConnection.close(); } catch (JMSException e) { // TODO Auto-generated catch block e.printStackTrace(); } } } What am I doing wrong, if anything? When I reading message from queue.I will Redelivered same Message. also message is not delete from the queue. 16 Nov 09 16:42:34,663]Thread specific :: Received Message: org.jboss.mq.SpyObjectMessage { Header { jmsDestination : QUEUE.Open_NMS_Evnet_Queue jmsDeliveryMode : 2 jmsExpiration : 0 jmsPriority : 4 jmsMessageID : ID:2-12583698243211 jmsTimeStamp : 1258369824321 jmsCorrelationID: null jmsReplyTo : null jmsType : null jmsRedelivered : true jmsProperties : {JMSXDeliveryCount=252, JMS_JBOSS_REDELIVERY_COUNT=251} jmsPropReadWrite: false msgReadOnly : true producerClientId: ID:2 } } I am awaiting your reply. Please Quick response Thanks & Regards Jay Prakash -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7449) Message consumer closing due to error in listening thread

by Jay Prakash Dutta (JIRA)

Message consumer closing due to error in listening thread --------------------------------------------------------- Key: JBAS-7449 URL: https://jira.jboss.org/jira/browse/JBAS-7449 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMS (JBossMQ) Affects Versions: JBossAS-4.2.2.GA Environment: Ubuntu 8.04,jboss-4.2.2.GA, Reporter: Jay Prakash Dutta Assignee: Adrian Brock Hi, I have a process which puts a message on a queue and then reading message from queue and insert in DB. When it inserted to DB, it tries to close the queue, which it does successfully, but I quickly get: 16:19:26,429 WARN [SpyMessageConsumer] Message consumer closing due to error in listening thread. javax.jms.IllegalStateException: The session is closed at org.jboss.mq.SpySession.checkClosed(SpySession.java:1149) at org.jboss.mq.SpySession.doAcknowledge(SpySession.java:175) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:353) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:704) at java.lang.Thread.run(Thread.java:595) When I close the queue, I do a finally { if(qConnection!=null){ try { qConnection.close(); } catch (JMSException e) { // TODO Auto-generated catch block e.printStackTrace(); } } } What am I doing wrong, if anything? When I reading message from queue.I will Redelivered same Message. also message is not delete from the queue. 16 Nov 09 16:42:34,663]Thread specific :: Received Message: org.jboss.mq.SpyObjectMessage { Header { jmsDestination : QUEUE.Open_NMS_Evnet_Queue jmsDeliveryMode : 2 jmsExpiration : 0 jmsPriority : 4 jmsMessageID : ID:2-12583698243211 jmsTimeStamp : 1258369824321 jmsCorrelationID: null jmsReplyTo : null jmsType : null jmsRedelivered : true jmsProperties : {JMSXDeliveryCount=252, JMS_JBOSS_REDELIVERY_COUNT=251} jmsPropReadWrite: false msgReadOnly : true producerClientId: ID:2 } } I am awaiting your reply. Please Quick response Thanks & Regards Jay Prakash -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7611) Remove Sun JDK14 isLocal bug fix

by Adrian Brock (JIRA)

Remove Sun JDK14 isLocal bug fix -------------------------------- Key: JBAS-7611 URL: https://jira.jboss.org/jira/browse/JBAS-7611 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: IIOP service Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.M2 Remove the use of org.jboss.iiop.SunJDK14IsLocalBugFix since JDK14 is no longer supported making this workaround redundant. The class can't even be compiled on JDK5+ so it is no longer included in the build or release anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-257) Integrate JBoss Stdio

by Jesper Pedersen (JIRA)

Integrate JBoss Stdio --------------------- Key: JBJCA-257 URL: https://jira.jboss.org/jira/browse/JBJCA-257 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha8 Integrate JBoss Stdio such that the logger for ManagedConnectionFactory#setLogWriter() is redirected to the logging framework. Also install replacements for System.in, System.out and System.err. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-256) JBoss Stdio 1.0.0.CR1

by Jesper Pedersen (JIRA)

JBoss Stdio 1.0.0.CR1 --------------------- Key: JBJCA-256 URL: https://jira.jboss.org/jira/browse/JBJCA-256 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7605) hibernate-validator-legacy.jar is needed for admin-console initialization

by Shelly McGowan (JIRA)

hibernate-validator-legacy.jar is needed for admin-console initialization ------------------------------------------------------------------------- Key: JBAS-7605 URL: https://jira.jboss.org/jira/browse/JBAS-7605 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: JBossAS-6.0.0.M2 hibernate-validator-legacy.jar needs to be added to common/lib. It was added to 6.0.0.M1 but not to trunk. See: JBAS-7271 I've had this implemented locally so filing this issue for tracking. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
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 January 2010