[JBoss-user] [Messaging, JMS JBossMQ] - big message not removed from the queue
We found a problem on JMS. I am not sure if it is my configuration problem. I
wrote a simple MDB. At client side, when I put a small size ObjectMessage into
the queue, MDB works fine. Only one MDB pickups and processes the message for
one time. However, when I put a big size ObjectMessage (~MB) into the queue and
MDB needs to process a little longer for a message, I found there are serveral
MDB which sequentially pick up the same message from the queue and process it.
I wonder if I should set something for message persistence to solve this
problem.
btw, jboss is running on a linux environment. I can see many same session pool
message for MeesageDriverBean. Does that multithread or multi-CPU cause the
problem? But I doubt because it is running fine for the small size message.
Thanks for your help in advance!
This is the my-jbossmq-destinations-service.xml in
jboss-4.0.2/server/default/deploy/jms directory
?xml version=1.0 encoding=UTF-8?
depends
optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager
--
MDB is very simple. ZippingMessage contains a list of filename need to be
zipped. When ZippingMessage is bigger, this MDB needs to process longer time on
zipping.
public void onMessage(Message arg0) {
// TODO Auto-generated method stub
try {
ObjectMessage om = (ObjectMessage) arg0;
ZippingMessage izm = (ZippingMessage) om.getObject();
// start zipping and wait it finished
ZipManager zipper = new ZipManager();
zipper.setName(izm.getZipFilename());
zipper.setFiles(izm.getItems());
zipper.start();
zipper.join();
} catch (Exception e) {
log.error(Unexpected exception: + e.getMessage());
}
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896162#3896162
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896162
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: big message not removed from the queue
jchen0516 wrote : We found a problem on JMS. I am not sure if it is my
configuration problem. I wrote a simple MDB. At client side, when I put a small
size ObjectMessage into the queue, MDB works fine. Only one MDB pickups and
processes the message for one time. However, when I put a big size
ObjectMessage (~MB) into the queue and MDB needs to process a little longer for
a message, I found there are serveral MDB which sequentially pick up the same
message from the queue and process it. I wonder if I should set something for
message persistence to solve this problem.
|
| btw, jboss is running on a linux environment. I can see many same session
pool message for MeesageDriverBean. Does that multithread or multi-CPU cause
the problem? But I doubt because it is running fine for the small size message.
|
| Thanks for your help in advance!
|
|
| This is the my-jbossmq-destinations-service.xml in
jboss-4.0.2/server/default/deploy/jms directory
|
|
|
| mbean code=org.jboss.mq.server.jmx.Queue
| name=jboss.mq.destination:service=Queue,name=myQueue
| depends
optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager
| /mbean
|
|
| --
| MDB is very simple. ZippingMessage contains a list of filename need to be
zipped. When ZippingMessage is bigger, this MDB needs to process longer time on
zipping.
|
| public void onMessage(Message arg0) {
|
| // TODO Auto-generated method stub
| try {
|
| ObjectMessage om = (ObjectMessage) arg0;
| ZippingMessage izm = (ZippingMessage) om.getObject();
|
| // start zipping and wait it finished
| ZipManager zipper = new ZipManager();
| zipper.setName(izm.getZipFilename());
| zipper.setFiles(izm.getItems());
| zipper.start();
| zipper.join();
|
| } catch (Exception e) {
| log.error(Unexpected exception: + e.getMessage());
| }
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3896164#3896164
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896164
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - more detail on problem on MDB processing big message in the
We found a problem on JMS. I am not sure if it is my configuration problem. I wrote a simple MDB. At client side, when I put a small size ObjectMessage into the queue, MDB works fine. Only one MDB pickups and processes the message for one time. The processing time is less than 1 minute. However, when I put a big size ObjectMessage (~MB) into the queue and MDB needs to process a little longer for a message (processing time is 4 minutes), I found there are serveral MDB which sequentially pick up the same message from the queue and process it. I wonder if I should set something for message persistence to solve this problem. Also, I check localDB.log, I saw it consistently write message to the queue by jboss (not client for sure) and delete message from the queue, like this: INSERT INTO JMS_MESSAGES VALUES(4,'QUEUE.myQueue',NULL,'A','aced0 ... COMMIT DELETE FROM JMS_MESSAGES WHERE MESSAGEID=4 AND DESTINATION='QUEUE.myQueue' INSERT INTO JMS_MESSAGES VALUES(4,'QUEUE.myQueue',NULL,'A','aced0 ... COMMIT DELETE FROM JMS_MESSAGES WHERE MESSAGEID=4 AND DESTINATION='QUEUE.myQueue' INSERT INTO JMS_MESSAGES VALUES(4,'QUEUE.myQueue',NULL,'A','aced0 ... COMMIT DELETE FROM JMS_MESSAGES WHERE MESSAGEID=4 AND DESTINATION='QUEUE.myQueue' However, I couldnot find DELETE FROM JMS_TRANSACTIONS ... When the message is small job, I can see DELETE FROM JMS_TRANSACTIONS... after DELETE FROM JMS_MESSAGES WHERE ... Any idea? If I use transacted queuesession, could that help? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3896177#3896177 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3896177 --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
