March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1870) ClientSocketWrapper constructors have a redundant call to createStreams()

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1870?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1870: -------------------------------------- Fix Version/s: 1.4.8.SP11 (was: 1.4.8.SP10) > ClientSocketWrapper constructors have a redundant call to createStreams() > ------------------------------------------------------------------------- > > Key: JBMESSAGING-1870 > URL: https://issues.jboss.org/browse/JBMESSAGING-1870 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA > Reporter: Ron Sigal > Assignee: Yong Hao Gao > Priority: Minor > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP11 > > > org.jboss.jms.client.remoting.ClientSocketWrapper is derived from org.jboss.remoting.transport.socket.ClientSocketWrapper. The constructors of the former look like > public ClientSocketWrapper(Socket socket) throws IOException > { > super(socket); > createStreams(socket, null); > } > public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception > { > super(socket, metadata, timeout); > createStreams(socket, metadata); > } > and the constructors of the latter look like > public ClientSocketWrapper(Socket socket) throws IOException > { > super(socket); > createStreams(socket, null); > } > public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception > { > super(socket, timeout); > createStreams(socket, metadata); > } > The calls to createStreams() in the JBossMessaging versions of ClientSocketWrapper is redundant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1866) Adapt JBM tests to new failover model

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1866?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1866: -------------------------------------- Fix Version/s: 1.4.8.SP11 (was: 1.4.8.SP10) > Adapt JBM tests to new failover model > ------------------------------------- > > Key: JBMESSAGING-1866 > URL: https://issues.jboss.org/browse/JBMESSAGING-1866 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP11 > > > In jbm test suite some tests will fail if the 'keepOldFailoverModel' is set to false. This is because with new model, the failover for a dead node doesn't happen immediately. This affects all tests which expect a failover to happen after a certain timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1852) Make the connection failover retry paramters configurable

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1852?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1852: -------------------------------------- Fix Version/s: 1.4.8.SP11 (was: 1.4.8.SP10) > Make the connection failover retry paramters configurable > --------------------------------------------------------- > > Key: JBMESSAGING-1852 > URL: https://issues.jboss.org/browse/JBMESSAGING-1852 > Project: JBoss Messaging > Issue Type: Enhancement > Components: JMS Client Manager > Affects Versions: 1.4.0.SP3.CP11, 1.4.7.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP11 > > > Currently if a connection is broken and the client tries to fail over to a new connection, the retry times and intervals are hardcoded. (10 and 2sec resp.) > Make it configurable can suit some use cases where the server is shutdown and come back later. (with hardcoded retry, the failover may have given up before the server is back). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1923) Node cannot enter cluster during failover

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1923?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1923: -------------------------------------- Fix Version/s: 1.4.8.SP11 (was: 1.4.8.SP10) > Node cannot enter cluster during failover > ----------------------------------------- > > Key: JBMESSAGING-1923 > URL: https://issues.jboss.org/browse/JBMESSAGING-1923 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Clustering > Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP8 > Reporter: Terrence Cowhey > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP11 > > > The setup is a cluster of 4 nodes, arranged into 2 'sites': > Primary Site: site2blade1, site2blade2 > Secondary Site: site2blade3, site2blade4 > After restarting the nodes of the secondary site many times, one of them fails to come up, with a deployment failure in JMS - the PostOffice fails with an IllegalStateException. > The previous restarts were induced by either 'kill -KILL' on the app server, or a graceful shutdown. The final (failed) restart was on site2blade4, and was induced by a graceful shutdown of the app server. > The IllegalStateException is being thrown during a failover while a new node is starting to join the cluster. Waiting 60 seconds to start the node in question fixes the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1944) When a message is rejected by a full destination the session.close() method has a 10 seconds delay before returning.

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1944?page=com.atlassian.jira.... ] Yong Hao Gao closed JBMESSAGING-1944. ------------------------------------- > When a message is rejected by a full destination the session.close() method has a 10 seconds delay before returning. > -------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-1944 > URL: https://issues.jboss.org/browse/JBMESSAGING-1944 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Environment: JBoss EAP 5.x > Reporter: Tom Ross > Assignee: Tom Ross > Fix For: 1.4.8.SP10 > > > The session.close() method waits on the send() method to notify it that all message have been sent. This arrangement breaks when a none persistent message gets rejected by a full destination. In that case the close() method waits for 10 seconds before returning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3116) Update to HAL 2.2.0.Beta5

by Harald Pehl (JIRA)

Harald Pehl created WFLY-3116: --------------------------------- Summary: Update to HAL 2.2.0.Beta5 Key: WFLY-3116 URL: https://issues.jboss.org/browse/WFLY-3116 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 8.0.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum updated WFLY-3115: ------------------------------------ Description: When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. When defining JNDI-names (e.g. java:jboss/url/Configuration) instead of concrete URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 was: When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. When defining JNDI-names (e.g. java:app/url/Configuration) instead of convreate URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 > JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-3115 > URL: https://issues.jboss.org/browse/WFLY-3115 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. > When defining JNDI-names (e.g. java:jboss/url/Configuration) instead of concrete URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). > see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum updated WFLY-3115: ------------------------------------ Priority: Major (was: Critical) > JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-3115 > URL: https://issues.jboss.org/browse/WFLY-3115 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. > When defining JNDI-names (e.g. java:app/url/Configuration) instead of convreate URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). > see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum updated WFLY-3115: ------------------------------------ Summary: JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources (was: JNDI-Names should be supported in jboss-specific deployment descriptors for URL resurces) > JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-3115 > URL: https://issues.jboss.org/browse/WFLY-3115 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > Priority: Critical > > When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. > When defining JNDI-names (e.g. java:app/url/Configuration) instead of convreate URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). > see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resurces

by Thomas Kriechbaum (JIRA)

Thomas Kriechbaum created WFLY-3115: --------------------------------------- Summary: JNDI-Names should be supported in jboss-specific deployment descriptors for URL resurces Key: WFLY-3115 URL: https://issues.jboss.org/browse/WFLY-3115 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Final Reporter: Thomas Kriechbaum Priority: Critical When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. When defining JNDI-names (e.g. java:app/url/Configuration) instead of convreate URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014