March 2011 - jboss-jira - Jboss List Archives

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

by Yong Hao Gao (JIRA)

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.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP12, 1.4.8.GA 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1833) Intermittent test failure -- MultipleFailoverTest.testAllKindsOfServerFailures()

by Yong Hao Gao (JIRA)

Intermittent test failure -- MultipleFailoverTest.testAllKindsOfServerFailures() -------------------------------------------------------------------------------- Key: JBMESSAGING-1833 URL: https://issues.jboss.org/browse/JBMESSAGING-1833 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP12, 1.4.8.GA I'm seeing failure in the test, the stack trace: 1) testAllKindsOfServerFailures(org.jboss.test.messaging.jms.clustering.MultipleFailoverTest)javax.jms.JMSException: Cannot find a cached connection factory delegate for node -1 at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:124) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java) at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:276) at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect40.invoke(ProducerAspect40.java) at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java) at org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:165) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:208) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:146) at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:137) at org.jboss.test.messaging.jms.clustering.MultipleFailoverTest.testAllKindsOfServerFailures(MultipleFailoverTest.java:174) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1843) Incorporate JBREM-1144

by Yong Hao Gao (JIRA)

Incorporate JBREM-1144 ---------------------- Key: JBMESSAGING-1843 URL: https://issues.jboss.org/browse/JBMESSAGING-1843 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Priority: Critical Fix For: 1.4.0.SP3.CP12, 1.4.8.GA -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1830) Random MultipleFailoverTest failures

by Yong Hao Gao (JIRA)

Random MultipleFailoverTest failures ------------------------------------ Key: JBMESSAGING-1830 URL: https://jira.jboss.org/browse/JBMESSAGING-1830 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP12, 1.4.8.GA The MultipleFailoverTest.testAllKindsOfServerFailures sometimes fails for reason not yet known. So far I have found that the some failoveMap updates didn't get received, so the client didn't failover to the right node. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1802) Persisting MapMessage with large String value is broken

by Justin Bertram (JIRA)

Persisting MapMessage with large String value is broken ------------------------------------------------------- Key: JBMESSAGING-1802 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1802 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP10 Reporter: Justin Bertram Assignee: Howard Gao Sending a javax.jms.MapMessage that has a String value >= 65536 characters fails. Here's the test-case to reproduce. I ran this against a fresh install of JBoss EAP 5: import java.util.Properties; import javax.jms.Connection; import javax.jms.ConnectionFactory; import javax.jms.DeliveryMode; import javax.jms.Destination; import javax.jms.MapMessage; import javax.jms.MessageProducer; import javax.jms.Session; import javax.naming.InitialContext; public class MessageSender { public static void main(String[] args) throws Exception { Properties props = new Properties(); props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); props.put("java.naming.provider.url", "127.0.0.1:1099"); props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); InitialContext initialcontext = new InitialContext(props); ConnectionFactory connectionFactory = (ConnectionFactory) initialcontext.lookup("ConnectionFactory"); Connection connection = connectionFactory.createConnection(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); Destination destination = (Destination) initialcontext.lookup("queue/DLQ"); MessageProducer producer = session.createProducer(destination); producer.setDeliveryMode(DeliveryMode.PERSISTENT); StringBuilder x = new StringBuilder(); for (int i = 0; i < Math.pow(2, 16) - 1; i++) { x.append("x"); } MapMessage message = session.createMapMessage(); message.setString("x", x.toString()); producer.send(message); System.out.println("Send succeeded!"); x.append("x"); // string is now 2^16 (65536) characters long message = session.createMapMessage(); message.setString("x", x.toString()); try { producer.send(message); } catch (Exception e) { System.out.println("Send failed!\n " + e.getCause().getMessage()); //e.printStackTrace(); } connection.close(); } } -- 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

11 years, 7 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWEB-193) SeLinux policy for JBoss Enterprise Web Server

by Sam Weaver (JIRA)

SeLinux policy for JBoss Enterprise Web Server ---------------------------------------------- Key: JBWEB-193 URL: https://issues.jboss.org/browse/JBWEB-193 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sam Weaver Assignee: Remy Maucherat Priority: Minor SeLinux causes JBoss EWS to stop working, or randomly fail to start. Therefore requesting an SeLinux policy for JBoss EWS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1820) Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation.

by Justin Bertram (JIRA)

Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation. -------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1820 URL: https://jira.jboss.org/browse/JBMESSAGING-1820 Project: JBoss Messaging Issue Type: Task Components: Configuration and Management, Documentation and Training Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 1.4.0.SP3.CP11, 1.4.8.GA This feature was removed in JBoss Messaging 1.4.0.CR2, but the documentation and configuration files were never updated. -- 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

11 years, 7 months

3
14
0 / 0

[JBoss JIRA] Created: (JBAS-8326) Invalid dependency in jboss-as-jmxpom

by Martin Höller (JIRA)

Invalid dependency in jboss-as-jmxpom ------------------------------------- Key: JBAS-8326 URL: https://jira.jboss.org/browse/JBAS-8326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-5.1.0.GA Environment: Maven 2.0.10, JBossAS 5.1.0.GA Reporter: Martin Höller Assignee: Dimitris Andreadis The maven module with groupId "org.jboss.jbossas" and artifactId "jboss-as-jmx" has a dependency to jboss-as-j2se. This might be ok. However, the dependency is declared twice, the second time with a type of "test-jar" but not with scope test. This prevents it from beeing used as a dependency in an EAR, as the maven-ear-plugin doesn't know (and shouldn't need to know) how to handle artifacts of type test-jar. It probably should't be packaged in an EAR anyway, but the dependency nevertheless seems wrong. -- 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

11 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8117) Rename folder prefix in distribution zip from jboss to jboss-as

by Dan Allen (JIRA)

Rename folder prefix in distribution zip from jboss to jboss-as --------------------------------------------------------------- Key: JBAS-8117 URL: https://jira.jboss.org/browse/JBAS-8117 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dan Allen Assignee: Paul Gier We complain that people still refer to AS as just JBoss but you gotta admit that we're not encouraging them not to considering that the AS download is just called jboss and expands just as jboss. The dist zipfile name (jboss-as-distribution-6.0.0.20100429-M3.zip) is consistent with the renaming. However, when you unzip it, the top-level directory (i.e. JBOSS_HOME) name is "jboss-6.0.0.20100429-M3". Can't we change this to "jboss-as-6.0.0.20100429-M3", or even better to "jboss-as-6.0.0.M3" (I don't think the date is necessary), for future releases? -- 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

11 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8070) The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME

by Paul Gier (JIRA)

The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME ----------------------------------------------------------------------------------------- Key: JBAS-8070 URL: https://jira.jboss.org/browse/JBAS-8070 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.M4 The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME -- 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

11 years, 7 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2011