December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-1165) Reduce log level of ""received new control socket for unrecognized listenerId" message

by Ron Sigal (JIRA)

Reduce log level of ""received new control socket for unrecognized listenerId" message -------------------------------------------------------------------------------------- Key: JBREM-1165 URL: https://jira.jboss.org/jira/browse/JBREM-1165 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.2.3.SP2, 2.5.2.SP1 (Flounder) This message indicates that, in the process of shutting removing a bisocket callback connection, the server side has been removed before the client side. Just before it gets shut down, the org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlMonitorTimerTask has missed a control connection ping and tries to recreate the control connection. It's just a timing issue and the log message should be reduced from ERROR to INFO. -- 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

15 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-1168) CoyoteInvoker.normalize() should handle empty URLs

by Ron Sigal (JIRA)

CoyoteInvoker.normalize() should handle empty URLs -------------------------------------------------- Key: JBREM-1168 URL: https://jira.jboss.org/jira/browse/JBREM-1168 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2, 2.5.2.SP1 (Flounder) When, for some reason, tomcat passes an empty URL to org.jboss.remoting.transport.coyote.CoyoteInvoker, the normalize() method throws an ArrayIndexOutOfBoundsException. The problem should be handled more gracefully. -- 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

15 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1164) Remoting shouldn't require IPv6 addresses to be surrounded by brackets

by Ron Sigal (JIRA)

Remoting shouldn't require IPv6 addresses to be surrounded by brackets ---------------------------------------------------------------------- Key: JBREM-1164 URL: https://jira.jboss.org/jira/browse/JBREM-1164 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP1 (Flounder) Although IPv6 addresses are surrounded by brackets in URLs, the addresses themselves don't have brackets. Thus, it should be possible to start the Application Server with run.sh -b ::1 instead of requiring run.sh -b [::1] -- 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

15 years, 9 months

3
17
0 / 0

[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

15 years, 9 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

15 years, 9 months

3
14
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

15 years, 9 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2281) Perf issue when many user dashboard

by Thomas Heute (JIRA)

Perf issue when many user dashboard ----------------------------------- Key: JBPORTAL-2281 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2281 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Heute On 'configure dashboard' when many users have a dashboard performance can drop considerably -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBID-217) STSSecurityHandler: Improve exception/fault handling.

by Daniel Bevenius (JIRA)

STSSecurityHandler: Improve exception/fault handling. ----------------------------------------------------- Key: JBID-217 URL: https://jira.jboss.org/jira/browse/JBID-217 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Improve the exception handling in this class. Currently only a WebServiceException is thrown from the handleMessage method. Use the appropriate fault codes that are defined in WS-Security for handling execptions in this handler: UnsupportedSecurityToken InvalidSecurity InvalidSecurityToken FailedAuthentication FailedCheck SecurityTokenUnavailable -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-232) War's metadata location is used too broadly

by Ales Justin (JIRA)

War's metadata location is used too broadly ------------------------------------------- Key: JBDEPLOY-232 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-232 Project: JBoss Deployers Issue Type: Task Affects Versions: JBDEPLOY-2.0.8.SP1 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.0.9.GA, JBDEPLOY-2.1.0.Alpha1 When adding .war libs metadata locations as deployment's metadata locations, we can stumble upon unexpected behavior; see forum for more details. We need to limit the usage of alternative metadata locations. e.g. diff between default and alternative -- JEE EJB might also pick up from alternative -- 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

15 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009