JMS Receiver

[Former Member]

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

[Former Member · Accepted solution]

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

[Former Member · Accepted solution]

Hi swarup,

Because as i am using receiver JMS communication channel, i dont have the control to set the cluster id.

[Former Member · Accepted solution]

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

[vijay_b4]

Hi Anandha,

could you check the jms adapter service is running on the VA?

or you can have the complete cache refresh in sxi_cache

and

There may be problem with your Queue channel that was defined for connection pipline with the receiver.

Verify the Queue channel.

Reward points if this helps

Regards

Pragathi.

[vijay_b4]

Hi Anandha,

Check this link:

JMS Client Cannot Create Connection

http://help.sap.com/saphelp_nw04/helpdata/en/f5/2f2c4142aef623e10000000a155106/frameset.htm

Possible Error Causes

● User password for the JMS provider is not valid

● User X does not exist

● User X is locked

And perform initial task - setting Permissions for Portal Content.

For details,

http://help.sap.com/saphelp_nw70/helpdata/en/ab/a954036e164c7eaeca840144f267dd/content.htm

Reward points if this helps

Regards

Pragathi.