May 2008 - jboss-user - Jboss List Archives

[Messaging, JMS & JBossMQ] - Re: Huge queue

by adrian＠jboss.org

See message chunking on the persistence manager config View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151504#4151504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151504

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: JMS Durable subscriptions

by adrian＠jboss.org

Look at the SQL for how john/needle is created in the example config. And/or read the docs/wiki. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151503#4151503 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151503

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Send Mail in specified date.

by kukeltje

anonymous wrote : Or does somebody know a work around? A workaround for what? not using cvs-head? Sure...: - Grab the source for the 3.2.x release you are using and looking at the differences in timer related classes and patching those. - Wait for 3.2.3 - View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151502#4151502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151502

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: XA Recovery of messages sent to a Topic

by adrian＠jboss.org

"mmusgrov" wrote : | This is a problem for TM recovery since the XAResource a for temporary topic queue does not return XAResource.XA_RDONLY for the prepare phase. Thus when the TM calls recover on the resource no xids are returned and hence the transaction can never be recovered. | I don't understand this? If JBossMQ doesn't return the XID then the TM must assume it was committed. anonymous wrote : | Could anyone hazzard a guess as to how much effort would be involved in resolving this issue. It would however be a good optimization to return read only in this case. (Read Only i s an optimization which is why the behaviour you describe is not a bug). The PersistenceManager knows whether it wrote anything to the transaction log (database). i.e. it could do org.jboss.mq.pm.Tx.checkPersisted() but unfortunately the ServerIL has no way to return this information to the client. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151501#4151501 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151501

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: replace the Business Calendar at runtime

by kukeltje

no, not that I know of. You can of course patch jBPM since the source is open View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151500#4151500 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151500

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Out Of Memory problem

by kukeltje

look at the loads of testcases in the source how to use jBPM. jBPM itself never closes the context, nor should you do that in nodes. It should happen in the 'controlling' logic. That is something you provide or e.g. the command executor if you use async stuff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151499#4151499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151499

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Timer continuously expiring without repeater option set

by kukeltje

look at the async functionality long during 'actions' should not be done synchronous. It still could be a bug though that the timer repeats if the action is not finished within 'in time' even without a repeat. Still, you should use async actions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151496#4151496 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151496

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: MDBs stop listening

by adrian＠jboss.org

All I see is idle threads except for one SLSB thread waiting on an Oracle query. Check the server log for previous warnings. e.g. a network disconnect. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151495#4151495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151495

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: MDB login for topic subscriber

by maralcbr

hi Adrian, Thanks for your respose. Our problem is that we are running a cluster - this problem just happens with the second node of the cluster - the mdb/pool from the first loaded server connects fine, but the second loaded server gives that client id message. We could solve the issue with a hand from Brian Stanberry, giving a login/client id on the jboss command line. But although it fixes the problem, it seems a horrible solution. Analysing your answer, as the mdb is not a ha-singleton, it is loaded on both servers. Then, either if we put the pool size to one, we will have one connection on each server which will bring the same issue. I understood that if we remove the client-id it will work fine. The client-id configuration is not necessary? Thank in advance. Regards, Marcelo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151494#4151494 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151494

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: login/client id that is already connected/cluster config

by adrian＠jboss.org

A durable topic subscription and/or client id cannot be used by two clients at the same time. If you want to share the messages then use a queue. If you just want HA for the MDB that processes the topic subscription deploy your mdb in deploy-hasingleton so it only runs on one server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151493#4151493 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151493

18 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user May 2008