MQSERIES

How do you write a client on the server side itself ?? Is the Bindings Mode the only way to do this??
If yes, then what is MQJBND02 not found error.
Any urls having some info on the same???
Any help will be appreciated.
Thanx in advance
Vikas

Hello Vikas,
This means he can not find the mq library.
On windows this is a dll. (look in something like ibm\mqseries\lib)
Did you install everything? Path settings okay? (same thing on unix)
Greetings,
Tom

Similar Messages

A problem when I try to create a application view throug a Bea MQSeries Adapter8.1

          Hi, guys!
          I have installed Weblogic platform 8.1 beta, and try to use the MQSeries Adapter
          which provide by Bea weblogic, and it's seems I must deploy the .ear file which
          is an application include the MQ Adapter, on a domain which provide the Integration
          function, the ear file I was download from bea site. So I deploy it in the samples/domain/platform
          domain as the docs told me. And after that I create a new directory called session
          and a subdirectory contain a manifest.xml file, I do this also due to the docs
          provide by Bea. And then I can create the application view in the application
          view console, BUT, when I try to add a Event in the console, the page and OS console
          both print this message :
          DEBUG 21 ?? 2003 20:43:11,906 BEA_MQSERIES_1_0.DesignTime - getMergedDictionary
          got exception:
          DEBUG 21 ?? 2003 20:43:11,906 BEA_MQSERIES_1_0.DesignTime -
          StackTrace:
          java.lang.NullPointerException
          at com.ibi.beamqseries.web.DesignTimeRequestHandler.getMergedDictionary(DesignTimeRequestHandler.java:372)
          at jsp_servlet.__addservc._jspService(__addservc.java:120)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1047)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:383)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:301)
          at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:547)
          at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:364)
          at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:153)
          at jsp_servlet.__display._jspService(__display.java:632)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1047)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:383)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:301)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6319)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3525)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2553)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          And I'm not quit sure about how to make the Schema directory correcttly, I just
          make one manifest.xml file. and hope I can find more document about the adapter,
          or can fix this problem.
          by the way, I just have userguid, installguide and releasenotes pdf file which
          can be download from Bea
          Regards,
          shannon


Can you tell me the exact url of the BEA_MQSERIES_8_1.ear?
          Please give it to me... Thanks in advance...

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

MQSeries and JAVA

I'm trying to use the MqSeries classes with JAVA. I put the import com.ibm.mq.* statement in my program but I get an error that the package does not exist. What folder should the MQ Classes be in? I am using JDK1.3.0_02.
Thanks

You will have to include the necessary MQ jar files in your classpath.
If using a builder, you will have to import the jar files into the builder so that the builder knows that the packages/classes exist.

Error/Exception handling in MQSeries

Hi,
What is the robust (yet simple) way to handle any exception generated while doing any operation in MQ Series for e.g. putting messages on queue.
Currently i have just done exception handling using try/catch blocks in my java application.
Kindly explain.
Thanks,
Sahil

This forum is specific to the Sun Java System Message Queue
product and is not a forum on IBM's MQSeries product.
If you have a question on MQSeries, you may want to look for a forum on IBM's site.

Problems while doing a rollback on MQSeries using a java client

Hi,
I'm new to using MQSeries with Java client. I have a kind of similar problem. I have a set of messages in a Queue. When i'm doing a rollback on certain message it's returing to the same pointer where it had come from in the queue. When i'm iterating through the messages in the queue using a for loop, the same message is again retireved. So, i tried to set the setMQGMO_MARK_SKIP_BACKOUT flag to true. But i'm getting an RequestException with error code 2046: MQRC_OPTIONS_ERROR
Any help on this would be highlly appreciated.
I'm pasting the code snippet below.
Class X {
public void receive(
com.stc.connector.webspheremqadapter.message.IMessage input, com.stc.connector.webspheremqadapter.message.IMqOtd
MQSeries_1){
int msginqueue = MQSeries_1.getCurrentDepth();
String corrID = "";
byte[] corrIDInputArray = input.getMsgHeader().getCorrelationId();
String corrInputID = (new String( corrIDInputArray )).trim();
for (int i = 0; i < msginqueue; i = i + 1) {
MQSeries_1.getQueue().getGMO().setMQGMO_SYNCPOINT( true );
MQSeries_1.getQueue().getWithOptions();
byte[] corrIDArray = MQSeries_1.getMessage().getMsgHeader().getCorrelationId();
corrID = (new String( corrIDArray )).trim();
if (corrID.equalsIgnoreCase( corrInputID )) {
MQSeries_1.commit();
} else {
MQSeries_1.getQueue().getGMO().setMQGMO_MARK_SKIP_BACKOUT( true );
MQSeries_1.backout();
}

I agree that you should check for a specific axis / tomcat forum (maybe on apache website??;)) anyway ... check the path and classpath you use while building the wsdd file and when running the adminclient, and check the syntax of its invokation

JMS, MQSeries, R/3 Link, NT and AIX...

Hi all,
To put you in situation, I have a java application which can run from any type of OS as of now. It sends documents to a queue (IDOCS) and those documents are then sent to SAP by an R/3 Link adapter. Using native binding and running the java application on the same computer as the QueueManager (AIX) it was all working fine.
Now, I have translated my app to use JMS instead and tried to run it on my Windows 2000 PC. The message are sent allrigth to the queue, but R/3 Link is now giving me a handfull of errors, complaining about conversion, character sets and things like that.
Here is a sample of errors I get:
02/18/03 17:00:39 SMQ4165: Warning on MQGET from inbound queue. Reason code 2110.
EXPLANATION: The attempt to get a message from the inbound message queue returned a warning. The warning code was 2110. The message will be passed to the use
r exit if one has been specified. If no exit was specified, the message will be passed to the bad message queue. If no bad message queue was specified, the
message will be left on the inbound queue, and the server will terminate.
ACTION: None.
02/18/03 17:00:39 SMQ4192: A data conversion problem occurred on the MQGET. Attempting to process message.
EXPLANATION: A warning was issued because the message needs codepage conversion, but the message is either not in MQSTR format, or a user-defined data- conver
sion exit call failed.
ACTION: Ensure that incoming messages from machines with a different code page, are in MQSTR format or that there is a user exit defined to convert messages i
n other formats.
02/18/03 17:00:40 SMQ4167: IDoc has an invalid structure version. IDoc value="16777216". Expected value="1".
EXPLANATION: The value of the version field in the IDoc header structure contains an invalid value.
ACTION: Ensure that the IDoc message starts with a valid version of the Saplink header structure (MQSAPH).
02/18/03 17:00:40 SMQ4191: A message was put to the bad message queue. Bad message type 1, reason 4108.
EXPLANATION: The message was not in a valid IDoc format. The bad message type is 1 and the bad message reason is 4108.
ACTION: Check the bad message reason code in the bad message header of the message. Attempt to correct the error and send the message again.
I finally set the CCSID to 819 in the connection string, now I suspect that my problem is related to the encoding I use but I can't find what to set it to instead. I write everything in a ByteMessage by the way, just as I was doing it with the native bindings.
Does anyone know how I am supposed to set this up? What encoding type should I set it to? Is the CCSID correct? previously, I was setting the format this way: bytesMessage.format = "MQHSAP ";
But using JMS, there is no such property so I tried to just write it to the ByteMessage, not sure this works either...
Thanks in advance,
Daniel
If it can be of any help, here is a code fragment of what I am doing:
using native binding, which was working fine
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH");
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ");
for(int i = 28; i < 108; i++)
bytesMessage.writeByte(32);
bytesMessage.writeBytes(textMessage);
bytesMessage.encoding = MQC.MQENC_INTEGER_NORMAL;
bytesMessage.format = "MQHSAP ";
And using JMS:
//Test code
queue = session.createQueue("queue://" + manager + "/" + name + "?priority=5&persistence=2&targetClient=1&encoding=" +
MQC.MQENC_INTEGER_REVERSED + "&CCSID=819");
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH".getBytes());
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ".getBytes());
StringBuffer padding = new StringBuffer(80);
for(int i = 28; i < 108; i++)
padding.append(" ");
bytesMessage.writeBytes(padding.toString().getBytes());
bytesMessage.writeBytes("MQHSAP ".getBytes());
bytesMessage.writeBytes(textMessage.getBytes());
queueSender.send(bytesMessage);

Hi There,
I know you used JMS and Link for R/3.
Now I am doing the same but I am getting the same problem besides I am doing what you mention in the forum.
Can you give me a hand to fix this?
I have configured and MQSeries under win2003 and in the same machine a Link 4 R/3. I have a Java app using a .bindings file to connect to the Q and send a message the same way you did, but i am getting this error:
IDoc has an invalid structure header. IDoc value="RFH ". Expected value="SAPH".
IDoc has an invalid structure version. IDoc value="2". Expected value="1".
IDoc has an invalid system number. IDoc value=<T.
IDoc has an invalid client. IDoc value=�Y♦.
IDoc has an invalid language. IDoc value=.
A message was put to the bad message queue. Bad message type 1, reason 4110.
It seems as if the all the JMS headers are at the begining of the msg and it always throw the same error. it doesn't matter what data I put in the bytesMessage.
I would really appreciate your help.
Here a portion code of my SendMessage operation.
     public String EnviarMsg(String Msg) throws JMSException {
          String resp = null;
          try {
               if (getQueueSend() == null) {
                    // Create un objeto QueueSender como productor del mensaje.
                    setQueueSend(QSess.createSender(MQueue));
                    // Crear y enviar un mensaje a la cola.
               * Aqui viene codigo para enviar msgs a la cola en formato SAP
               txtMsg = QSess.createBytesMessage();
               txtMsg.writeBytes("SAPH".getBytes());
               txtMsg.writeInt(1);
               txtMsg.writeInt(108);
               txtMsg.writeInt(273);
               txtMsg.writeInt(819);
               txtMsg.writeBytes("MQSTR ".getBytes());
               byte b = 32;
               for(int i=28; i<108; i++)
                    txtMsg.writeByte(b);
               txtMsg.writeBytes(Msg.getBytes());
               //txtMsg.encoding = MQC.MQENC_INTEGER_NORMAL;
               txtMsg.setStringProperty("JMS_IBM_Format", "MQHSAP ");
               //txtMsg.setText(Msg);
               // QueueSend.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
               // QueueSend.setTimeToLive(30000);Funciona. Probado con el MQSeries
               // 6.0
               QueueSend.send(txtMsg);
               resp = "OK";

JMS adapter error in MQSeries connection

Dear All,
i am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
     at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
     at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
     at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
     at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
     at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
Thanks and Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:32 PM
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:39 PM

Hi,
Check this as well [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm35210_.htm]
Regards,
Venkata S Pagolu

BizTalk : MQSeries adapter throwing error after 30 minutes idle time

We have BizTalk and windows MQSeries on separate servers. As long someone logged on to MQseries server, BizTalk able to communicate with MQSeries server and able to receive and send messages to MQs. If there is no session active on MQSeries server,
after 30 minutes BizTalk strat throwing following error. Once you log back to MQSeries server, it will work 30 more minutes.
Error: The adapter "MQSeries" raised an error message. Details "Retrieving the COM class factory for remote component with CLSID {....} from machine 192.... faied due to the following error : 8000401a 192....
Has any one encountered similar issue?
Thanks,
Chirag

Hi,
This seems to be permission issue. Please refer the similar thread
http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/13427a41-edd7-45fc-9d43-69838720d923
http://www.biztalkgurus.com/biztalk_server/biztalk_2006/f/10/p/5085/26750.aspx
Hope it can help you

IBM MqSeries configuration

hi all,
i m using mqseries 5.3. I have created Sender QMgr & Receiver QMgr & in that i have created sender queue & receiver queue.
In sender queue i have created two channels
1) Server connection channel
2) sender channel
In receiver queue i have created
1) receiver channel.
All the above mentioned things i have created using MQseries explorer & both these QMgrs are on the same machine.
When i tried to test communication between two channel using ping then i am getting following error on MQ Explorer
Unexpected Error(AMQ4048)
& in AMQERR01.log file i m getting the following error.
"AMQ6120: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 626 --------------------------------------------------------
12/11/2005 10:38:24
AMQ6184: An internal WebSphere MQ error has occurred on queue manager SenderQ.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1536.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 660 --------------------------------------------------------
12/11/2005 10:38:25"
can anyone pls help. i m looking for the solution from last 5 days.
pls its urgent
thanx a lot in adv.
reg,
ritu

I'm sure the people here will help if possible, but you'll probably have better luck on at http://www.mqseries.net/
I take it you've already tried the obvious...
http://www-1.ibm.com/support/docview.wss?uid=swg21110451

JMS adapter for MQSeries: Changing from MQ5.3 to 6.X libraries

Hi,
Can someone point in the direction of documentation as to how I would migrate/update a BPEL 10.1.3.5.0 environment using JMS adapters for MQSeries 5.3 to use new libraries for MQSeries 6.x.
In a test env I have located the following, but I am not sure now to proceed.
[bpel@omv2rrm2 5.3]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3
[bpel@omv2rrm2 5.3]$
[bpel@omv2rrm2 5.3]$ ls -l
total 2124
-rwx------ 1 bpel dba 352652 Apr 17 2008 com.ibm.mq-5.3.jar
-rwx------ 1 bpel dba 1798896 Apr 17 2008 com.ibm.mqjms-5.3.jar
[bpel@omv2rrm2 5.3]$
...and...
[bpel@omv2rrm2 config]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/config
[bpel@omv2rrm2 config]$ cat server.xml
<?xml version="1.0"?>
<application-server xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/application-server-10_1.xsd" localhostIsAdmin="true"
application-directory="../applications"
check-for-updates="adminClientOnly"
deployment-directory="../application-deployments"
connector-directory="../connectors"
schema-major-version="10" schema-minor-version="0" >
<shared-library name="global.libraries" version="1.0" library-compatible="true">
<code-source path="../applib"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>
<shared-library name="oracle.mqseries" version="5.3">
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mqjms-5.3.jar"/>
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mq-5.3.jar"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>

Just upgrade your SOA to 10.1.3.5.0 and then point to the newer MQ jars in those 2 files.

Remote queue in XI server for IBM MQSeries

Dear All,
my scenario is IBM MQSeries -> message via sender JMS adapter -> XI -> receiver RFC adapter -> R/3.
now for IBM MQSeries to send a message to XI via a transmission queue in MQSeries - it needs a remote queue name and queue manager name in XI server.
So now where can i find these information regarding remote queue name and queue manager name in XI server. I currently do not know whether in XI server, currently is there any remote queue or not? So how to find this information. If we do not have remote queue manager in XI currently, then how to install a remote queue name and queue manager in XI server.
It is slightly urgent. So i request you all to please reply quickly.
Thanks and Regards,
Rajeev Gupta

Dear Sebastin,
Thanks for your inputs.
I have to connect to MQSeries 5.2.1 to XI server.
am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
One more question - should the queue manager in MQSeries server be a local or remote queue manager..........i was not able to create a remote queue manager in MQSeries 5.2.1 as by default it is creating a local queue manager.......
Thanks and Regards,
Rajeev Gupta

Newbie : Problem starting OPG for IBM MQseries: TNS-00530, Error Code 2

Hi All
First of all, if this is the wrong place to post this question, I apologize.
I have installed a new installation of Oracle 9.2.0.1 and at a separate home location the OPG for IBM MQSeries for 9.2.0.1 off the same bits.
The configuration said that the default SID of PG4MQS92 would be setup since I was using a local MQ queue manager but I didnt see any entries in the listener.ora or the tnsames.ora so added the following.
listener.ora
(SID_DESC =
(SID_NAME = pg4mqs92)
(ORACLE_HOME = C:\Software\oracle\pg4mqs92)
(PROGRAM = pg4mqs92)
tnsnames.ora
ORACLE_QM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = testmachine)(PORT = 1521))
(CONNECT_DATA =
(SID = pg4mqs92)
(HS=OK)
When I ran tnsping on ORACLE_QM it was resolved. But when I start the putsample.sql program after importing all the required packages using the pgmdeploy9.sql script I get the following output.
DECLARE
ERROR at line 1:
ORA-04052: error occurred when looking up remote object
[email protected]
ORA-00604: error occurred at recursive SQL level 1
ORA-28545: error diagnosed by Net8 when connecting to an agent
NCRO: Failed to make RSLV connection
ORA-02063: preceding 2 lines from PG4MQ
In the listener.log I see the following error
07-DEC-2005 07:34:19 * (CONNECT_DATA=(SID=pg4mqs92)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.100)(PORT=1271)) * establish * pg4mqs92 * 12500
TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
32-bit Windows Error: 2: No such file or directory
I noticed that during the install a boot file for the pgm4mqs92 SID was not found anywhere. Is it maintained in the registry, if so where ?
If the boot file is missing is there a sample I can use and where do I need to put it ?
Am running on Windows XP Professional.
Have been stuck with this a while and cannot find any information on this, so any help would be appreciated.
Thanks
- Deepak

I am getting the same error while starting or stopping the listener
LSNRCTL> start CSCLIST
Starting tnslsnr: please wait...
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
LSNRCTL> stop CSCLIST
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=CSCINDAE708070)(PORT=152
2)))
NL-00303: syntax error in NV string
TNS-01153: Failed to process string: (DESCRIPTION=(CONNECT_DATA=(CID=(PROGRAM=)
(HOST=)(USER=Manager(REMOVE)))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=CSCLIST)(VERS
ION=186646784)))
Pls help
Listener.ora:
# listener.ora Network Configuration File: D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
CSCLIST =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = CSCINDAE708070)(PORT = 1522))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1522))
SID_LIST_CSCLIST =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1\bin\oraclr11.dll")
ADR_BASE_CSCLIST = D:\Sagaya\11gDBhome

Message Bridge between WLS 6.1 sp3 and MQSeries 5.2

          Hi,
          I'm really struggling with getting the Message Bridge working with Weblogic 6.1
          sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
          machine. First I'll pose some questions that I have, then I discuss the error
          I'm getting. Here are my questions:
          1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
          ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
          ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
          jms destination bridge and my weblogic queue is the target jms destination bridge,
          what values do I set for the listed config-properties? I can't seem to find any
          documentation on what these values should be. Am I missing something? Do these
          values even have to be set?
          2. When I go to install a Weblogic instance to a different physical machine what
          has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
          and Weblogic on a different physical machineB. I want machineA to forward all
          messages placed on a MQSeries Queue to forward them to machineB where the weblogic
          Queue resides. Does machineB also have to contain an MQSeries installation?
          Or can I just grab the necessary libraries and jar files and place them on the
          Weblogic machineB so they can be included?
          3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
          onto a different physical server that I cannot use Exactly-once quality of service?
          Other notes:
          1. I have the following patches installed for Weblogic 6.1 sp3:
          CR081404_610sp3.jar
          CR081511_61sp3.jar
          2. Here is the commands I used to create my ConnectionFactory and Queue within
          MQSeries:
          def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
          def q(MQTestQueue) qmanager(QM_jeff) queue(default)
          Okay...here is my error:
          <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
          "Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
          reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
          javax.resource.ResourceException: Error creating consumer or receiving message
          at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
          at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
          at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
          at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
          at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
          at $Proxy82.receive(Unknown Source)
          at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
          at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
          at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          Has anyone see this error before? Here is part of my ra.xml file....I just put
          these entries in to see what happens:
          <config-property>
          <config-property-name>ConnectionURL</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
          </config-property>
          <config-property>
          <config-property-name>InitialContextFactory</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
          </config-property>
          <config-property>
          <config-property-name>ConnectionFactoryJNDI</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>MQTestConnectionFactory</config-property-value>
          </config-property>
          <config-property>
          <config-property-name>DestinationJNDI</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>MQTestQueue</config-property-value>
          </config-property>
          <config-property>
          <config-property-name>DestinationType</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value></config-property-value>
          </config-property>
          <config-property>
          <config-property-name>AdapterType</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>XATransaction</config-property-value>
          </config-property>
          Here is a snip of my config.xml:
          <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
          Name="Messaging Bridge" QualityOfService="Atmost-once"
          SourceDestination="Source JMS Bridge Destination"
          TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
          <JMSBridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          ConnectionFactoryJNDIName="MQTestConnectionFactory"
          ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
          DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
          Name="Source JMS Bridge Destination"/>
          <JMSBridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
          ConnectionURL="t3://localhost:7001"
          DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
          InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
          JMS Bridge Destination"/>
          Any help would be greatly appreciated. Thank you in advance for your help.
          Sincerely,
          Jeff


          I tried your suggestion and it worked!! The only thing is, it
          makes the deployment of the resource adapter a little more
          complicated. Now my customers are going to have to edit their
          config.xml, instead of just dropping in the appropriate rar into
          the applications directory. But one nice side affect of placing
          the rar's in a different directory is it makes the Message
          Bridge a little more stable. I was finding it to be very
          unstable. One time I would startup my Application Server and
          everything was fine, then I would shutdown. The next time I
          started it up, I would get exceptions. I have yet to see that
          behavior with this new configuration.
          Thanks again for all of your help, it is greatly appreciated!!
          Jeff
          Dongbo Xiao <[email protected]> wrote:
          >Looks like that somehow you have the adapter deployed
          >multiple times, may not be intended. The cause is that
          >everything in the application directory will be automatically
          >deployed and all of them are added to the config.xml. During
          >the next boot, those appear in the config.xml will be deployed and
          >everything in the application directory too. As a result, the adapters
          >are deployed twice. The complain about runtime mbean not found may
          >mean the one that is overridden by the new one.
          >
          >The work around is not to put your adapters in the application
          >directory, instead, put them in a different directory and point to
          >the directory in your config.xml.
          >
          >Dongbo
          >Jeff wrote:
          >>
          >> One more thing...
          >> I noticed that the exception specified that it couldn't find
          >> mydomain:Location=myserver,Name=jms-xa-
          >> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
          >> time MBean, but what's interesting that if I run the following
          >> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
          >> property ActiveConnectionsCurrentCount -url
          >> http://localhost:7001 -username xxxx -password xxxx I get the
          >> following output:
          >>
          >> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
          >> adp_Pool_3,ServerRuntime=myse
          >> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
          >> tCount=0}}
          >> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
          >> adp_Pool_2,ServerRuntime=
          >> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
          >> rrentCount=0}}
          >>
          >> So from that...it looks like the MBean is there. Any ideas why it
          >is not being
          >> found?
          >>
          >> Thanks,
          >>
          >> Jeff
          >>
          >> "Jeff" <[email protected]> wrote:
          >> >
          >> >
          >> >
          >> >Thank you very much!!
          >> >
          >> >I tried your suggestions and created a general Queue Connection Factory
          >> >within
          >> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
          >the
          >> >jms-notrans-adp.rar
          >> >resource adapter. With this configuration, I can send messages to
          >MQSeries
          >> >and
          >> >they get forwarded to Weblogic.
          >> >
          >> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
          >> >get the bridge
          >> >working at all. I realize that MQSeries has a bug with Transactions
          >> >and remote
          >> >servers, but I have MQSeries and Weblogic running on the same machine.
          >> > I thought
          >> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
          >JMS
          >> >Bridge
          >> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
          >and
          >> >it should
          >> >work? I tried it and it didn't work. ( see attachment for weblogic.log
          >> >showing
          >> >exception ).
          >> >
          >> >Here is my config.xml:
          >> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
          >> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
          >> > QualityOfService="Exactly-once"
          >> > SourceDestination="Source JMS Bridge Destination"
          >> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
          >> > <JMSBridgeDestination
          >> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
          >> > ConnectionURL="t3://localhost:7001"
          >> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
          >Name="Target
          >> >JMS Bridge Destination"/>
          >> > <JMSBridgeDestination
          >> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          >> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
          >> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
          >> > DestinationJNDIName="MQTestQueue"
          >> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
          >> >Name="Source
          >> >JMS Bridge Destination"/>
          >> >
          >> >Again, thank you very much for your response. It helped me a great
          >deal.
          >> > Any
          >> >thoughts on the above problem please foward them along.
          >> >
          >> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
          >> >file is
          >> >dated 8/13/2002
          >> >
          >> >
          >> >Sincerely,
          >> >
          >> >Jeff
          >> >
          >> >Dongbo Xiao <[email protected]> wrote:
          >> >>Please see my comments inline.
          >> >>
          >> >>
          >> >>Jeff wrote:
          >> >>>
          >> >>> Hi,
          >> >>> I'm really struggling with getting the Message Bridge working with
          >> >>Weblogic 6.1
          >> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
          >> >>Windows 2000
          >> >>> machine. First I'll pose some questions that I have, then I discuss
          >> >>the error
          >> >>> I'm getting. Here are my questions:
          >> >>>
          >> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
          >> >> Within the
          >> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
          >> >>InitialContextFactory,
          >> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
          >> >is
          >> >>the source
          >> >>> jms destination bridge and my weblogic queue is the target jms
          >destination
          >> >>bridge,
          >> >>> what values do I set for the listed config-properties? I can't
          >seem
          >> >>to find any
          >> >>> documentation on what these values should be. Am I missing something?
          >> >> Do these
          >> >>> values even have to be set?
          >> >>>
          >> >>
          >> >>You DON'T have to do anything to the adapter deployment descriptor
          >> >>files.
          >> >>The values given there for the listed config-properties are just
          >default
          >> >>values.
          >> >>The values configured in JMSBridgeDestination instances are the values
          >> >>used to
          >> >>override the default values in the dd file.
          >> >>
          >> >>> 2. When I go to install a Weblogic instance to a different physical
          >> >>machine what
          >> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
          >on
          >> >>physical machineA
          >> >>> and Weblogic on a different physical machineB. I want machineA
          >to
          >> >>forward all
          >> >>> messages placed on a MQSeries Queue to forward them to machineB
          >where
          >> >>the weblogic
          >> >>> Queue resides. Does machineB also have to contain an MQSeries
          >installation?
          >> >>> Or can I just grab the necessary libraries and jar files and place
          >> >>them on the
          >> >>> Weblogic machineB so they can be included?
          >> >>>
          >> >>
          >> >>You don't have to install MQSeries on the machine that the WebLogic
          >> >>server is running. You need the necessary libraries and jar files
          >> >>though.
          >> >>
          >> >>> 3. Is it correct that if I distribute Weblogic onto one physical
          >server
          >> >>and MQSeries
          >> >>> onto a different physical server that I cannot use Exactly-once
          >quality
          >> >>of service?
          >> >>>
          >> >>
          >> >>That is correct and it is a MQSeries transaction limitation.
          >> >>
          >> >>> Other notes:
          >> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
          >> >>> CR081404_610sp3.jar
          >> >>> CR081511_61sp3.jar
          >> >>>
          >> >>
          >> >>What version of CR081511_61sp3.jar you have? You need the one dated
          >> >on
          >> >>8/13/2002.
          >> >>
          >> >>> 2. Here is the commands I used to create my ConnectionFactory
          >and
          >> >>Queue within
          >> >>> MQSeries:
          >> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
          >> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
          >> >>>
          >> >>
          >> >>The only possible error I see here is that you create a xaqcf while
          >> >your
          >> >>bridge
          >> >>is configured to have "Atmost-once" QOS. The bridge adapter will
          >create
          >> >>XASession
          >> >>if the connection factory is xa because it knows nothing about QOS
          >of
          >> >>the bridge.
          >> >>As I said, there is a limitation in MQSeries transactions, which
          >prevent
          >> >>the
          >> >>transaction to happen between remote servers. Although the bridge
          >does
          >> >>not
          >> >>start the the transaction in your case, but MQSeries xa connection
          >> >>factory may
          >> >>throw error when it detects the other side is remote. Having said
          >that,
          >> >>I am not
          >> >>completely sure this is the problem caused the bridge to fail. I
          >suggest
          >> >>you use
          >> >>a non-xa connection factory on the MQSeries side and see if the problem
          >> >>goes away.
          >> >>
          >> >>> Okay...here is my error:
          >> >>>
          >> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
          >> >>in bridge
          >> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
          >> >>java.lang.
          >> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
          >> >>> javax.resource.ResourceException: Error creating consumer or receiving
          >> >>message
          >> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
          >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
          >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
          >> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
          >> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
          >> >>> at java.lang.reflect.Method.invoke(Native Method)
          >> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
          >> >>> at $Proxy82.receive(Unknown Source)
          >> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
          >> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
          >> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          >> >>>
          >> >>
          >> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
          >> >>more error
          >> >>information.
          >> >>
          >> >>> Has anyone see this error before? Here is part of my ra.xml file....I
          >> >>just put
          >> >>> these entries in to see what happens:
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>ConnectionURL</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>InitialContextFactory</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>DestinationJNDI</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property-value>MQTestQueue</config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>DestinationType</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property-value></config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>> <config-property>
          >> >>> <config-property-name>AdapterType</config-property-name>
          >> >>> <config-property-type>java.lang.String</config-property-type>
          >> >>> <config-property-value>XATransaction</config-property-value>
          >> >>> </config-property>
          >> >>>
          >> >>
          >> >>As I said earlier, you are not supposed to change the adapter dd
          >file.
          >> >>
          >> >>
          >> >>> Here is a snip of my config.xml:
          >> >>>
          >> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
          >> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
          >> >>> SourceDestination="Source JMS Bridge Destination"
          >> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
          >> >>> <JMSBridgeDestination
          >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          >> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
          >> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
          >> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
          >> >>> Name="Source JMS Bridge Destination"/>
          >> >>>
          >> >>> <JMSBridgeDestination
          >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          >> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
          >> >>> ConnectionURL="t3://localhost:7001"
          >> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
          >> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
          >Name="Target
          >> >>> JMS Bridge Destination"/>
          >> >>>
          >> >>
          >> >>Your configuration of the bridge and bridge destinations look fine.
          >> >
          >> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
          >> >>and PATH for starting the WebLogic server that the bridge is running
          >> >>on.
          >> >>
          >> >>You can also turn on debug for more information.
          >> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
          >> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
          >> >>
          >> >>
          >> >>Thanks,
          >> >>Dongbo
          >> >

Error handling in MQSeries

Hi,
I am doing remote queuing for which I have defined two queue managers QM1 and QM2.
On QM1 I have defined a local queue Q1
On QM2 I have defined a remote queue R2 which is configured to point to Q1 on QM1
On QM2 I have defined a transmission q T2 to hold the messages
Now suppose the channels and connections defined on both the queue managers are not running and if I send messages on R2 (further to be sent to Q1) the messages won�t reach Q1 instead they will reside on T2.
I am using java code to put messages on the queue, the messages are successfully put on transmission queue but not on Q1(Since channels are not running), but the program does not throw any exception. How can i check for this condition in the java program?
Regards,
Sahil

This forum is specific to the Sun Java System Message Queue
product and is not a forum on IBM's MQSeries product.
If you have a question on MQSeries, you may want to look for a forum on IBM's site.

How to read messages from mqseries continuously by java?

Hi,
I'm sending messages to the queue of MQSeries.
Here my requirement is i have to write a java/jms program that should run at the back side and check the queue for every 5 minutes for messages.If any message exists in the queue the java/jms program should read the message and display it on the console.
If anybody has idea please reply it.
thanks in advance

Hi!
You have many ways. You could define a cron on a UNIX box to make sure a simple command line app connects to the queue every 5 min and uses JMS API to read the queue and do whatever you need with the messages.
http://java.sun.com/products/jms/javadoc-102a/index.html
On the other hand, unless its critical to recover messages just every 5 min., you could create an MDB. Actually this is the best solution: a Message Driven Enterprise Java Bean is just a listener over the queue reacting instantly to every message received. The way to create and configure them depends strongly on your appserver and development process: an IDE as WSAD or something like that creates them very easily. The actual problem with these ones is to properly configure them on your appserver. However, all appservers will allow you to define a 'Foreign JMS Provider' or something like that pointing to the actual MQ implementation you have and define an activation specification on which to sit your MDB.
Regards
Jorge

MQSERIES

Similar Messages

Maybe you are looking for