it after
we stumbled on the tracing option.
Regards
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett
Sent: Wednesday, August 08, 2007 12:05 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] U2 AMI Interface
Hi David,
thanks
Hi Herve,
thanks for the information. I think I'll write some C code and see if
the problem happens there as well.
regards,
Craig
Herve Balestrieri wrote:
Craig,
The behaviour you describe is related to WebSphere MQ, not the U2AMI
interface.
This interface is purely programmatic with the
Hi Craig
We use U2AMI. It was a steep learning curve, but it all works well
now...
I don't think I've ever seen a timeout error/issue when using
amSendRequest. We do see it with amReceiveMsg though. However, this is
not an issue for our application, when just try again...more
specifically we
Craig,
I didn't realise there were debug logs available, any suggestions on
where I should look?
Not sure what you need to check in the trace logs. I assume you
application is working okay or are debugging are existing issue?
Before we execute the BASIC application with the U2AMI calls, we
