Env: JBoss 3.2.1
is there a way within a MessageDrivenBean to detect whether
or not a JMS message has been previously released?
We are using ContainerAck in the MDB so in the case of a failure
the message is being resent from JMS. But within the MDB, we would
like to detect this condition and
I am curious as to what the future direction is with respect to
Jetty vs. Tomcat? Prior to 3.2.3, JBoss always release
2 separate binaries . It looks like now only Tomcat is
the bundled Servlet stack instead of Jetty.
Will TC be the defacto servlet for post 3.2.3 ?
Thanks
View the original p
Look inside the Wiki forum for the FAQ item. In there, it shows you how to setup a
singleton MDB by limiting the size of the pool to 1. You can apply the same principle
to do what you need.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828883#3828883
Re
looks like it's only in 3.2.2 . what would it take to back port to 3.2.1 ? Looks like
only the 2 files were changed
module: src/main/org/jboss/mq ; files: SpyMessage.java SpyQueueBrowser.java
comments:
Added the following vendor-specific JMS properties
public static final String PROPERTY_SCHE
Is this extension in JBoss 3.2.1 ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828472#3828472
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828472
---
This SF.N
sorry for the 3x post..
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828425#3828425
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828425
---
This SF.Net email
from the description of message-selector in the EJB spec, it looks like the JMS syntax
only allows for static value to be compared. I thought i'd ask to see if JBoss has
any extension to allow dynamic comparison ?
eg. during submission of a message to be consumed by MDB , i'd
set a long value
from the description of message-selector in the EJB spec, it looks like the JMS syntax
only allows for static value to be compared. I thought i'd ask to see if JBoss has
any extension to allow dynamic comparison ?
eg. during submission of a message to be consumed by MDB , i'd
set a long value
from the description of message-selector in the EJB spec, it looks like the JMS syntax
only allows for static value to be compared. I thought i'd ask to see if JBoss has
any extension to allow dynamic comparison ?
eg. during submission of a message to be consumed by MDB , i'd
set a long value
We have multiple JMS Queues where each queue is handled by a MessageDrivenBean.
Let say there are 2 queues: queue/HighPriority and queue/LowPriority.
Is there a way to specify the thread priority for
the 2 queues during deployment ? e.g. MDB that handles the queue/LowPriority is
assigned a lo
Env: JBoss 3.2.1
http://jboss.org/wiki/Wiki.jsp?page=ConfigureXXXForMessageDrivenBean
I'd like to limit the size of the pool for my MDB to 8 instances.
I followed instructions in the wiki page.
So my questions are:
1. Once deployed without any error, how do I verify via jmx-console that the
Just like genman has suggested, you can use the same datasource config file but
different table name withing the same Oracle SID or schema
eg.
JMS_MESSAGES, JMS_TRANSACTIONS vs.
NODEX_JMS_MESSAGES , NODEX_JMS_TRANSACTIONS
You can specify the table that JMS uses in jboss-mqservice.xml.
|
Why was Tomcat 4.1.x chosen instead?
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822815#3822815
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822815
---
OK never mind. Just read up on the UnifiedClassLoader3 & UnifiedLoaderRepository3
stuff and it looks like I need to enable HierarchyLoaderRepository3
adding the snippet below to METAINF/jboss-app.xml seems to solve the problem.
something.com:loader=EAR01.ear
View the origin
Env: Win2K , JBoss 3.2.1, JDK 1.4.2
I have 2 ears being deployed.
EAR01.ear
| + war01.war
| + sharedservlet.jar
|
|
| EAR02.ear
| + war02.war
| + sharedservlet.jar
1. Both ears contained the same servlet.class deployed under different URI.
2. There's a sharedservlet
15 matches
Mail list logo
