[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, 8 months
[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, 8 months
[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, 8 months
[JBoss JIRA] Created: (JBBUILD-607) AS testsuite test targets don't work on windows
by Alexey Loubyansky (JIRA)
AS testsuite test targets don't work on windows
-----------------------------------------------
Key: JBBUILD-607
URL: https://jira.jboss.org/jira/browse/JBBUILD-607
Project: JBoss Build System
Issue Type: Bug
Components: Targets and Tasks
Reporter: Alexey Loubyansky
Since we've switched to maven repository classpath for testsuite classpath, the classpath got too long to work on windows.
So, it either has to be shorter or a manifest-only jar can be created that would reference all the jars and dirs.
The problem with the manifest-only jar is that there must be relative path from the jar location to all the other jars and dirs that need to be included in the classpath. Taking into account that the relative path might not exist (e.g. the AS checkout and maven local repo can be on different drives) the jar might not work.
(Although, right now on my windows machine fixed it with generating the manifest-only jar.)
--
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, 8 months