February 2012 - jboss-jira - Jboss List Archives

[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

13 years, 6 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

13 years, 6 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

13 years, 6 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

13 years, 6 months

4
17
0 / 0

[JBoss JIRA] (JBMESSAGING-1905) Proper handling the timeout issue in receive(timeout)

by Yong Hao Gao (Created) (JIRA)

Proper handling the timeout issue in receive(timeout) ----------------------------------------------------- Key: JBMESSAGING-1905 URL: https://issues.jboss.org/browse/JBMESSAGING-1905 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.SP3, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1880) JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer)

by Yong Hao Gao (JIRA)

JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer) --------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1880 URL: https://issues.jboss.org/browse/JBMESSAGING-1880 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 If a client consumer receives a message and exit without acknowledging it or close the connection/session/consumer object, the message will be cancelled at the server side. When the message is delivered, its JMSRedelivered flag should be true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
11
0 / 0

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

by Ron Sigal (JIRA)

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.8.GA, 1.4.0.SP3.CP12 Reporter: Ron Sigal Priority: Minor 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
12
0 / 0

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

by Yong Hao Gao (JIRA)

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

13 years, 6 months

2
11
0 / 0

[JBoss JIRA] Created: (AS7-1440) allow default persistence provider to be configured

by Scott Marlow (JIRA)

allow default persistence provider to be configured --------------------------------------------------- Key: AS7-1440 URL: https://issues.jboss.org/browse/AS7-1440 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Fix For: 7.1.0.Alpha1 Allow default persistence provider to be configured, so that a different provider could be used by default. This helps improve our JPA plugability (users preferred persistence provider can become the default). Without this feature, the user could instead make application changes to the persistence.xml to accomplish the same (not always possible if user cannot make app changes). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

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

13 years, 6 months

2
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 February 2012