Hi
I need to create/destroy topics/queues on the fly in JVM. Is there a way I can
access the admin interface (as Java interfaces/classes) where I can do these
operations.
Thanks
Raghu
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3956541#3956541
Reply to
There is one connection, one topic and one session shared by three threads.
Session is created with AUTO_ACKNOWLEDE flag. And there are no queues.
The threads -
1. Sender thread has a producer on the topic.
2. Relayer thread has a producer and a consumer on the topic.
3. Receiver thread has a
Thanks for pointing out the tunables.
Does it mean that if I have messages of fixed size 'm', I should provision for
at least (FullSize+downCacheSize+pageSize)*m amount of memory in the JVM to
prevent any OutOfMemory exceptions?
Also, even after (FullSize+downCacheSize) number of outstanding
Sorry for posting this late.
Upgrading to CR2 of jboss-messaging solved the hang problem. I am posting the
working code anyway.
And these variables need to be set in build.properties.
jms.test.java.naming.provider.url = jnp://server name:1099
jms.test.java.naming.factory.initial =
Hi
I am using a JMS topic for communication between a producer and a consumer. The
producer generates large quantities of data (many large streaming messages).
I would expect that in case the consumer is slow, JBOSS would throttle the
producer. But I am noticing that the the producer keeps
Here is the code. Four lines are commented out to disable the relay operation
in the MyRelayerWithNewSession class. You could enable the relay operation by
removing the comments and see the difference in the behaviour.
Thanks
Raghu
| import javax.jms.*;
|
The messaging server and the client (with its three threads) are running on two
different machines. I am passing these two parameters through the
'build.properties' file on the client side.
==
jms.test.java.naming.provider.url = jnp://bhatp-desktop:1099
jms.test.java.naming.factory.initial =
Hi
I am using jboss-4.0.4.GA with jboss-messaging-1.0.0.GA on linux/x86 platform
and using JMS API. Java is Standard Edition (build 1.5.0_04-b05). The setup is
run with default configuration (no changes made). The JBoss messaging server
runs on a different machine from the test machine.
I am
