| Author |
Message
|
| bhaski |
 Posted: Fri Jan 06, 2017 8:51 am Post subject: MQ 7.5.04 AMS help for JMS Remote Client |
 |
|
Voyager
Joined: 13 Sep 2006
Posts: 78
Location: USA
|
Hi Friends
I am getting this given error while sending msg to MQ AMS Queues from Remote system.. It is working good with amqsputc and amqsget ( @ server ).. Need your help based on this given error
( Testing it with JmsProducer samples )
JmsProducer output:
com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2007: Failed to send
a message to destination 'AMS.TEST.IN'.
JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an er
ror.
Use the linked exception to determine the cause of this error.
Inner exception(s):
com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' (
'MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
FAILURE
Error Log Msg:
AMQ9034: Message on queue AMS.TEST.IN does not have a valid protection type.
EXPLANATION:
The WebSphere MQ security policy interceptor detected invalid internal
protection data in a message header. This usually occurs because the WebSphere
MQ message header information within the message is not valid. The queue name
is 'AMS.TEST.IN'. The application details (if available) are
'JMS.AMS.SVRCONN:10.xxx.xx.xxx'.
ACTION:
Check that the application putting messages to queue 'AMS.TEST.IN' is correctly
configured to use Advanced Message Security. If the application is a client,
ensure it has the Advanced Message Security libraries correctly installed. If
it is a Java application, ensure it has the Advanced Message Security JAR
file(s) installed, and the CLASSPATH is correctly set so it includes these JAR
file(s).
Thanks
Bhaski
[/b] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Jan 06, 2017 10:02 am Post subject: Re: MQ 7.5.04 AMS help for JMS Remote Client |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bhaski wrote: |
ACTION:
Check that the application putting messages to queue 'AMS.TEST.IN' is correctly
configured to use Advanced Message Security. If the application is a client,
ensure it has the Advanced Message Security libraries correctly installed. If
it is a Java application, ensure it has the Advanced Message Security JAR
file(s) installed, and the CLASSPATH is correctly set so it includes these JAR
file(s). |
Is the application correctly configured?
Are the JAR files installed as indicated?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bhaski |
| Posted: Fri Jan 06, 2017 10:09 am Post subject: |
|
|
Voyager
Joined: 13 Sep 2006
Posts: 78
Location: USA
|
Thank you..
I hope so.. Cos if I don't use AMS, it is working fine.. not sure what are the jar files ( AMS related ) are required for these.
_________________
Thanks and Regards
Bhaski
Websphere MQ Admin Certified
Websphere WMB Admin certified |
|
| Back to top |
|
|
| bhaski |
| Posted: Fri Jan 06, 2017 10:16 am Post subject: |
|
|
Voyager
Joined: 13 Sep 2006
Posts: 78
Location: USA
|
both server and client are same MQ versions
_________________
Thanks and Regards
Bhaski
Websphere MQ Admin Certified
Websphere WMB Admin certified |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 06, 2017 10:30 am Post subject: Re: MQ 7.5.04 AMS help for JMS Remote Client |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bhaski wrote: |
Check that the application putting messages to queue 'AMS.TEST.IN' is correctly configured to use Advanced Message Security.
If the application is a client, ensure it has the Advanced Message Security libraries correctly installed.
If it is a Java application, ensure it has the Advanced Message Security JAR
file(s) installed, and the CLASSPATH is correctly set so it includes these JAR
file(s). |
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 06, 2017 11:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bhaski wrote: |
| I hope so.. Cos if I don't use AMS, it is working fine.. not sure what are the jar files ( AMS related ) are required for these. |
So you've got a working JMS application. Yay.
You then try and use it with an AMS set up without changing the application configuration nor adding the JAR files that support AMS to your application. Explain to me again, slowly, why you're surprised you get a 2063.
If an application could use an AMS protected queue without any AMS configuration and without any AMS support at the transport level, that's not a lot of protection is it?
Don't respond "if that's the case, why does amqsputc and amqsget work?" - it's Friday afternoon and you could get some unfortunate responses.
(clue- what language are those samples written in?)
(hint - it's not Java)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bhaski |
| Posted: Mon Jan 09, 2017 9:40 am Post subject: |
|
|
Voyager
Joined: 13 Sep 2006
Posts: 78
Location: USA
|
Solution is done.
Thank you for your support.. it is working by passing the certificate to Java directly instead of setting as environment variable. java -D<keystore.conf>, it is working now.. |
|
| Back to top |
|
|
|
|
