| Author |
Message
|
| venky |
 Posted: Thu Jun 22, 2006 1:37 pm Post subject: WBIA JDBC adapter - JMS QM creation/connection. |
 |
|
Master
Joined: 08 Jul 2003
Posts: 205
|
Hi All,
Iam trying to configure WBIA JDBC adapter with Process server as the integration broker. After the configurations, once I start the adapter, Iam getting the following error.
[Time: 2006/06/22 17:33:16.047] [System: ConnectorAgent] [SS: CaesarConnector] [
Thread: wbia_main (#1128372607)] [Type: Trace] [Mesg: :The Connection String is
WBIA_QM:WBIA.JMS.SVRCONN:localhost:5558]
[Time: 2006/06/22 17:33:16.156] [System: ConnectorAgent] [SS: CaesarConnector] [
Thread: wbia_main (#1128372607)] [Type: Info] [MsgID: 9055] [Mesg: Using Client
connection to the Queue Manager.]
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhos
t:WBIA_QM'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironm
ent.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:150)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueue
ConnectionFactory.java:185)
at CxCommon.Messaging.jms.JMSTransportUtil.initQueueConnection(JMSTransp
ortUtil.java:221)
at CxCommon.Messaging.jms.SessionMgr.createSession(SessionMgr.java:266)
at CxCommon.Messaging.jms.SessionMgr.getAgentSession(SessionMgr.java:119
)
at CxCommon.Messaging.ClientPacketSyncDrvFormatter.<init>(ClientPacketSy
ncDrvFormatter.java:173)
at CxCommon.Messaging.ClientTransportManager.<init>(ClientTransportManag
er.java:192)
at CxCommon.Messaging.ClientTransportManager.<init>(ClientTransportManag
er.java:214)
at AppSide_Connector.AgentBusinessObjectManager.setupTransport(AgentBusi
nessObjectManager.java:321)
at AppSide_Connector.AgentBusinessObjectManager.<init>(AgentBusinessObje
ctManager.java:265)
at AppSide_Connector.AppEnd.run(AppEnd.java:1435)
at AppSide_Connector.AppEnd.init(AppEnd.java:362)
at AppSide_Connector.AppEnd.<init>(AppEnd.java:137)
at AppSide_Connector.AppEnd.main(AppEnd.java:1069)
at AppEndWrapper.main(AppEndWrapper.java:2
[Time: 2006/06/22 17:33:17.297] [System: ConnectorAgent] [SS: CaesarConnector] [
Thread: wbia_main (#1128372607)] [Type: Trace] [Mesg: :Can NOT create JMS connec
tion to queue manager -- WBIA_QM:WBIA.JMS.SVRCONN:localhost:5558]
[Time: 2006/06/22 17:33:17.297] [System: ConnectorAgent] [SS: CaesarConnector] [
Thread: wbia_main (#1128372607)] [Type: Error] [MsgID: 9052] [Mesg: Unable to ge
t a MQ series Queue Manager or Queue Connection. Reason: failed to create connec
tion --javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'l
ocalhost:WBIA_QM'.]
Press any key to continue . . .
has anyone come across similar/same issue. Any help is appreciated.
Thank you,
Venky... |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Jun 22, 2006 1:45 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Is this QMGR running?
WBIA_QM
Is it running on the right port 5558
Is the channel WBIA.JMS.SVRCONN created. |
|
| Back to top |
|
|
| venky |
| Posted: Thu Jun 22, 2006 2:04 pm Post subject: |
|
|
Master
Joined: 08 Jul 2003
Posts: 205
|
Thank you for your reply...
My assumption is When we deploy the respective module to the WPS server, its suppose to create the JMS queue managers and queues. The default port is suppose to be 5558. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jun 22, 2006 3:14 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Your assumption is wrong.
I think what you are guessing is that a default messaging engine would be created for you. If you create a mediation for the default messaging engine and real MQ, and then create channels to the real QMGR, then the default port is 5558. You should be better off by giving the real QMGR and real Queues and define them as resources in WPS.
That way these queues will be available and accessible for both WPS and WBI adapter.
On the other hand if you use WebSphere Adapter then that might create a Bus for you. |
|
| Back to top |
|
|
| venky |
| Posted: Tue Jun 27, 2006 12:26 pm Post subject: |
|
|
Master
Joined: 08 Jul 2003
Posts: 205
|
| Quote: |
| Your assumption is wrong. ....If you create a mediation for the default messaging engine and real MQ, and then create channels to the real QMGR, then the default port is 5558. |
I didn't understand you there.
In the model Iam building, there is no real MQ ( WMQ ) involved. The delivery transport is JMS. When I create the WPS Module using Enterprise service discovery agent, and deploy this to Websphere Process Server, JMS queues and QM will be created along with deployment.
I am facing some issues with the adapter startup.
Thank you. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jun 27, 2006 4:56 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| When I create the WPS Module using Enterprise service discovery agent, and deploy this to Websphere Process Server, JMS queues and QM will be created along with deployment. |
Those queues and QMs cannot be accessed outside of WPS. If you were running WebSphere Adapters, then that would make sense. But you are saying that you are using WBIAdapters. These run outside of WPS. So you need to configure something that can talk to default messaging that comes with WPS. |
|
| Back to top |
|
|
| midhunkalyan |
| Posted: Fri Jul 14, 2006 1:54 pm Post subject: Is the problem solved - I am also getting the same error |
|
|
Newbie
Joined: 14 Jul 2006
Posts: 2
|
Hi venky,
I am trying to start the JText adapter similar to ur case. I am trying to talk to WPS (Websphere MQ Client link). I am also getting the same exception as u were getting - Did u find out a solution for this one.
It would be great if u can post the solution if u did find out.
Thanks
Midhun |
|
| Back to top |
|
|
|
|
