| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 4 matches |
| Author |
Message |
 Topic: Client works on Java, but fail .net with 2035 or 2059 |
Edilba
Replies: 5
Views: 4784
|
 Forum: General Discussion Posted: Mon Jan 18, 2010 2:10 pm Subject: Client works on Java, but fail .net with 2035 or 2059 |
Problem solved using a customized SecurityExit on client side and using TRANSPORT_MQSERIES_CLIENT as connection type.
Thank you all. |
| Topic: Client works on Java, but fail .net with 2035 or 2059 |
Edilba
Replies: 5
Views: 4784
|
Forum: General Discussion Posted: Mon Jan 18, 2010 3:38 am Subject: Client works on Java, but fail .net with 2035 or 2059 |
Thanks for your help, zpat.
I'm gonna try right now.
Regards. |
| Topic: Client works on Java, but fail .net with 2035 or 2059 |
Edilba
Replies: 5
Views: 4784
|
Forum: General Discussion Posted: Sun Jan 17, 2010 3:20 am Subject: Client works on Java, but fail .net with 2035 or 2059 |
Thanks for your help.
I'll keep looking here for more information.
Regards. |
| Topic: Client works on Java, but fail .net with 2035 or 2059 |
Edilba
Replies: 5
Views: 4784
|
Forum: General Discussion Posted: Sat Jan 16, 2010 9:49 am Subject: Client works on Java, but fail .net with 2035 or 2059 |
Hi,
I'm having this problem: a MQClient program in Java works, but same program written is .Net (dotnet) doesn't.
Client (v7.0.1) is running on Windows. Server is running on AS400.
When .Net ... |
|
|
|
