on 05-24-2008 9:42 AM
Hi,
We have given the right credentials and out of 10 messages only 3 went thru. Remaining failed with these errors.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_r_PODownloadon node: 24541950 having object id: e42d9a8005783260b8d8db26cd2f5564 encountered error: Access denied to resource: type=<jms>, application=, destinationType=queue, resource=PoImport, action=send in sending to destination PoImport, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>, application=, destinationType=queue, resource=PoImport, action=send
As i checked out, the successful messages were executed with one cluster node whereas the failure messages were in another cluster node .
Is it the problem on configuration of JMS receiver or Basis Cluster Node.
Regards,
Anandh
HI Anandh,
If you are running the Adapter Engine on a server cluster, the communication channels comprise multiple instances for the various cluster nodes.
When you choose EOIO, the processing can be done by one J2EE server node only. So put the cluster ID of the required server note here.
The documentation for JMS sender adapter lists the following:
"Specify the Processing J2EE Cluster Server (Cluster ID).
This specification stops queue-jumping in the JMS
queue. The valid cluster ID is located on the J2EE
server Administrator under Server."
OR
To control communication channels externally, you use an HTTP GET or POST request to the following URL:
http(s)://host:port/AdapterFramework/ChannelAdminServlet?party=party&service=service&channel=channel&action=action
(You can use an asterisk (*) as a placeholder to administer several channels simultaneously.)
Refer
http://help.sap.com/search/highlightContent.jsp
Cross Cluster Notification
Thanks
Swarup
Edited by: Swarup Sawant on May 24, 2008 10:57 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
Yes you are right as on Receiver JMS side we can't Specify the Processing J2EE Cluster Server (Cluster ID). Thus there will be the queue-jumping in the JMS queue and the EOIO channel is activated automatically on a different working node. This configuration ensures node failover by the adapter in a clustered environment.
A JMS provider must provide functions for serializing JMS-administrable objects as Java objects in a file. Connection and access parameters are set. The files must be copied to each cluster server.
So you need to replicate these serializing JMS-administrable objects to all cluster server available in J2EE server u2013 Administrator under Server.
Thanks
Swarup
User | Count |
---|---|
83 | |
9 | |
9 | |
7 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.