Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am
22.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robb
lling user / application, this might lead to 'unexpected' delta values in case of concurrent multi users / application statistics queries.
Regards
Ulf Schroeter
"Scott M Stark" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
23.01.2004 19:02
Bitte antworte
I would recommend use of standard web-services instead of some non-standard c/c++-to-jms-hacks.
Regards
Ulf
Hi Dave,
good article ! But we should should look for a better place to store it ( e.g. JBoss homepage ) or even better include it into the offical documentation. You should ask Scott !
Regards
Ulf
I am sorry, but simple answer: no
Horia Muntean <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
01.10.2003 11:25
Bitte antworten an jboss-user
An: [EMAIL PROTECTED]
Kopie:
Thema: [JBoss-user] Maximum queue depth on JBoss
Hello,
For consistent updates of multiple resources we need XA transactions. Unfortunately some of our resources (e.g. MySQL DB or SAP R/3 JCA Connector, so it should be a quite common issue) only support local transactions ( meaning no 2-phase commit ).
Nevertheless consistent updates between multiple
For consistent updates of multiple resources we need XA transactions. Unfortunately some of our resources (e.g. MySQL DB or SAP R/3 JCA Connector, so it should be a quite common issue) only support local transactions ( meaning no 2-phase commit ).
Nevertheless consistent updates between multiple
ROM principals WHERE principal_id=?
SELECT role, 'Roles' FROM roles WHERE principal_id=? AND rolecontext='JMS-System'
Ulf Schroeter
IT Entwicklung - Design & Research
MobilCom Communikationstechnik GmbH
Hollerstr. 126
24782 Buedelsdorf
Te
Good work !
Regards
Ulf Schroeter
This can be caused by a simple timeout of your client connection request to the connection manager (e.g. due to high workload). The exception message is a little bit missleading and has been changed in 3.2.2x to "No manged connection available within configured timeout..". You can increase the tim
The JMS specification explicitly states that no assumptions about message delivery order should be made. You have to implement you own delivery order tracking logic ( normally based on tracking the ascending message ID and usage of some kind of message buffering in case of unordered message delive
>This could probably solve our problem.
>We could add the PROPERTY_SCHEDULED_DELIVERY within a second MDB on the
>server ;-)
>(not very good but it would be a starting-point ;-) )
Yes, this could work, but I still think, that using a stateless session bean that gets invoked by the scheduler is a
>How can I configure such a behaviour?
>Is there a right way to do this within JMS?
No, JMS specification does not include something like timed message processing. Therefore every solution to you problem is application server specificin a way.
You have two basisc alternatives for JBOSS:
1) use
You don't have to use a XA datasource for the jdbc2 persistence manager, local-tx-datasource is sufficient !
Regards
Ulf
"Marek Lange" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
04.06.2003 15:18
Bitte antworten an jboss-user
An: <[EMAIL PROTECTED]>
Maybe the message cache is still using a file persistence manager for temporary messages storage. Have a look into the your tmp directory. Is there something like a jbossmq subdirectory ? Check your deploy/jbossmq-service.xml and make sure that the message cache also uses the jdbc persistence mana
Very good, so please share your knowledge, because this is interesting for other people too :-)
"Roy Jones" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
28.03.2003 03:46
Bitte antworten an jboss-user
An: <[EMAIL PROTECTED]>
Kopie:
Them
I think that you also have to manually add the new queue/topic definition to jbossmq-destinations-service.xml because otherwise destinations created at runtime will not survive server restart.
Ulf Schroeter
MobilCom Communikationstechnik GmbH
You can use the jboss.mq.DestinationManger-MBean via jmx- console to create queues and topics at runtime. You also have to update the jbossmq-destinations-service.xml for persisting your configuration update, because queues and topics created at runtime will not be automatically stored in the conf
How is it possible to include major source upgrades ( some new classes, some modifcations of existing classes ) into the regular JBoss/JBossMQ source WITHOUTdeveloper CVS access ?
We have developped some missing - but for JBoss usage in a more complex JMS production environment vital - JBossMQ /
ionManager$XAConnectionEventListener.delist() on your previously ( inside tran.begin() ) enlisted resource.
Ulf Schroeter
"GROVE,MIKE (HP-FtCollins,ex1)" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]
10.01.2003 00:08
Bitte antworten an jboss-user
An: "'[
a complex topic/queue store and forward scenario with multiple durable subscribers and high message counts.
Regards,
Ulf Schroeter
28 matches
Mail list logo
