[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, 6 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, 6 months
[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree
by Andrew Lee Rubinger (JIRA)
Move JBossAS Maven Plugins into their own tree
----------------------------------------------
Key: JBASMP-12
URL: https://jira.jboss.org/jira/browse/JBASMP-12
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Currently under maven/plugins/jboss/trunk is:
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin
drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin
drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire
-rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml
Those prefixed with "maven-jboss-as" should be in their own tree
--
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, 6 months