By 'not deploy the MDBs' you mean ''Not processing pending messages in queues', right?
If so there is a flag you can set per MDB which specify whether the MDB is 'active' or
not (I think it's deliveryActive or something, check the jboss_3_2.dtd for more
details).
Regards,
Stephane
View the
Declare it twice with two different name and the same ejb-class, one on the first
destination and the other one on the other destination
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847856#3847856
Reply to the post :
http://www.jboss.or
Uh?
If you want only ONE receiver per message, use a queue.
The Singleton MDB is *NOT* the behavior you expect. Using this you limit the pooling
to only one instance per node.
Anyway, a message will always be received by all subscribers of a Topic, whatever the
pooling configuration.
Regards,
This is a log4j question and you have sample in the log4j.xml !!
|
|
|
|
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845126#3845126
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=
What DB are you using, which JBoss version?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844602#3844602
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844602
-
Adrian posted a solution in the FAQ.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844597#3844597
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844597
Do you need to send those 10.000 messages in the same transaction? Otherwise, you can
use java:/JmsXA and create a connection for each message. Won"t be a problem since
it's a pooled behind the scenes.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
Jboss creates a temporary destination only if the queue does not exist at the time the
MDB is deployed. Are you sure queue/test is created first? In which file are you
declaring it?
Also, you can add a depends tag in your jboss.xml to depend on the Queue's MBean.
Regards,
Stephane
View the or
"lokman" wrote : The whole point in the MDB idea is that you have a pool of consumers
on the queue. Using less threads means less consumers and should mean worse
performance, not better performance.
|
Provided that your consumers will not run into some concurrency issues (while
processing me
As from 3.2.4, it's using a database to persist subscription instead of the
jbossmq-state.xml file.
Check deploy/jms/ for the class name to use (hsql-jbossmq-state.xml I think).
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842557#3842557
Ah ok, I didn't knew.
Thanks,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842542#3842542
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842542
---
This
Your tests seems interesting. I just have one question: if you use non persistent
messages, why are you considering databases?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842537#3842537
Reply to the post :
http://www.jboss.org/index
FAQ
http://www.jboss.org/wiki/Wiki.jsp?page=IsThereAStandaloneDistributionOfJBossMQ
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842535#3842535
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842535
-
I updated Wiki examples with latest changes in 3.2.4
http://www.jboss.org/wiki/Wiki.jsp?page=JmsReceiverBean
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842512#3842512
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
OK. Now, let's say I want to receive X messages in a transactional context, I have a
session bean for that (see JmsReceiver on the Wiki).
Should I stop the connection at the end as well?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38422
If I am not wrong, we have to call connection.start() as from 3.2.4 using java:/JmsXA
to receive a message
Am I correct?
Regards,
Stephane
PS : since we move from 3.2.3 to 3.2.4 we do not receive any message using java:/JmsXA.
View the original post :
http://www.jboss.org/index.html?module=
Well I might misunderstand your question, true, but back to your first post:
QueueConnectionFactory qf = (QueueConnectionFactory) ctx.lookup("java:/JmsXA");
qf.createQueueConnection();
will work in your Mbean. Then you can do whatever you want with the connection
(returns it to the caller for
Also, the Wiki contains code that shows how to use java:/JmsXA with XDoclet in a
Session Bean.
http://www.jboss.org/wiki/Wiki.jsp?page=JmsSenderBean
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841664#3841664
Reply to the post :
http://www.jboss.org/index
(4) read Adrian's post one more time. The name is java:/JmsXA not java:/Jms ...
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841663#3841663
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841663
-
Show the code that sends the message to QueueA in your session bean.
It should NOT use JMS transacted session (i.e. pass true when you create your JMS
session). If your Session Bean is enlisted to a JTA transaction, sending of the JMS
message will also be enlisted automatically.
Regards,
Steph
Read the FAQ, Adrian added an entry on that subject.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841662#3841662
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841662
If you want to get rid of the bug in concurrent.jar, just copy the concurrent.jar of
the JBoss 3.2.4 distribution in your 3.2.3 local copy.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840781#3840781
Reply to the post :
http://www.jboss
Hello,
Since we moved to JBoss 3.2.4, we start having trouble with JBossMQ. We are using
JDBC2 persistence manager and mysql 4.0.18
We are using the standard mysql-jdbc2-service.xml provided with the JBoss release
| 11:25:08,632 WARN [jboss.tm.TransactionImpl] XAException:
tx=TransactionIm
It's in jms-ds.xml. If you check release 3.2.4 they made it explicit. Check CVS on
branch 3_2 and you'll have a sample.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839642#3839642
Reply to the post :
http://www.jboss.org/index.html?modu
If you're running your sample code inside JBoss you only need to create a default
InitialContext object.
| Context context = new InitialContext();
|
If you're running for a separate process, you need to set the property that are inside
$JBOSS_HOME/server/default/conf/jndi.properties and
Do you need custom security config? If no declare your queue as
|
| jboss.mq:service=DestinationManager
|
|
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839319#3839319
Reply to the post :
http://www.jboss.org/index.h
Yup, JMX.
Each MDB is exposed as an MBean and have a startDelivery() and stopDelivery() method.
I will add a sample code later on Wiki.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839318#3839318
Reply to the post :
http://www.jboss.or
Have you tried to put in the server's lib directory?
$JBOSS_HOME/server/default/lib if you're using the default server.
You can also declare your lib with a java module inside application.xml
jaxen-full.jar
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module
Ok, checked a little bit further I forgot to define the security conf of my topic.
Problem solved.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838347#3838347
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode
I have 3 durable subscription if I check the JMX object for my topic
opic,kserver/EventTopic,b2bOutboundPK.b2bOutboundPKDurableSubscriber,true,0,0,76,76,-
Topic,kserver/EventTopic,b2bOutboundParcelHistory.b2bOutboundParcelHistoryDurableSubscriber,true,0,0,125,125,-
Topic,kserver/EventTopic,b2bOutb
Hello,
I read the mini tutorial on the forum
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=45285
But it does not work. I have 3 MDBs with a durable subscription on a Topic. Example
for one of them
My ejb-jar:
Blah
ejb/kserver/ParcelHistoryExportMDB
Hey, thanks a lot. Why not posting this to the WiKi?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838290#3838290
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838290
HSQL is more a 'demo' database. I won't suggest you to use it with that amount of
users.
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836802#3836802
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3
Apparently this thread was lost so I repost it.
We are using JBoss 3.2.3, Postgresql as JDBC2PM.
We have some processors (MDB) that read messages from queues and do some action. If it
fails, the message is sent to an error queue with extra info in the aim we can
'repost' the mesage after a whil
We are using JBoss 3.2.3, Postgresql as JDBC2PM.
We have some processors (MDB) that read messages from queues and do some action. If it
fails, the message is sent to an error queue with extra info in the aim we can
'repost' the mesage after a while (if the error is thrown because of missing info
Why not searching the origin of the deadlock in a first place?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835673#3835673
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835673
Ooops actually you're using the DM as well
/me is stupid
My code does the same internally from a session bean. I will post it on the wiki asap.
Regards,
StÃphane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831694#3831694
Reply to the post :
http://www.
I have also a piece of code that does that using the destination manager. You can post
your sample on the JBossMQ Wiki.
http://jboss.org/wiki/Wiki.jsp?page=JBossMQ
Regards,
StÃphane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831693#3831693
Reply to the
Hey,
No need to create multiple threads for the same question:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48692
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831408#3831408
Reply to the post :
http://www.jboss.org/index.h
Have a look to
http://www.jboss.org/developers/guides/quickstart
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831403#3831403
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831403
---
40 matches
Mail list logo