| Author |
Message
|
| jayjain |
 Posted: Mon Mar 26, 2007 12:37 am Post subject: getting prob during Publish a message after process |
 |
|
Newbie
Joined: 26 Mar 2007
Posts: 5
|
I am getting problem during publish any message.
Scnerio : We get request from some queue and doing processing after that we publish it to another queue.
There are two cases :
1)When we get single request after processing and dring publisheing we are getting prob in queueSender.send(message);
2) where there are multiple records in request, it's processed and published sucesssfully.
Please let me know if you require more info.
Thanks in advance.
Jay Jain
jay.jain@birlasoft.com |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 26, 2007 12:49 am Post subject: Re: getting prob during Publish a message after process |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jayjain wrote: |
1)When we get single request after processing and dring publisheing we are getting prob in queueSender.send(message);
|
Any reason codes, log entries, trace, diagnostic, other symptoms or is it just "getting prob".
Also what version of MQ are you running and on what platform. Are you using the base WMQ pub/sub or WMB?
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Mon Mar 26, 2007 12:50 am; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 26, 2007 12:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That sounds very much like a problem in your code.
What is the problem you get in the send method? Does it throw an exception? Does that exception have a LinkedException attached?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jayjain |
| Posted: Mon Mar 26, 2007 1:48 am Post subject: |
|
|
Newbie
Joined: 26 Mar 2007
Posts: 5
|
| jefflowrey wrote: |
That sounds very much like a problem in your code.
What is the problem you get in the send method? Does it throw an exception? Does that exception have a LinkedException attached? |
If I changed the MQ server its working fine so, I hope Code is OK.
I am using : IBM MQ Clent version 5.3
I am getting this error:
2007-03-20 04:33:34,418 INFO [STDOUT] QueueConnection / Queue Object Created
2007-03-20 04:33:35,888 INFO [STDOUT] javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1589)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1012)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1046)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ge.vfs.oscar.framework.JMSPublisher.publishMessage(JMSPublisher.java:178)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ge.vfs.oscar.controller.OSCARResponseController.publishResponse(OSCARResponseController.java:238)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ge.vfs.oscar.controller.OSCARResponseController.provideResponse(OSCARResponseController.java:6
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ge.vfs.oscar.controller.OSCARRequestController.handleRequest(OSCARRequestController.java:71)
2007-03-20 04:33:35,888 INFO [STDOUT] at com.ge.vfs.oscar.mdb.OSCARMDBBean.onMessage(OSCARMDBBean.java:138)
2007-03-20 04:33:35,888 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
2007-03-20 04:33:35,888 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2007-03-20 04:33:35,888 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:475)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:87)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:4
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:316)
2007-03-20 04:33:35,888 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:149)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.plugins.contact admin.invoke(contact admin.java:95)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java:854)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:920)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1213)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
2007-03-20 04:33:35,889 INFO [STDOUT] at com.ibm.mq.jms.MQSession.run(MQSession.java:1650)
2007-03-20 04:33:35,889 INFO [STDOUT] at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
2007-03-20 04:33:35,889 INFO [STDOUT] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
2007-03-20 04:33:35,889 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534)
Thanks for your first responce.. Please tell me if you require more info... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 2:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Does that exception have a LinkedException attached? |
You need to code to obtain the LinkedException, which will contain the MQ reason code.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jayjain |
| Posted: Mon Mar 26, 2007 2:52 am Post subject: |
|
|
Newbie
Joined: 26 Mar 2007
Posts: 5
|
| Vitor wrote: |
| jefflowrey wrote: |
| Does that exception have a LinkedException attached? |
You need to code to obtain the LinkedException, which will contain the MQ reason code. |
This is the MQ reason but for multiple records processing its not giving this error.
AMQ9604: Channel 'JAVA.CHANNEL.OSCAR' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'JAVA.CHANNEL.OSCAR' is no longer
running. The check process system call returned 545284357 for process 4092.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 3:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Pedantically, that's not the reason code contained in the Linked Exception but a log entry. The reason code is a 4 digit number; if that log entry is indeed the matching one, it's probably a 2019. But not for certain, which is why the linked exception is important.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 3:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
In the meantime, what kind of channel is "JAVA.CHANNEL.OSCAR"? How is it defined? How does your Java access it (JNDI?)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jayjain |
| Posted: Mon Mar 26, 2007 3:09 am Post subject: |
|
|
Newbie
Joined: 26 Mar 2007
Posts: 5
|
May be it will help with this (1348)
----- amqrcsia.c : 1348 -------------------------------------------------------
03/19/2007 04:06:22
AMQ9604: Channel 'JAVA.CHANNEL.OSCAR' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'JAVA.CHANNEL.OSCAR' is no longer
running. The check process system call returned 545284357 for process 4092.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 3:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jayjain wrote: |
| May be it will help with this (1348) |
No, that's no help at all. Does this number has any context?
Just post the Linked Exception. You may think it's pointless, you may be right, but humour me. 
Also the answers to the channel questions I asked.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jayjain |
| Posted: Mon Mar 26, 2007 3:36 am Post subject: |
|
|
Newbie
Joined: 26 Mar 2007
Posts: 5
|
Please tell me if this will help you...
We are using bindings where all the things are defined like channel name etc..
these are the chennels defined there on MQ Server for particular MQ Manager.
Pls got the below details how we are accessing the Details from .bindings into OSCAR
1. QueueConnectionFactoryName=ctxOSCAR/QOSCARCF
2. QueueName=ctxOSCAR/QOSCARPUB
and in the code we are using like
String ctxFactory = bundle.getString("contextFactory");
String providerURL = bundle.getString("providerUrl");
String qcfName = bundle.getString("QueueConnectionFactoryName");
String qName = bundle.getString("QueueName");
Contents of bindings file :
#This file is used by the JNDI FSContext.
#Fri Mar 09 11:45:17 EST 2007
TEST.QUEUE/RefAddr/6/Encoding=String
QOSCAR/RefAddr/2/Encoding=String
QOSCARPUB/RefAddr/6/Type=ENC
QOSCARPUB/RefAddr/9/Content=HUB
QOSCARPUB/RefAddr/4/Encoding=String
QOSCAR/RefAddr/4/Encoding=String
TEST.QUEUE/RefAddr/8/Encoding=String
QOSCARPUB/RefAddr/7/Content=1
TEST.QUEUE/RefAddr/7/Type=FIQ
QOSCARCF/RefAddr/8/Type=UCP
QOSCARCF/RefAddr/6/Content=819
TEST.QUEUE/FactoryName=com.ibm.mq.jms.MQQueueFactory
QOSCAR/RefAddr/9/Type=QMGR
QOSCARPUB/RefAddr/6/Encoding=String
QOSCARPUB/RefAddr/5/Content=0
QOSCARCF/RefAddr/14/Type=MRET
QOSCARPUB/RefAddr/0/Type=VER
QOSCAR/RefAddr/6/Encoding=String
QOSCARCF/RefAddr/4/Content=1416
TEST.QUEUE/RefAddr/9/Content=
QOSCAR/RefAddr/3/Content=-2
TEST.QUEUE/ClassName=com.ibm.mq.jms.MQQueue
QOSCARPUB/RefAddr/8/Encoding=String
TEST.QUEUE/RefAddr/1/Type=EXP
QOSCARCF/RefAddr/2/Content=
QOSCAR/RefAddr/8/Encoding=String
QOSCARCF/RefAddr/2/Type=QMGR
QOSCAR/RefAddr/1/Content=-2
QOSCAR/RefAddr/3/Type=PER
TEST.QUEUE/RefAddr/7/Content=1
QOSCARPUB/FactoryName=com.ibm.mq.jms.MQQueueFactory
QOSCAR/ClassName=com.ibm.mq.jms.MQQueue
QOSCARCF/RefAddr/13/Content=SYSTEM.DEFAULT.MODEL.QUEUE
QOSCARPUB/RefAddr/7/Type=FIQ
QOSCARCF/RefAddr/11/Content=1
TEST.QUEUE/RefAddr/8/Type=QU
QOSCARPUB/RefAddr/3/Content=-2
QOSCARCF/RefAddr/9/Type=PINT
QOSCARPUB/RefAddr/1/Type=EXP
QOSCARPUB/RefAddr/1/Content=-2
QOSCARCF/RefAddr/0/Content=2
TEST.QUEUE/RefAddr/2/Type=PRI
TEST.QUEUE/RefAddr/5/Content=0
QOSCARCF/RefAddr/10/Encoding=String
QOSCARCF/RefAddr/3/Type=HOST
QOSCAR/RefAddr/4/Type=CCS
TEST.QUEUE/RefAddr/3/Content=-2
QOSCARCF/RefAddr/12/Encoding=String
TEST.QUEUE/RefAddr/1/Content=-2
QOSCARCF/RefAddr/1/Encoding=String
QOSCARPUB/RefAddr/8/Type=QU
QOSCARCF/RefAddr/14/Encoding=String
TEST.QUEUE/RefAddr/9/Type=QMGR
QOSCARPUB/RefAddr/1/Encoding=String
QOSCARCF/RefAddr/3/Encoding=String
QOSCAR/RefAddr/1/Encoding=String
QOSCARPUB/RefAddr/2/Type=PRI
QOSCARCF/RefAddr/9/Content=5000
QOSCARCF/RefAddr/5/Encoding=String
TEST.QUEUE/RefAddr/1/Encoding=String
QOSCAR/RefAddr/8/Content=UNIX.OSCAR.SIEBEL.RECEIVE
TEST.QUEUE/RefAddr/3/Type=PER
QOSCARCF/RefAddr/4/Type=PORT
QOSCAR/RefAddr/5/Type=TC
QOSCARCF/RefAddr/7/Encoding=String
QOSCAR/RefAddr/6/Content=273
QOSCARCF/RefAddr/10/Type=MBS
TEST.QUEUE/RefAddr/3/Encoding=String
QOSCARCF/RefAddr/9/Encoding=String
TEST.QUEUE/RefAddr/5/Encoding=String
QOSCARPUB/RefAddr/9/Type=QMGR
QOSCAR/FactoryName=com.ibm.mq.jms.MQQueueFactory
QOSCARPUB/RefAddr/3/Encoding=String
TEST.QUEUE/RefAddr/7/Encoding=String
QOSCAR/RefAddr/3/Encoding=String
QOSCARPUB/RefAddr/8/Content=UNIX.OSCAR.SIEBEL.SEND
QOSCARCF/RefAddr/14/Content=1
QOSCARCF/RefAddr/7/Content=false
QOSCARPUB/RefAddr/3/Type=PER
QOSCARPUB/RefAddr/5/Encoding=String
QOSCAR/RefAddr/5/Encoding=String
QOSCARPUB/RefAddr/6/Content=273
TEST.QUEUE/RefAddr/9/Encoding=String
QOSCARCF/RefAddr/5/Content=JAVA.CHANNEL.OSCAR
QOSCARPUB/ClassName=com.ibm.mq.jms.MQQueue
TEST.QUEUE/RefAddr/4/Type=CCS
QOSCARPUB/RefAddr/4/Content=1208
QOSCAR/RefAddr/4/Content=1208
QOSCARCF/RefAddr/5/Type=CHAN
QOSCARPUB/RefAddr/7/Encoding=String
QOSCAR/RefAddr/7/Encoding=String
QOSCAR/RefAddr/6/Type=ENC
QOSCARCF/RefAddr/3/Content=3.131.89.35
QOSCARCF/RefAddr/11/Type=FIQ
TEST.QUEUE/RefAddr/8/Content=TEST.QUEUE
QOSCAR/RefAddr/2/Content=-2
QOSCARCF/RefAddr/1/Content=1
QOSCARPUB/RefAddr/9/Encoding=String
QOSCAR/RefAddr/9/Encoding=String
QOSCAR/RefAddr/0/Content=1
QOSCAR/RefAddr/0/Type=VER
QOSCARCF/RefAddr/12/Content=5000
QOSCARCF/RefAddr/10/Content=10
QOSCARPUB/RefAddr/4/Type=CCS
QOSCARPUB/RefAddr/2/Content=-2
TEST.QUEUE/RefAddr/5/Type=TC
QOSCARCF/RefAddr/6/Type=CCS
TEST.QUEUE/RefAddr/6/Content=273
QOSCAR/RefAddr/7/Type=FIQ
QOSCARPUB/RefAddr/0/Content=1
QOSCARCF/RefAddr/12/Type=RINT
TEST.QUEUE/RefAddr/4/Content=1208
QOSCARCF/RefAddr/11/Encoding=String
QOSCARCF/RefAddr/0/Type=VER
TEST.QUEUE/RefAddr/2/Content=-2
QOSCAR/RefAddr/1/Type=EXP
QOSCARCF/RefAddr/0/Encoding=String
QOSCARCF/RefAddr/13/Encoding=String
QOSCARCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
QOSCARCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
QOSCARPUB/RefAddr/0/Encoding=String
QOSCARCF/RefAddr/2/Encoding=String
QOSCAR/RefAddr/0/Encoding=String
QOSCARPUB/RefAddr/5/Type=TC
QOSCARPUB/RefAddr/2/Encoding=String
QOSCARCF/RefAddr/4/Encoding=String
TEST.QUEUE/RefAddr/6/Type=ENC
TEST.QUEUE/RefAddr/0/Encoding=String
QOSCARCF/RefAddr/7/Type=SPAG
QOSCAR/RefAddr/9/Content=HUB
QOSCAR/RefAddr/8/Type=QU
QOSCARCF/RefAddr/13/Type=TM
QOSCARCF/RefAddr/8/Content=true
QOSCARCF/RefAddr/6/Encoding=String
TEST.QUEUE/RefAddr/2/Encoding=String
QOSCAR/RefAddr/7/Content=1
TEST.QUEUE/RefAddr/0/Content=1
TEST.QUEUE/RefAddr/0/Type=VER
QOSCAR/RefAddr/5/Content=0
QOSCARCF/RefAddr/8/Encoding=String
QOSCARCF/RefAddr/1/Type=TRAN
TEST.QUEUE/RefAddr/4/Encoding=String
QOSCAR/RefAddr/2/Type=PRI |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2007 3:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jayjain wrote: |
these are the chennels defined there on MQ Server for particular MQ Manager.
|
I doubt you have channels called TEST.QUEUE.....
Perhaps I should have been a bit more explicit. When I said "channel definition" I meant the definition of the channel on the queue manager, rather than the JNDI entry controlling it. You may need to speak to your MQ Admin about this.
How's production & posting of the Linked Exception coming?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
