April 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken

by timfox

I don't remember having that conversation. A large message implementation which allows user to run out of memory is useless. What's the use case for this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223493#4223493 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223493

17 years

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: BUILD FAILED: set jboss.server to the name of the JBoss

by ben.cotton＠rutgers.edu

Still having the exact same problem after full JBossAS 5.0.1.CR build from scratch: 1. pulled down the AS 5 source from https://svn.jboss.org/repos/jbossas/branches/Branch_5_x/ 2. cd build/ dir 3. ant clean all install #BUILD 100% SUCCESSFUL 4. export JBOSS_HOME=/cygdrive/c/Users/buddy/workspace/JBoss-AS-5.x/build/output/jboss-5.1.0.CR1/ 5. cd /cygdrive/c/Users/buddy/workspace/JBOSS_4_6_0_CR1 6. ant jbossjta anonymous wrote : | [java] BUILD FAILED | [java] c:\Users\buddy\workspace\JBOSS_4_6_0_CR1\build.xml:145: The following error occurred while executing this line: | [java] c:\Users\buddy\workspace\JBOSS_4_6_0_CR1\atsintegration\build.xml:74: The JBoss server 'all' does not appear to exist in the installation directory. Please set jboss.server to the name of the JBoss server instance. | [java] | [java] Total time: 3 minutes 29 seconds | | BUILD FAILED | | Thanks, Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223490#4223490 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223490

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken

by clebert.suconic＠jboss.com

I was able to send and receive 500 * 1024 * 1024 bytes, if removing one reference of the memory (that would use 500M of memory): Index: src/org/jboss/jms/example/LargeMessageExample.java | =================================================================== | --- src/org/jboss/jms/example/LargeMessageExample.java (revision 6312) | +++ src/org/jboss/jms/example/LargeMessageExample.java (working copy) | @@ -68,10 +68,12 @@ | | //Step 7. Create a BytesMessage with 1MB arbitrary bytes | BytesMessage message = session.createBytesMessage(); | - message.writeBytes(new byte[1024 * 1024]); | + message.writeBytes(new byte[500 * 1024 * 1024]); | | //Step 8. Send the Message | producer.send(message); | + | + message = null; | | System.out.println("Large Message sent"); | | @@ -84,7 +86,7 @@ | connection.start(); | | //Step 11. Receive the message | - BytesMessage messageReceived = (BytesMessage) messageConsumer.receive(5000); | + BytesMessage messageReceived = (BytesMessage) messageConsumer.receive(120000); | | System.out.println("Received message: " + messageReceived.getBodyLength() + " bytes"); | And by adding more memory on the VM: Index: jms/common/build.xml | =================================================================== | --- jms/common/build.xml (revision 6312) | +++ jms/common/build.xml (working copy) | @@ -104,7 +104,8 @@ | <target name="runExample" depends="compile"> | <java classname="${example.classname}" fork="true" resultproperty="example-result"> | <jvmarg value="-XX:+UseParallelGC"/> | - <jvmarg value="-Xms512M"/> | + <jvmarg value="-verbose:gc"/> | + <jvmarg value="-Xms1024M"/> | <jvmarg value="-Xmx2048M"/> | <jvmarg value="-XX:+AggressiveOpts"/> | <jvmarg value="-XX:+UseFastAccessorMethods"/> | I rememver having a conversation with you about supporting ClientFiles through JMS, and I remember we deciding on support that thorugh the core-api. If we do want to expose it thorugh JMS, we would need some special methods to specify the Client directory.. and how to add a fileHandle to a message. (Or maybe having StreamMessage storing the data on a temporary file). I will do a little more extensive testing on monday to make sure nothing is broken. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223488#4223488 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223488

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken

by clebert.suconic＠jboss.com

There will be another client example doing large messages, using ClientFiles. And I will also make sure there is nothing broken. if there is.. it will be an easy fix. I will do this first thing on monday. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223486#4223486 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223486

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken

by clebert.suconic＠jboss.com

In the client Tim. FileMessage on the client is only available through core. (At least ATM) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223483#4223483 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223483

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken (Repost)

by timfox

Why should it be running out of memory? The whole point of large messages is the user should be able to send virtually unlimited size messages without worrying about running out of memory. If it doesn't work then it's broken. The only limit to message size should be disk space on server and client. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223458#4223458 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223458

17 years

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: BUILD FAILED: set jboss.server to the name of the JBoss

by ben.cotton＠rutgers.edu

Exact same error, exact same spot with export JBOSS_HOME=/cygdrive/c/Users/buddy//jboss-5.1.0.Beta1/ Will now try a full AS 5 build from source, followed by another re-try of ant jbossjta Thanks for your support, Jonathan ... if the full AS 5 build approach fails, maybe I should try a switch to a Linux (redHat .iso download available anywhere?) build environ rather than you re-producing this with Cygwin. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223482#4223482 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223482

17 years

1
0
0 / 0

[Design the new POJO MicroContainer] - CL's GlobalCapabilities have a bug

by alesj

Kabir's GlobalCapabilities cause a NPE in current Deployers trunk. A bit of background on how this NPE was exposed. :-) I've released temp 2.2.0 Milestone1 releases of MC sub-projects: * VFS * Kernel * CL This is off the trunk, since currently most of the branches look exactly the same as trunk, hence I don't expect any big diff when I do proper 2.0.x releases. This is just to get Alexey and Remy to move fwd with their work on XB and Metadata. I've also committed Deployers with all the updates, although the current build fails, hence exposing the bug. | 516 ERROR [MockClassLoaderDescribeDeployer] Error during undeploy: A | java.lang.NullPointerException | at org.jboss.classloading.spi.dependency.Module.getCapabilities(Module.java:661) | at org.jboss.classloading.spi.dependency.Module.determinePackageNames(Module.java:716) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.unjoin(ClassLoadingSpace.java:283) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.split(ClassLoadingSpace.java:190) | at org.jboss.classloading.spi.dependency.Domain.removeModule(Domain.java:186) | at org.jboss.classloading.spi.dependency.Module.release(Module.java:922) | at org.jboss.deployers.plugins.classloading.AbstractDeploymentClassLoaderPolicyModule.release(AbstractDeploymentClassLoaderPolicyModule.java:147) | at org.jboss.classloading.spi.dependency.ClassLoading.removeModule(ClassLoading.java:126) | at org.jboss.deployers.plugins.classloading.AbstractClassLoaderDescribeDeployer.undeploy(AbstractClassLoaderDescribeDeployer.java:120) | at org.jboss.deployers.plugins.classloading.AbstractClassLoaderDescribeDeployer.undeploy(AbstractClassLoaderDescribeDeployer.java:39) | at org.jboss.deployers.spi.deployer.helpers.AbstractOptionalRealDeployer.internalUndeploy(AbstractOptionalRealDeployer.java:91) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.undeploy(AbstractRealDeployer.java:112) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:196) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doUndeploy(DeployersImpl.java:1469) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1376) | at org.jboss.deployers.plugins.deployers.DeployersImpl.uninstall(DeployersImpl.java:1331) | at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354) | at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1664) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1275) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:827) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:694) | at org.jboss.deployers.plugins.main.MainDeployerImpl.undeploy(MainDeployerImpl.java:601) | at org.jboss.test.deployers.AbstractDeployerTest.assertUndeploy(AbstractDeployerTest.java:207) | at org.jboss.test.deployers.classloading.test.MockClassLoaderDependenciesUnitTestCase.testSimpleClassLoader(MockClassLoaderDependenciesUnitTestCase.java:67) | Once this is fixed I'll do a new CL release + Deployers 2.2.0.M1. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223480#4223480 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223480

17 years

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: BUILD FAILED: set jboss.server to the name of the JBoss

by jhalliday

I would not expect it to build against 4.2.2 at all, the AS internals have changed substantially. As for 5.0.0.GA, it may predate some shuffling around of AS libraries which will confuse the build script, or it may (less likely) be a problem with cygwin paths not being handled properly. Try AS 5.1.0.Beta1 or build the AS source from branch 5.x maybe? Failing that I'll have to install cygwin into a windows vm and try to recreate the issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223479#4223479 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223479

17 years

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: BUILD FAILED: set jboss.server to the name of the JBoss

by ben.cotton＠rutgers.edu

I have two installations of JBossAS ... Whether I build with export JBOSS_HOME=/cygdrive/c/Users/buddy//jboss-5.0.0.GA/ or build with export JBOSS_HOME=/cygdrive/c/Users/buddy//jboss-4.2.2.GA/ executing ant jbossjta from ../workspace/JBOSS_4_6_0_CR1/ results in the exact same "Please set jboss.server to the name of the JBoss server instance." error message. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223477#4223477 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223477

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009