I am doing a smoke test. The queue is filled and the local node crashes. I
expect another node to process these messages. What happens, if the local node
is not recoverable (e.g. hardware defect)?
View the original post :
I read this document but it gives me no answer. The only section which
references MDB is the example section. But this does not explain how an
failover works with an MDB.
From reading this forum I learned that jboss messaging prefers the local node
as well.
Let me go back to my ealier
ataylor wrote : anonymous wrote : But this does not explain how an failover
works with an MDB
|
| MDB's are outside the scope of JBM. You can find more information from the
app server guys or the app server docs.
|
;-)
The app server 4.2.2 docs don't describe how jms works with new
timfox wrote : mbreuer wrote :
| | You are right, jbossas 4.2.2 comes with jbossmq, so it does not
reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to
the clustering section, it also adresses jbossmq.
| |
|
| JBoss 5 is still a beta.
|
| If you used
Hi Tim, I am still waiting for your response!
Are you just kidding? Or was it a serious question?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4162902#4162902
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4162902
After migration from JBossMQ to JBossMessaging i get an exception when starting
the 2nd cluster node.
2008-07-03 10:40:05,011 66685 ERROR [org.jboss.messaging.util.ExceptionUtil]
(main:) SessionEndpoint[12-n9fx37if-1-oy9w37if-9w9nuy-m3g4o4c5] cre
| ateConsumerDelegate
Solved! The problematic code was instantiated several times, so at least one
jms-session per request was created. Seems this blocks the queue for a while,
because the other (old) session processes the request and puts it back (no
consumer) after a specific period.
View the original post :
I tried it in the other way and moved the queue definitions from
deploy-hasingleton to deploy folder.
| server
| mbean code=org.jboss.jms.server.destination.QueueService
| name=jboss.messaging.destination:service=Queue,name=...
| xmbean-dd=xmdesc/Queue-xmbean.xml
|
While starting jboss 4.2.2.GA i get follwoing exception:
2008-07-02 12:50:50,676 30122 WARN [org.jboss.system.ServiceController]
(main:) Problem starting service jboss:service=invoker,type=po
| oledha
| java.lang.Exception: Port 4448 is already in use
| at
What about cluster-service.xml definitions? How should they be changed?
I am using a standard jboss all-configuration.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4162091#4162091
Reply to the post :
I tried it again and reinstalled jboss 4.2.2.GA with messaging. After that it
look a bit different. First of all, the consumers receive the messages. But
they don't receive immediatelly, they wait up to nearly timeout seconds.
Message msg = MessageConsumer.receive(6);
Sometimes the call
I am developing against several jboss servers, e.g. 4.0.3SP1 or 4.2.2.GA.
While using maven it's very tricky to handle the correct classpath. Is there a
way to say maven use all client jar's coming with server release x.y.z?
I searched repository.jboss.org for dependencies. It seems there's no
Any idea, why the receive fails?
How can i find out, what goes wrong? Are there special log entries?
The ObjectMessage is stored to an oracle database, but the header fields are of
type blob, so a can't take a look into.
View the original post :
I am evaluating JBoss 4.2.2 and JBoss Messaging 1.4.0SP3. When using
MessageConsumer with a messageSelector, the communication hangs.
The response ObjectMessage is build in the right way, msg.setJMSCorrelationID()
and msg.setJMSType() are set. The MessageProducer sends
the message, but the
Thanks for the hint!
Probably the client classpath (outside) jboss contains a wrong jar, i will
check it.
What about the behavior inside the container? JBossObjectMessage seems to be
the right one. After setting JMSCorrelationID the object contains (in debugger)
the header property. Any
The example runs without trouble.
I used the example for my eclipse testclient. As noted, my test-client used the
the wrong classpath, i will verify this. Primary goal to get jboss messaging
running inside the container.
The message driven beans work fine. Also my jms-client works in general.
16 matches
Mail list logo
