RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging It uses the MQSeries API to create the connection factory and queue objects, but those objects get registered in the JNDI namespace of JBoss itself. Basically, this is something very similar to the jbossmq-destinations.xml but for MQSeries (with the addition of the connection factory definitions). Thomas Cherel Development Manager Phone 508-366-3888 x3399 Cell 508-615-4535 [EMAIL PROTECTED] www.ascentialsoftware.com -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, August 29, 2003 10:04 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging :-) I thought it used the MQSeries API to construct the object referenes rather than JNDI? Regards, Adrian On Fri, 2003-08-29 at 14:29, [EMAIL PROTECTED] wrote: > I know this patch, I submitted it :-) > The patch contains much more details that what we discussed and can > probably be reused to figure out how to configure weblogic JMS in > JBoss (the initial email of this list). > > Thomas Cherel > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 29, 2003 7:49 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > On Fri, 2003-08-29 at 02:38, [EMAIL PROTECTED] > wrote: > > Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - > > also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended > > Transactional Clients - which requires CSD03) you have the support > fro > > XAConnectionFactory and through regular TCP/IP connection (in > previous > > version, you also had it, I think, but only through the "binding" > mode > > of MQ - shared memory - forcing you to have the queue manager on the > > same machine as JBoss and a whole lot of MQ dlls in the JBoss path). > > Somebody provided some mbeans to deploy MQSeries's queues and > connection factories into JBoss's jndi. > http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687 > > Regards, > Adrian > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
:-) I thought it used the MQSeries API to construct the object referenes rather than JNDI? Regards, Adrian On Fri, 2003-08-29 at 14:29, [EMAIL PROTECTED] wrote: > I know this patch, I submitted it :-) > The patch contains much more details that what we discussed and can > probably be reused to figure out how to configure weblogic JMS in > JBoss (the initial email of this list). > > Thomas Cherel > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Friday, August 29, 2003 7:49 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > On Fri, 2003-08-29 at 02:38, [EMAIL PROTECTED] > wrote: > > Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - > > also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended > > Transactional Clients - which requires CSD03) you have the support > fro > > XAConnectionFactory and through regular TCP/IP connection (in > previous > > version, you also had it, I think, but only through the "binding" > mode > > of MQ - shared memory - forcing you to have the queue manager on the > > same machine as JBoss and a whole lot of MQ dlls in the JBoss path). > > Somebody provided some mbeans to deploy MQSeries's queues and > connection factories into JBoss's jndi. > http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687 > > Regards, > Adrian > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging I know this patch, I submitted it :-) The patch contains much more details that what we discussed and can probably be reused to figure out how to configure weblogic JMS in JBoss (the initial email of this list). Thomas Cherel -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, August 29, 2003 7:49 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging On Fri, 2003-08-29 at 02:38, [EMAIL PROTECTED] wrote: > Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - > also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended > Transactional Clients - which requires CSD03) you have the support fro > XAConnectionFactory and through regular TCP/IP connection (in previous > version, you also had it, I think, but only through the "binding" mode > of MQ - shared memory - forcing you to have the queue manager on the > same machine as JBoss and a whole lot of MQ dlls in the JBoss path). Somebody provided some mbeans to deploy MQSeries's queues and connection factories into JBoss's jndi. http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687 Regards, Adrian --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Thanks for the details. Thomas Cherel -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED] Sent: Friday, August 29, 2003 7:53 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging On Fri, 2003-08-29 at 03:06, [EMAIL PROTECTED] wrote: > Quick question related to the remote invoker proxy binding. > Is it something new (this invoker proxy binding) in JBoss 3.2 to avoid > creating a complete different container-configuration? > > In JBoss 3.0.5, when bringing MQSeries as a JMS provider, I end up > creating a new container-configuration (I did not want to replace the > JBossMQ provider) to have MDB listening to MQSeries destinations (and > add something like "WSMQ Message Driven > Bean" in the jboss.xml of the MDB). > > Am I able, in JBoss 3.2, to just configure a new invoker proxy binding > instead? Meaning that the settings in the MDB > jboss.xml will overwrite the default invoker proxy of the Standard > Message Driven Bean? > Yes, that is the purpose of the invoker proxy bindings.It separates the container configuration from how you connect to the container. More generally they allow mutiple invokers for different protocols such as RMI and IIOP connection for the same EJB bound at different jndi names. Regards, Adrian > Thomas Cherel > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 7:26 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > This is sore point in the spec :-) > It leaves it for each JMS implementation to solve. It implements the > ConnectionConsumer and the Session. The message is passed under the > radar. In particular what happens when there is failure part way > through. > > This is a problem that JCA1.5's MessageEndpoint makes simple > to solve. The ConnectionConsumer is no longer used. > > Ignore DTM. The XAResource is instantiated inside JBoss > and enlisted in a JBoss Transaction. You don't need a DTM > to access a remote database. > > JBoss-3.2 config > 1) You need a remote provider (really an overly complicated way of > configuring jndi objects) > name="jboss.mq:service=RemoteJMSProviderLoader,name=JBossMQProvider"> > RemoteJMSProvider > jnp:/remote:1099 > > org.jboss.jms.jndi.JBossMQProvider > > name="QueueFactoryRef">java:/XAConnectionFactory > name="TopicFactoryRef">java:/XAConnectionFactory > > > 2) Then configure it on an invoker proxy binding: > > > remote-message-driven-bean > default > > org.jboss.ejb.plugins.jms.JMSContainerInvoker > > > RemoteJMSProvider > > StdJMSPool > 15 > 1 > >10 > > queue/DLQ > 10 > 0 > > > > > > 3) Use it on an mdb (jboss.xml) > > > test/mdb > > queue/testQueue > > > > remote-message-driven-bean > > > > > Regards, > Adrian > > On Thu, 2003-08-28 at 21:03, Barlow, Dustin wrote: > > In a previous discussion we had, you mentioned the following flow of > > JMS->CMT MDB > > > > > > The order of work is roughly: > > > > 1) receive() > > 2) getSession() and enlist in tx > > 3) getMDB() > > 4) onMessage() > > 5) releaseMDB() > > 6) commitSession() > > > > > > In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that > the JMS > > session would be aquired from Weblogic's JMS queue and since the > session > > would need to be enlisted in the TM of JBoss that it would require > DTM. But > > it seems from your reply that the session would not be a Weblogic > JMS > > session, but rather a local JBoss JMS session? Or am I mixing up > the JMS > > session with another type of JBoss session? > > > > Also, can you share your container setup for doing an MDB on JBoss > instance > > 1 binding to a queue on JBoss instance 2? I would be interested in > seeing > > how you set that up. > > > > Thanks for your time, > > Dustin > > > > > -Original Message- > > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, August 28, 2003 2:55 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
On Fri, 2003-08-29 at 03:06, [EMAIL PROTECTED] wrote: > Quick question related to the remote invoker proxy binding. > Is it something new (this invoker proxy binding) in JBoss 3.2 to avoid > creating a complete different container-configuration? > > In JBoss 3.0.5, when bringing MQSeries as a JMS provider, I end up > creating a new container-configuration (I did not want to replace the > JBossMQ provider) to have MDB listening to MQSeries destinations (and > add something like "WSMQ Message Driven > Bean" in the jboss.xml of the MDB). > > Am I able, in JBoss 3.2, to just configure a new invoker proxy binding > instead? Meaning that the settings in the MDB > jboss.xml will overwrite the default invoker proxy of the Standard > Message Driven Bean? > Yes, that is the purpose of the invoker proxy bindings.It separates the container configuration from how you connect to the container. More generally they allow mutiple invokers for different protocols such as RMI and IIOP connection for the same EJB bound at different jndi names. Regards, Adrian > Thomas Cherel > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 7:26 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > This is sore point in the spec :-) > It leaves it for each JMS implementation to solve. It implements the > ConnectionConsumer and the Session. The message is passed under the > radar. In particular what happens when there is failure part way > through. > > This is a problem that JCA1.5's MessageEndpoint makes simple > to solve. The ConnectionConsumer is no longer used. > > Ignore DTM. The XAResource is instantiated inside JBoss > and enlisted in a JBoss Transaction. You don't need a DTM > to access a remote database. > > JBoss-3.2 config > 1) You need a remote provider (really an overly complicated way of > configuring jndi objects) > name="jboss.mq:service=RemoteJMSProviderLoader,name=JBossMQProvider"> > RemoteJMSProvider > jnp:/remote:1099 > > org.jboss.jms.jndi.JBossMQProvider > > name="QueueFactoryRef">java:/XAConnectionFactory > name="TopicFactoryRef">java:/XAConnectionFactory > > > 2) Then configure it on an invoker proxy binding: > > > remote-message-driven-bean > default > > org.jboss.ejb.plugins.jms.JMSContainerInvoker > > > RemoteJMSProvider > > StdJMSPool > 15 > 1 > >10 > > queue/DLQ > 10 > 0 > > > > > > 3) Use it on an mdb (jboss.xml) > > > test/mdb > > queue/testQueue > > > > remote-message-driven-bean > > > > > Regards, > Adrian > > On Thu, 2003-08-28 at 21:03, Barlow, Dustin wrote: > > In a previous discussion we had, you mentioned the following flow of > > JMS->CMT MDB > > > > > > The order of work is roughly: > > > > 1) receive() > > 2) getSession() and enlist in tx > > 3) getMDB() > > 4) onMessage() > > 5) releaseMDB() > > 6) commitSession() > > > > > > In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that > the JMS > > session would be aquired from Weblogic's JMS queue and since the > session > > would need to be enlisted in the TM of JBoss that it would require > DTM. But > > it seems from your reply that the session would not be a Weblogic > JMS > > session, but rather a local JBoss JMS session? Or am I mixing up > the JMS > > session with another type of JBoss session? > > > > Also, can you share your container setup for doing an MDB on JBoss > instance > > 1 binding to a queue on JBoss instance 2? I would be interested in > seeing > > how you set that up. > > > > Thanks for your time, > > Dustin > > > > > -Original Message- > > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, August 28, 2003 2:55 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > > > > No, a distributed TM is only required when there are multiple > > > transaction managers. > > > > > > The JBossTM enlists the JMS's XASession/XA
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
On Fri, 2003-08-29 at 02:38, [EMAIL PROTECTED] wrote: > Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - > also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended > Transactional Clients - which requires CSD03) you have the support fro > XAConnectionFactory and through regular TCP/IP connection (in previous > version, you also had it, I think, but only through the "binding" mode > of MQ - shared memory - forcing you to have the queue manager on the > same machine as JBoss and a whole lot of MQ dlls in the JBoss path). Somebody provided some mbeans to deploy MQSeries's queues and connection factories into JBoss's jndi. http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687 Regards, Adrian --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging Quick question related to the remote invoker proxy binding. Is it something new (this invoker proxy binding) in JBoss 3.2 to avoid creating a complete different container-configuration? In JBoss 3.0.5, when bringing MQSeries as a JMS provider, I end up creating a new container-configuration (I did not want to replace the JBossMQ provider) to have MDB listening to MQSeries destinations (and add something like "WSMQ Message Driven Bean" in the jboss.xml of the MDB). Am I able, in JBoss 3.2, to just configure a new invoker proxy binding instead? Meaning that the settings in the MDB jboss.xml will overwrite the default invoker proxy of the Standard Message Driven Bean? Thomas Cherel -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 28, 2003 7:26 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging This is sore point in the spec :-) It leaves it for each JMS implementation to solve. It implements the ConnectionConsumer and the Session. The message is passed under the radar. In particular what happens when there is failure part way through. This is a problem that JCA1.5's MessageEndpoint makes simple to solve. The ConnectionConsumer is no longer used. Ignore DTM. The XAResource is instantiated inside JBoss and enlisted in a JBoss Transaction. You don't need a DTM to access a remote database. JBoss-3.2 config 1) You need a remote provider (really an overly complicated way of configuring jndi objects) name="jboss.mq:service=RemoteJMSProviderLoader,name=JBossMQProvider"> RemoteJMSProvider jnp:/remote:1099 org.jboss.jms.jndi.JBossMQProvider name="QueueFactoryRef">java:/XAConnectionFactory name="TopicFactoryRef">java:/XAConnectionFactory 2) Then configure it on an invoker proxy binding: remote-message-driven-bean default org.jboss.ejb.plugins.jms.JMSContainerInvoker RemoteJMSProvider StdJMSPool 15 1 10 queue/DLQ 10 0 3) Use it on an mdb (jboss.xml) test/mdb queue/testQueue remote-message-driven-bean Regards, Adrian On Thu, 2003-08-28 at 21:03, Barlow, Dustin wrote: > In a previous discussion we had, you mentioned the following flow of > JMS->CMT MDB > > > The order of work is roughly: > > 1) receive() > 2) getSession() and enlist in tx > 3) getMDB() > 4) onMessage() > 5) releaseMDB() > 6) commitSession() > > > In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that the JMS > session would be aquired from Weblogic's JMS queue and since the session > would need to be enlisted in the TM of JBoss that it would require DTM. But > it seems from your reply that the session would not be a Weblogic JMS > session, but rather a local JBoss JMS session? Or am I mixing up the JMS > session with another type of JBoss session? > > Also, can you share your container setup for doing an MDB on JBoss instance > 1 binding to a queue on JBoss instance 2? I would be interested in seeing > how you set that up. > > Thanks for your time, > Dustin > > > -Original Message- > > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, August 28, 2003 2:55 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > No, a distributed TM is only required when there are multiple > > transaction managers. > > > > The JBossTM enlists the JMS's XASession/XAResource. > > There is only one transaction manager. > > > > If the MDB did a remote ejb invocation then it would require a DTM. > > > > Of course you might want a logging TM for recovery. > > > > It should work with any JMS implementation. I've only tried it > > with JBoss<->JBoss. I've heard of people doing it with Arjuna > > and MQSeries. > > Sonic seem to want you replace JBoss's ServerSessionPoolFactory > > for reasons I don't understand. > > > > Regards, > > Adrian > > > > On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > > > In the 3.x series, how are CMTs handled if the JBoss MDB > > binds to a queue on > > > a Weblogic instance? Doesn't this require distributed TM > > which isn't > > > currently supported in 3.x? Would this even work between > > two JBoss 3.x &g
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended Transactional Clients - which requires CSD03) you have the support fro XAConnectionFactory and through regular TCP/IP connection (in previous version, you also had it, I think, but only through the "binding" mode of MQ - shared memory - forcing you to have the queue manager on the same machine as JBoss and a whole lot of MQ dlls in the JBoss path). I do not know if the issue I had was related to the deadlock you mention or not, but here is the answer I get through the JBoss mailing list (from [EMAIL PROTECTED]): Hi Thomas, I have done the Websphere MQ integration with jboss in the past and ran into the same issues. It's not you and it's not jboss. The JMS ASF spec is a little weak in describing who/how the inbound XA transaction gets started. The only way JBossMQ was able to implement the ASF spec was by starting the transaction without an associated XID. Once the message gets delivered to the container, JBossMQ allows the container to associate an XID with the session. The session then assigns the XID to the TX that delivered the message. JBossMQ had to kind of jump through hoops to get this to work. It would have been much easier to allow JBossMQ to assign an XID to the transaction to begin with. WebSphere MQ might be trying to do something like that. But since it's not in the JMS ASF spec, IBM would need to tell us what MQ is expecting (outside the spec) to get the asynch message delivery to work. Other ways to skin this cat: - Don't use the current MDB container invoker (which uses the ASF to do asynch message delivery). Write a new MDB container invoker that does synchronous Receiver.receive() calls to get messages. The problem with this approach is that you need to start a JTA TX before you do the receive() and our current TM will timeout the TXs that take too long. A solution my be to use receiveNoWait() instead. - Implement a MDB conatiner invoker using the new JCA TX inflow stuff. I have not had time to look into this yet or if MQ has a JCA resource adapter but this would be the best solution. Regards, Hiram Thomas Cherel Development Manager Phone 508-366-3888 x3399 Cell 508-615-4535 [EMAIL PROTECTED] www.ascentialsoftware.com -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 28, 2003 7:26 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging If was a frequently asked question in the forums for 3.0 that MQSeries didn't support an XAConnectionFactory. You had to fallback to acknowledgements with no XA false in the MDB config 3.2 detects whether a connectionfactory implements XAConnectionFactory Somebody else pointed out a bug in JBoss's ServerSessionPool that caused a deadlock in MQSeries. It wasn't a problem for jbossmq (is that what you are referring to?) Regards, Adrian On Thu, 2003-08-28 at 20:45, [EMAIL PROTECTED] wrote: > I managed to have MQSeries configured as a JMS provider in JBoss (and > then have JBoss MDB listening to MQ queues). But XA support did not > work (got an answer from on of the JBoss developer mentioning some > incompatibility between what MQSeries XA requires and what JBoss TM is > doing. Seems that JMS spec has some holes in this area). > > I also managed to have SonicMQ working, but I did not test yet the XA > capability. > In any cases, if you are able to add WebLogic as a JMS provider in > JBoss, you can basically do anything you want: > - JBoss MDB listening to WebLogic queue/topics > - Any JBoss component (MDB, EJB, Mbeans, ...) sending messages > to WebLogic queue/topics > - As long as you are within one JBoss server, and if WebLogic > JMS XA works with JBoss TM, then you can do XA (transaction integrity) > between all those pieces (weblogic queue/topics and other JBoss > queue/topics or XA database sources). > > Thomas Cherel > > > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 28, 2003 2:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > No, a distributed TM is only required when there are multiple > transaction managers. > > The JBossTM enlists the JMS's XASession/XAResource. > There is only one transaction manager. > > If the MDB did a remote ejb invocation then it would require a DTM. > > Of course you might want a logging TM for recovery. > > It should work with any JMS implementation. I've only tried it > with JBoss<->JBoss. I've heard of people doing it with Arjuna > and MQSeries. > Sonic seem to want you repla
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
This is sore point in the spec :-) It leaves it for each JMS implementation to solve. It implements the ConnectionConsumer and the Session. The message is passed under the radar. In particular what happens when there is failure part way through. This is a problem that JCA1.5's MessageEndpoint makes simple to solve. The ConnectionConsumer is no longer used. Ignore DTM. The XAResource is instantiated inside JBoss and enlisted in a JBoss Transaction. You don't need a DTM to access a remote database. JBoss-3.2 config 1) You need a remote provider (really an overly complicated way of configuring jndi objects) RemoteJMSProvider jnp:/remote:1099 org.jboss.jms.jndi.JBossMQProvider java:/XAConnectionFactory java:/XAConnectionFactory 2) Then configure it on an invoker proxy binding: remote-message-driven-bean default org.jboss.ejb.plugins.jms.JMSContainerInvoker RemoteJMSProvider StdJMSPool 15 1 10 queue/DLQ 10 0 3) Use it on an mdb (jboss.xml) test/mdb queue/testQueue remote-message-driven-bean Regards, Adrian On Thu, 2003-08-28 at 21:03, Barlow, Dustin wrote: > In a previous discussion we had, you mentioned the following flow of > JMS->CMT MDB > > > The order of work is roughly: > > 1) receive() > 2) getSession() and enlist in tx > 3) getMDB() > 4) onMessage() > 5) releaseMDB() > 6) commitSession() > > > In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that the JMS > session would be aquired from Weblogic's JMS queue and since the session > would need to be enlisted in the TM of JBoss that it would require DTM. But > it seems from your reply that the session would not be a Weblogic JMS > session, but rather a local JBoss JMS session? Or am I mixing up the JMS > session with another type of JBoss session? > > Also, can you share your container setup for doing an MDB on JBoss instance > 1 binding to a queue on JBoss instance 2? I would be interested in seeing > how you set that up. > > Thanks for your time, > Dustin > > > -Original Message- > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 28, 2003 2:55 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > No, a distributed TM is only required when there are multiple > > transaction managers. > > > > The JBossTM enlists the JMS's XASession/XAResource. > > There is only one transaction manager. > > > > If the MDB did a remote ejb invocation then it would require a DTM. > > > > Of course you might want a logging TM for recovery. > > > > It should work with any JMS implementation. I've only tried it > > with JBoss<->JBoss. I've heard of people doing it with Arjuna > > and MQSeries. > > Sonic seem to want you replace JBoss's ServerSessionPoolFactory > > for reasons I don't understand. > > > > Regards, > > Adrian > > > > On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > > > In the 3.x series, how are CMTs handled if the JBoss MDB > > binds to a queue on > > > a Weblogic instance? Doesn't this require distributed TM > > which isn't > > > currently supported in 3.x? Would this even work between > > two JBoss 3.x > > > instances? > > > > > > Dustin > > > > > > > -Original Message- > > > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > > > Sent: Thursday, August 28, 2003 1:24 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > > > > > > > There are two types of interoperability. > > > > > > > > JBoss MDB can use any messaging system (it doesn't care > > about jbossmq) > > > > > > > > Different JMS systems can transport each others messages > > > > (typically by wrapping them in their own native message) - > > > > this is obviously slower than a uniform environment. > > > > > > > > Regards, > > > > Adrian > > > > > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > > > Curley, John wrote: > > > > > > Hi, All: > > > >
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
If was a frequently asked question in the forums for 3.0 that MQSeries didn't support an XAConnectionFactory. You had to fallback to acknowledgements with no XA false in the MDB config 3.2 detects whether a connectionfactory implements XAConnectionFactory Somebody else pointed out a bug in JBoss's ServerSessionPool that caused a deadlock in MQSeries. It wasn't a problem for jbossmq (is that what you are referring to?) Regards, Adrian On Thu, 2003-08-28 at 20:45, [EMAIL PROTECTED] wrote: > I managed to have MQSeries configured as a JMS provider in JBoss (and > then have JBoss MDB listening to MQ queues). But XA support did not > work (got an answer from on of the JBoss developer mentioning some > incompatibility between what MQSeries XA requires and what JBoss TM is > doing. Seems that JMS spec has some holes in this area). > > I also managed to have SonicMQ working, but I did not test yet the XA > capability. > In any cases, if you are able to add WebLogic as a JMS provider in > JBoss, you can basically do anything you want: > - JBoss MDB listening to WebLogic queue/topics > - Any JBoss component (MDB, EJB, Mbeans, ...) sending messages > to WebLogic queue/topics > - As long as you are within one JBoss server, and if WebLogic > JMS XA works with JBoss TM, then you can do XA (transaction integrity) > between all those pieces (weblogic queue/topics and other JBoss > queue/topics or XA database sources). > > Thomas Cherel > > > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 2:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > No, a distributed TM is only required when there are multiple > transaction managers. > > The JBossTM enlists the JMS's XASession/XAResource. > There is only one transaction manager. > > If the MDB did a remote ejb invocation then it would require a DTM. > > Of course you might want a logging TM for recovery. > > It should work with any JMS implementation. I've only tried it > with JBoss<->JBoss. I've heard of people doing it with Arjuna > and MQSeries. > Sonic seem to want you replace JBoss's ServerSessionPoolFactory > for reasons I don't understand. > > Regards, > Adrian > > On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > > In the 3.x series, how are CMTs handled if the JBoss MDB binds to a > queue on > > a Weblogic instance? Doesn't this require distributed TM which > isn't > > currently supported in 3.x? Would this even work between two JBoss > 3.x > > instances? > > > > Dustin > > > > > -Original Message- > > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, August 28, 2003 1:24 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > > > > There are two types of interoperability. > > > > > > JBoss MDB can use any messaging system (it doesn't care about > jbossmq) > > > > > > Different JMS systems can transport each others messages > > > (typically by wrapping them in their own native message) - > > > this is obviously slower than a uniform environment. > > > > > > Regards, > > > Adrian > > > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > > Curley, John wrote: > > > > > Hi, All: > > > > > > > > > > Can anyone give me feedback on performing JMS messaging > to/from > > > > > JBoss/WebLogic environments? > > > > > > > > > > Should there be any issues with guaranteed messaging? > > > > > > > > > > In theory, there should be interoperability between the > > > two environments as > > > > > implied by the J2EE specification. > > > > > > > > Not really. The J2EE spec guarantees that applications will > > > be portable > > > > between environments, not that servers will be interoperable. > > > > > > > > Depending on exactly what you need to do, you can use the JBoss > JMS > > > > implementation from within weblogic, or the weblogic > > > implementation from > > > > within JBoss, by constructing your initial JNDI context > > > appropriately. > > > > > > > > hth, > > > > danch > > > > > > >
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging When configuring WebLogic as a JMS provider within JBoss, the MDB will get a WebLogic session. If this is an XA compliant session, then it can be enlisted in the JBoss TM (see JMS spec, where, on a XASession, you can say, getXAResource). The "tricky" part is: does WebLogic JMS interface supports the XA part of JMS and does it support it without having to use WebLogic TM or having it running within WebLogic. If it does, then it should work with the JBoss TM. On the JBoss instance 1 to JBoss instance 2, I never tried, but I suppose that you should be able to do that. It might come down to bringing the JNDI namespace of one JBoss into the other (or at least the connection factories and queues object registered in JNDI). I am not sure how you will do that, but I will be surprised if you cannot do it. Thomas Cherel Development Manager Phone 508-366-3888 x3399 Cell 508-615-4535 [EMAIL PROTECTED] www.ascentialsoftware.com -Original Message- From: Barlow, Dustin [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 28, 2003 4:04 PM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging In a previous discussion we had, you mentioned the following flow of JMS->CMT MDB The order of work is roughly: 1) receive() 2) getSession() and enlist in tx 3) getMDB() 4) onMessage() 5) releaseMDB() 6) commitSession() In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that the JMS session would be aquired from Weblogic's JMS queue and since the session would need to be enlisted in the TM of JBoss that it would require DTM. But it seems from your reply that the session would not be a Weblogic JMS session, but rather a local JBoss JMS session? Or am I mixing up the JMS session with another type of JBoss session? Also, can you share your container setup for doing an MDB on JBoss instance 1 binding to a queue on JBoss instance 2? I would be interested in seeing how you set that up. Thanks for your time, Dustin > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 28, 2003 2:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > > No, a distributed TM is only required when there are multiple > transaction managers. > > The JBossTM enlists the JMS's XASession/XAResource. > There is only one transaction manager. > > If the MDB did a remote ejb invocation then it would require a DTM. > > Of course you might want a logging TM for recovery. > > It should work with any JMS implementation. I've only tried it > with JBoss<->JBoss. I've heard of people doing it with Arjuna > and MQSeries. > Sonic seem to want you replace JBoss's ServerSessionPoolFactory > for reasons I don't understand. > > Regards, > Adrian > > On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > > In the 3.x series, how are CMTs handled if the JBoss MDB > binds to a queue on > > a Weblogic instance? Doesn't this require distributed TM > which isn't > > currently supported in 3.x? Would this even work between > two JBoss 3.x > > instances? > > > > Dustin > > > > > -Original Message- > > > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, August 28, 2003 1:24 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > > > > There are two types of interoperability. > > > > > > JBoss MDB can use any messaging system (it doesn't care > about jbossmq) > > > > > > Different JMS systems can transport each others messages > > > (typically by wrapping them in their own native message) - > > > this is obviously slower than a uniform environment. > > > > > > Regards, > > > Adrian > > > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > > Curley, John wrote: > > > > > Hi, All: > > > > > > > > > > Can anyone give me feedback on performing JMS > messaging to/from > > > > > JBoss/WebLogic environments? > > > > > > > > > > Should there be any issues with guaranteed messaging? > > > > > > > > > > In theory, there should be interoperability between the > > > two environments as > > > > > implied by the J2EE specification. > > > > > > > > Not really. The J2EE spec guarantees that applications will > > > be portable > > > > between
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
In a previous discussion we had, you mentioned the following flow of JMS->CMT MDB The order of work is roughly: 1) receive() 2) getSession() and enlist in tx 3) getMDB() 4) onMessage() 5) releaseMDB() 6) commitSession() In this case (Weblogic JMS -> JBoss CMT MDB), I was thinking that the JMS session would be aquired from Weblogic's JMS queue and since the session would need to be enlisted in the TM of JBoss that it would require DTM. But it seems from your reply that the session would not be a Weblogic JMS session, but rather a local JBoss JMS session? Or am I mixing up the JMS session with another type of JBoss session? Also, can you share your container setup for doing an MDB on JBoss instance 1 binding to a queue on JBoss instance 2? I would be interested in seeing how you set that up. Thanks for your time, Dustin > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 2:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging > > > No, a distributed TM is only required when there are multiple > transaction managers. > > The JBossTM enlists the JMS's XASession/XAResource. > There is only one transaction manager. > > If the MDB did a remote ejb invocation then it would require a DTM. > > Of course you might want a logging TM for recovery. > > It should work with any JMS implementation. I've only tried it > with JBoss<->JBoss. I've heard of people doing it with Arjuna > and MQSeries. > Sonic seem to want you replace JBoss's ServerSessionPoolFactory > for reasons I don't understand. > > Regards, > Adrian > > On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > > In the 3.x series, how are CMTs handled if the JBoss MDB > binds to a queue on > > a Weblogic instance? Doesn't this require distributed TM > which isn't > > currently supported in 3.x? Would this even work between > two JBoss 3.x > > instances? > > > > Dustin > > > > > -----Original Message----- > > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, August 28, 2003 1:24 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > > > > There are two types of interoperability. > > > > > > JBoss MDB can use any messaging system (it doesn't care > about jbossmq) > > > > > > Different JMS systems can transport each others messages > > > (typically by wrapping them in their own native message) - > > > this is obviously slower than a uniform environment. > > > > > > Regards, > > > Adrian > > > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > > Curley, John wrote: > > > > > Hi, All: > > > > > > > > > > Can anyone give me feedback on performing JMS > messaging to/from > > > > > JBoss/WebLogic environments? > > > > > > > > > > Should there be any issues with guaranteed messaging? > > > > > > > > > > In theory, there should be interoperability between the > > > two environments as > > > > > implied by the J2EE specification. > > > > > > > > Not really. The J2EE spec guarantees that applications will > > > be portable > > > > between environments, not that servers will be interoperable. > > > > > > > > Depending on exactly what you need to do, you can use > the JBoss JMS > > > > implementation from within weblogic, or the weblogic > > > implementation from > > > > within JBoss, by constructing your initial JNDI context > > > appropriately. > > > > > > > > hth, > > > > danch > > > > > > > > > > > > > > > > > > > > > > > > > > > > --- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > ___ > > > > JBoss-user mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > &
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging I managed to have MQSeries configured as a JMS provider in JBoss (and then have JBoss MDB listening to MQ queues). But XA support did not work (got an answer from on of the JBoss developer mentioning some incompatibility between what MQSeries XA requires and what JBoss TM is doing. Seems that JMS spec has some holes in this area). I also managed to have SonicMQ working, but I did not test yet the XA capability. In any cases, if you are able to add WebLogic as a JMS provider in JBoss, you can basically do anything you want: - JBoss MDB listening to WebLogic queue/topics - Any JBoss component (MDB, EJB, Mbeans, ...) sending messages to WebLogic queue/topics - As long as you are within one JBoss server, and if WebLogic JMS XA works with JBoss TM, then you can do XA (transaction integrity) between all those pieces (weblogic queue/topics and other JBoss queue/topics or XA database sources). Thomas Cherel -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 28, 2003 2:55 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging No, a distributed TM is only required when there are multiple transaction managers. The JBossTM enlists the JMS's XASession/XAResource. There is only one transaction manager. If the MDB did a remote ejb invocation then it would require a DTM. Of course you might want a logging TM for recovery. It should work with any JMS implementation. I've only tried it with JBoss<->JBoss. I've heard of people doing it with Arjuna and MQSeries. Sonic seem to want you replace JBoss's ServerSessionPoolFactory for reasons I don't understand. Regards, Adrian On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > In the 3.x series, how are CMTs handled if the JBoss MDB binds to a queue on > a Weblogic instance? Doesn't this require distributed TM which isn't > currently supported in 3.x? Would this even work between two JBoss 3.x > instances? > > Dustin > > > -Original Message- > > From: Adrian Brock [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, August 28, 2003 1:24 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > There are two types of interoperability. > > > > JBoss MDB can use any messaging system (it doesn't care about jbossmq) > > > > Different JMS systems can transport each others messages > > (typically by wrapping them in their own native message) - > > this is obviously slower than a uniform environment. > > > > Regards, > > Adrian > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > Curley, John wrote: > > > > Hi, All: > > > > > > > > Can anyone give me feedback on performing JMS messaging to/from > > > > JBoss/WebLogic environments? > > > > > > > > Should there be any issues with guaranteed messaging? > > > > > > > > In theory, there should be interoperability between the > > two environments as > > > > implied by the J2EE specification. > > > > > > Not really. The J2EE spec guarantees that applications will > > be portable > > > between environments, not that servers will be interoperable. > > > > > > Depending on exactly what you need to do, you can use the JBoss JMS > > > implementation from within weblogic, or the weblogic > > implementation from > > > within JBoss, by constructing your initial JNDI context > > appropriately. > > > > > > hth, > > > danch > > > > > > > > > > > > > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > ___ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
No, a distributed TM is only required when there are multiple transaction managers. The JBossTM enlists the JMS's XASession/XAResource. There is only one transaction manager. If the MDB did a remote ejb invocation then it would require a DTM. Of course you might want a logging TM for recovery. It should work with any JMS implementation. I've only tried it with JBoss<->JBoss. I've heard of people doing it with Arjuna and MQSeries. Sonic seem to want you replace JBoss's ServerSessionPoolFactory for reasons I don't understand. Regards, Adrian On Thu, 2003-08-28 at 18:58, Barlow, Dustin wrote: > In the 3.x series, how are CMTs handled if the JBoss MDB binds to a queue on > a Weblogic instance? Doesn't this require distributed TM which isn't > currently supported in 3.x? Would this even work between two JBoss 3.x > instances? > > Dustin > > > -Original Message- > > From: Adrian Brock [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 28, 2003 1:24 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > > > > There are two types of interoperability. > > > > JBoss MDB can use any messaging system (it doesn't care about jbossmq) > > > > Different JMS systems can transport each others messages > > (typically by wrapping them in their own native message) - > > this is obviously slower than a uniform environment. > > > > Regards, > > Adrian > > > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > > Curley, John wrote: > > > > Hi, All: > > > > > > > > Can anyone give me feedback on performing JMS messaging to/from > > > > JBoss/WebLogic environments? > > > > > > > > Should there be any issues with guaranteed messaging? > > > > > > > > In theory, there should be interoperability between the > > two environments as > > > > implied by the J2EE specification. > > > > > > Not really. The J2EE spec guarantees that applications will > > be portable > > > between environments, not that servers will be interoperable. > > > > > > Depending on exactly what you need to do, you can use the JBoss JMS > > > implementation from within weblogic, or the weblogic > > implementation from > > > within JBoss, by constructing your initial JNDI context > > appropriately. > > > > > > hth, > > > danch > > > > > > > > > > > > > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > ___ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS: JBoss to Weblogic messaging
In the 3.x series, how are CMTs handled if the JBoss MDB binds to a queue on a Weblogic instance? Doesn't this require distributed TM which isn't currently supported in 3.x? Would this even work between two JBoss 3.x instances? Dustin > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 1:24 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging > > > There are two types of interoperability. > > JBoss MDB can use any messaging system (it doesn't care about jbossmq) > > Different JMS systems can transport each others messages > (typically by wrapping them in their own native message) - > this is obviously slower than a uniform environment. > > Regards, > Adrian > > On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > > Curley, John wrote: > > > Hi, All: > > > > > > Can anyone give me feedback on performing JMS messaging to/from > > > JBoss/WebLogic environments? > > > > > > Should there be any issues with guaranteed messaging? > > > > > > In theory, there should be interoperability between the > two environments as > > > implied by the J2EE specification. > > > > Not really. The J2EE spec guarantees that applications will > be portable > > between environments, not that servers will be interoperable. > > > > Depending on exactly what you need to do, you can use the JBoss JMS > > implementation from within weblogic, or the weblogic > implementation from > > within JBoss, by constructing your initial JNDI context > appropriately. > > > > hth, > > danch > > > > > > > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS: JBoss to Weblogic messaging
There are two types of interoperability. JBoss MDB can use any messaging system (it doesn't care about jbossmq) Different JMS systems can transport each others messages (typically by wrapping them in their own native message) - this is obviously slower than a uniform environment. Regards, Adrian On Thu, 2003-08-28 at 17:26, Dan Christopherson wrote: > Curley, John wrote: > > Hi, All: > > > > Can anyone give me feedback on performing JMS messaging to/from > > JBoss/WebLogic environments? > > > > Should there be any issues with guaranteed messaging? > > > > In theory, there should be interoperability between the two environments as > > implied by the J2EE specification. > > Not really. The J2EE spec guarantees that applications will be portable > between environments, not that servers will be interoperable. > > Depending on exactly what you need to do, you can use the JBoss JMS > implementation from within weblogic, or the weblogic implementation from > within JBoss, by constructing your initial JNDI context appropriately. > > hth, > danch > > > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS: JBoss to Weblogic messaging
Curley, John wrote: Hi, All: Can anyone give me feedback on performing JMS messaging to/from JBoss/WebLogic environments? Should there be any issues with guaranteed messaging? In theory, there should be interoperability between the two environments as implied by the J2EE specification. Not really. The J2EE spec guarantees that applications will be portable between environments, not that servers will be interoperable. Depending on exactly what you need to do, you can use the JBoss JMS implementation from within weblogic, or the weblogic implementation from within JBoss, by constructing your initial JNDI context appropriately. hth, danch --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JMS: JBoss to Weblogic messaging
Hi, All: Can anyone give me feedback on performing JMS messaging to/from JBoss/WebLogic environments? Should there be any issues with guaranteed messaging? In theory, there should be interoperability between the two environments as implied by the J2EE specification. Has anyone put this scenario in to production? Thanks, John Curley -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 6:10 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] HELLO DUBAI hi there... thank you for writing to us..we will get back to you shortly... Thank you. --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
