Hi Niels,
> Hello Binod,
>
> I tried your suggestion about writing a small client application. This
> gave me the same error.
> In the meanwhile IBM proposed a workaround for an internal error we
> see at the MQ server. (something DCOM related). We applied the
> workaround but the error persists.
> However we do get an exception with a stacktrace at the moment.:
>
> MQJMS1016E an internal error has occurred. Please contact your system
> administrator. Detail: com.ibm.mq.MQException: MQJE001: Completion
> Code 2, Reason 2019
>
> MQJMS2007: failed to send message to MQ queue
> javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
> at
> com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
>
This seems to be a pretty common exception. We can get more information
about the
exception by getting the linked exception.
try
{
<ur code>
}
catch (JMSException jmsx)
{
jmsx.printStackTrace();
Exception ex = jmsx.getLinkedException();
if (ex!=null)
{
ex.printStackTrace();
}
}
Can you try this?
- Binod.
> at
> com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1589)
>
> at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1012)
> at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1046)
> at
> com.ardatis.ventouris.rsvz.client.RSVZB2BClient.sendMessage(RSVZB2BClient.java:28)
>
> at
> com.ardatis.ventouris.rsvz.client.AbstractRSVZB2BClient.startProcess(AbstractRSVZB2BClient.java:107)
>
> at
> com.ardatis.ventouris.rsvz.client.RSVZB2BClient.main(RSVZB2BClient.java:14)
>
>
>
> Kind regards,
>
> Niels
>
>
> On 7/28/06, Binod <Binod.Pg_at_sun.com> wrote:
>
>> Hmm....
>>
>> Are you able to use a simple java client to work with the MQ server?
>>
>> - Binod.
>>
>> > Hi Binod,
>> >
>> >> >
>> >> > MQJMS1016E an internal error has occurred. Please contact your
>> system
>> >> > administrator. Detail: com.ibm.mq.MQException: MQJE001: Completion
>> >> > Code 2, Reason 2019
>> >>
>> >> Do you have a full stack trace?
>> >
>> >
>> > No that is something I really can't obtain. I already tried increasing
>> > the log levels of the application server. I also debugged while
>> > catching the exception, but the exception doesn't have a stacktrace.
>> >
>> >>
>> >> >
>> >> > I realize that the problem is probably located at the MQ Series
>> >> > server. And therefore we are logging a support case at IBM.
>> >>
>> >> Mostly it should be an MQ series issue. Are you sure that the
>> >> listener ports
>> >> are working fine?
>> >
>> >
>> > Yes the listener ports are working fine. I traced a session with
>> > ethereal (a network monitoring tool) and there you can see that the
>> > appserver is opening a connection to the mqserver, issues a MQ_CONN,
>> > MQ_OPEN and a MQ_PUT statement, but after that the connection is
>> > closed.
>> >
>> > I guess we will have to wait for IBM to react to our support case.
>> >
>> > Thank you for your reaction!
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
>> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>>
>>
>
>