If you deploy your MDB as a ha-singleton, wouldn't it fill up your requirements
?
1. Only one node consumes messages.
2. message sucker will migrate messages from other node to this one.
The only issue I see with this solution is ordering.
Messages sent to other nodes will be processed after th
IMHO, the Solaris behavior is the right one.
There are other differences wrt memory usage.
For instance on Solaris, if I understood correctly, you can run your jvm
without placing limits on memory, letting the jvm size itself according to the
load.
Sun tries probably to maintain some "advantag
Peter,
Actually, whether or not the jvm will return unused memory to the underlying OS
is jvm/platform dependent.
For instance, with the Sun jvm, on Windows, it never occurs while it is
supposed to happen on Solaris.
François
View the original post :
http://www.jboss.com/index.html?module=b
This is a known characteristic of the T1 processor. It is slow for single
threaded apps.
And the boot of JBoss is essentially single threaded. They are working on it.
If you want to boot your JBoss fast, you have to go for the fastest single
threaded processor, like Intel P4 Extreme or AMD 3G+
Oups, I forgot the code blocks :-(
|
|
|
|
| queue/TEST
|
|
| jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
|
| javax.jms.Queue
|
|
| baseQueueManagerName=MWTEST
| baseQueueName=TEST
|
|
With useJNDI=true and the following AdminObject defined, it works.
queue/TEST
jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
javax.jms.Queue
baseQueueManagerName=MWTEST
baseQueueName=TEST
Cheers,
View the original post :
