jboss-jira July 2010

jboss-jira@lists.jboss.org

1 participants
1585 discussions

[JBoss JIRA] Created: (JBMESSAGING-1809) Fix closed connection check in ClientSocketWrapper

by Ron Sigal (JIRA)

Fix closed connection check in ClientSocketWrapper -------------------------------------------------- Key: JBMESSAGING-1809 URL: https://jira.jboss.org/browse/JBMESSAGING-1809 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP10 Reporter: Ron Sigal Two problems have turned up in the closed connection checking mechanisms: 1. A regression in the default connection checking mechanism entered in JBMESSAGING-1737 "Update ClienSocketWrapper": When an instance of org.jboss.jms.client.remoting.ServerSocketWrapper closes, it writes a single org.jboss.jms.client.remoting.ClientSocketWrapper.CLOSING byte, and, prior to JBMESSAGING-1737, ClientSocketWrapper checked for the presence of >0 available bytes. However, I created a new version of ClientSocketWrapper for JBMESSAGING, based on the Remoting version of ClientSocketWrapper, and the Remoting version uses two CLOSING bytes. I accidentally included the the test for > 1 bytes. 2. The original closed connection checking mechanism, which is enabled by setting the parameter "socket.check_connection" to "true", sends a round trip byte, with value 1, from the client to the server and back. Now, Remoting uses 254 for ClientSocketWrapper.CLOSING, but, for some reason, I defined ClientSocketWrapper.CLOSING to be 1 in JBossMessaging. The 1 written by ServerSocketWrapper upon closing can be mistaken for the return of a 1 byte if the original connection checking mechanism is turned on, and a defunct connection can appear to be alive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1788) Document requirement that datasource be <local-tx-datasource>

by Justin Bertram (JIRA)

Document requirement that datasource be <local-tx-datasource> ------------------------------------------------------------- Key: JBMESSAGING-1788 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1788 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.6.GA, 1.4.0.SP3.CP09 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1 JBoss Messaging requires that its datasource be a <local-tx-datasource>. There is a wiki article [1] explaining why an <xa-datasource> is not required, but this should be in the official documentation. [1] http://community.jboss.org/wiki/JBMXADataSource -- 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

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6333) <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered

by Clebert Suconic (JIRA)

<database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered -------------------------------------------------------------------------------------- Key: JBAS-6333 URL: https://jira.jboss.org/jira/browse/JBAS-6333 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: JBossAS-5.0.1.CR1 -- 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

13 years, 10 months

5
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1812) Thread.sleep() is called with lock held in class ServerManagement

by Wendy Feng (JIRA)

Thread.sleep() is called with lock held in class ServerManagement ----------------------------------------------------------------- Key: JBMESSAGING-1812 URL: https://jira.jboss.org/browse/JBMESSAGING-1812 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 2.0.0.beta4 Reporter: Wendy Feng ServerManagement has unefficient code as follow: public static synchronized void kill(int i) throws Exception { ... try { while (true) { server.ping(); log.debug("server " + i + " still alive ..."); Thread.sleep(100); } } catch (Throwable e) { //Ok } Thread.sleep(300); log.info("server " + i + " killed and dead"); } } Since the kill() method has been synchronized, calling Thread.sleep() can not realease the resource to other waiting threads. It may cause poor performance or even deadlock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1811) Thread.sleep() is called with lock held in class NettyAcceptor

by Wendy Feng (JIRA)

Thread.sleep() is called with lock held in class NettyAcceptor -------------------------------------------------------------- Key: JBMESSAGING-1811 URL: https://jira.jboss.org/browse/JBMESSAGING-1811 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Affects Versions: 2.0.0.beta4 Reporter: Wendy Feng NettyAcceptor has unefficient code as follow: public synchronized void pause() { ... try { Thread.sleep(500); } catch (Exception e) { } ... } Since the pause() method has been synchronized, calling Thread.sleep() can not realease the resource to other waiting threads. It may cause poor performance or even deadlock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

← Newer
1
...
156
157
158
159
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2010