Similar Issue
Using DAO in MDB processing[dao connection pool different than jms connection
pool]:
MDBs receive some messages initially and then stop receiving messages from JMS.
And after some time there is application deadlock when the MDB that are
processing message attempts to acquire DB
In order to help other people facing the same problem, we got it working by
ONLY swithching to Jboss Messaging (instead of JBOSS MQ).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022884#4022884
Reply to the post :
http://www.jboss.com/index.html?module=bb&
I have the same problem and I'm currenlty able to continue processing by only
stopping and restarting delivery of the queue.
That's not an acceptable solution for us though.
Is there an entry in JIRA for that? Or may be upgrading to a higher jboss
version or downgrading to former concurrent.jar
Yes, we use a cluster of 2 nodes. But I'am quite sure that the problem will
occur in a non clustered environment.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990016#3990016
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
Are you testing this in a Clustered Environment?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990011#3990011
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990011
___
jboss
I am quite sure the Corba-Services are thread safe. They are not the origin of
the Problem.
We made some tests with thousand of messages sent to the message queues from
multiple Clients in parallel. Most of the time all went fine. In let's say 1 of
20 bulk tests the failure situation occurs. Th
Have you tested the remote procedure call to the Corba service with multiple
threads?
i.e Simulataneous calls to the rpc Corba service ???
Our MDS all access the ftp service, and then our JMS Queue gets stuck.
But when we restart the ftp service , the messages get clear. We suspect it
could be d
The MDB takes the messages, parses them and calls a Corba-Services with message
data as argument. It is simliar as an remote procedure call of the
Corba-Service.
The messages transfered via JMS are of type javax.jms.MapMessage. We do not use
a ftp server.
There are 7 similar MDBs and 7 queue
Victoria for what perpose do you use JMS?
We use it to send emails. We are also accessing an FTP server.
What does your MDB do?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989673#3989673
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
The server.log looked fine. The last debug output from the relevant MDB was a
message of an succesfully processed message. There wasn't any indication that
anything went wrong.
Should I use special settings or log levels in order to get more information
about the status of the MDB?
View the or
Thanks for the reply.
JBoss runs in cluster mode as this issue exists in the production environment.
We often have noticed that the jms queue is increasing and gets stuck,
especially when there is a high load of traffic.
We use JMS to send emails to our customers. We use ftp server to store the
Did you check the logs to determine if the MDB was still active. In extreme
cases, like deadlock on database or huge load due to redelivery, it can freeze
and fallover..?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989631#3989631
Reply to the post :
http
We are facing the same problem.
If anyone has an idea about this, can you please suggest something?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989579#3989579
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989579
__
13 matches
Mail list logo
