So I am wondering what I should do with messages that end up in the DLQ.
They weren't processed for some reason, but what should I do next?
I would like to hear about what some people have done or common error recovery
strategies.
View the original post :
Using JBoss 4.3
messageProducer.setTimeToLive(6);
After sending the message and waiting 10 minutes I still see it in the queue.
Is this a bug?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268881#4268881
Reply to the post :
Is it possible to configure JBoss so that when a connection is dropped that it
will automatically reconnect to the remote server? Or do I have to write code
to do this?
The scenario is that I have a persistent connection/session from Server A to
Server B. Can I configure retries some place
I am using the JBoss Messaging that is bundled with the JBoss 4.3 release.
Version 1.4 according to the release notes.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268901#4268901
Reply to the post :
I am using JBoss Messaging 1.4.
That is a good point about it never actually being delivered to the consumer.
The reason for my concern is I am using a selector with my consumer, and I am
thinking that a buildup of abandoned messages would slow down the
selection/consumption of other messages.
Thanks that helped.
I found that I also had to edit the ejb3-inteceptors-apo.xml file. There was a
point cut that needed changing:
annotation expr=!class(@org.jboss.annotation.ejb.PoolClass)
| @org.jboss.annotation.ejb.PoolClass
(value=org.jboss.ejb3.StrictMaxPool.class,
I am using JBoss 4.3 and having problems controlling the pool settings.
How can I control the MDB pool size? Can I use the JMX console verify the
changes? Specifically the min and max instances in the pool?
I have tried using the pool annotation and changing setting in the
standardjboss.xml
I have this working with JBoss 5.x by including a queue-service.xml in the
META-INF of my EAR.
Does anyone know how to do this with JBoss 4.3? I have worked around it by
just defining the queues destinations-service.xml, but would rather have this
happen at deployment time.
View the
That worked. Thanks!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4245669#4245669
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4245669
___
jboss-user mailing list
Thanks for the tip. That seemed to fix it.
I added that line to the PostOffice and the JMSUserManager. I also had to
comment out a few things: ChannelFactoryName and GroupName
I'll let you guys know if there are and adverse effects.
| ?xml version=1.0 encoding=UTF-8?
|
| !--
|
I have taken the JBoss 5.0.0 GA distribution and everything is working nicely
when I use the default hsqldb-persistence-service.xml configuration
(hypersonic).
However, I wanted to see what performance gains I could get with the
null-persistence-service.xml (no persistence) and I can't get
I found the answer here:
http://www.jboss.org/jbossejb3/docs/reference/build/reference/en/html/session-bean-config.html#d0e26
Note that the annotation is @Pool not @PoolClass
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4207135#4207135
Reply to the post :
While trying to to set the pool size for an MDB I made the following
discoveries.
1. The annotation is not PoolClass it is just Pool
2. Setting it from the xml is very difficult. I did as the instructions stated
and I get the following stacktrace. Any ideas on how to get past this?
|
Where is the MDB pool size set? I want to understand how I can manage the
number of instances of my MDB.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4203077#4203077
Reply to the post :
14 matches
Mail list logo