| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
dant
Replies: 4
Views: 3496
|
 Forum: IBM MQ Java / JMS Posted: Sun May 15, 2005 12:37 pm Subject: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
Yeah, it was a jndi mapping problem. I thought so initially when I first posted, but I suppose I was just mixed up and tired when I was trying different orion-ejb-jar.xml configurations.
Maybe som ... |
| Topic: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
dant
Replies: 4
Views: 3496
|
Forum: IBM MQ Java / JMS Posted: Fri May 13, 2005 8:22 am Subject: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
Are you getting errors?
Well, not MQ errors specifically. We get a javax.naming.Exception when we try to lookup a queue named "prodS". This prodS queue definitely exists in the MQ JNDI context at ... |
| Topic: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
dant
Replies: 4
Views: 3496
|
Forum: IBM MQ Java / JMS Posted: Fri May 13, 2005 7:50 am Subject: EJB Descriptor -- make MQ my 3rd Party JMS Provider |
Hello all. This forum has helped me once before, and I'm hoping you EJB experts out there can help a newbie with EJBs.
I have deployed a MDB into the Oracle 10g App Server (orion). This MDB can ... |
| Topic: MQv5.3 on Solaris 9 -- conflicting documentation! |
dant
Replies: 5
Views: 3176
|
Forum: IBM MQ Installation/Configuration Support Posted: Tue Apr 26, 2005 9:32 am Subject: MQv5.3 on Solaris 9 -- conflicting documentation! |
The MQ documentation for Solaris MQ Server 5.3 implementation (we're using Solaris 9) conflicts in that it states the runmqlsr uses /etc/services AND that it no longer relies on inetd.conf:
In one ... |
| Topic: Trouble with Remote Queue Concept and JMS |
dant
Replies: 1
Views: 2287
|
Forum: IBM MQ Java / JMS Posted: Fri Apr 01, 2005 1:35 pm Subject: Trouble with Remote Queue Concept and JMS |
Hello all,
I am confused about the JMS abstraction of the MQ objects. From what I can tell, one creates one QCF (QueueConnectionFactory) for each QueueManager one has. Well, assuming this is true ... |
|
|
|
