SMP3.0 cluster issues

[former_member234206]

Hi Experts,

We are using SMP3.0, SP Level 03, Workmanager6.1

We have two production servers at SAP say P01, P02. When users transmit/Connect to the server it always logs users into P02 server.

but none of the users logs into P01 server.

I checked the java back end file. there it is updated with P02 server in both the nodes.

So, I thought this might be the issue and re published the app in Node1 with P01 and restarted the server.

Now when i check in Node1 app server - it is updated with java be P01 (I thought well this is fine) and at the below location latest app is available

Server\configuration\com.sap.mobile.platform.server.agentry.application

And when i check in Node2 app server - it is also updated with java be P01.

Server\configuration\com.sap.mobile.platform.server.agentry.application

The question here is, though i have only published the app in Node1, how it accessed Node2 and updated with the latest application.

Please help me here, all the users are accessing one server which is causing memory issues.

let me know if anyfurther information is required on this regard.

Also i checked the below SAP Note and actioned as mentioned, still it is accessing the other node (node2) simultaneously when i do in node1.

2188862 - Problem of publishing Work Manager on SMP3.0 cluster environment.

Thanks in advance.

[bill_froelich]

Thulasiram,

It sounds like your JavaBE [LOGON_METHOD] is set to USER_AUTH.  In this configuration you specify the specific server to connect to.  If you have more than one SAP instance and want to balance the connections between the instances you should switch the LOGON_METHOD to be USER_AUTH_GROUP and configure the [GROUP_LOGIN] section.  This will use the SAP Message Server to balance the requests among your instances.

--Bill

[Former Member]

When you publish an Agentry application in a cluster system, the version is pushed to all the other servers in the cluster.

If you are having an issue with all your users going to one server and not splitting between the two, you need to look at the proxy the clients are connecting to see if it pushes to one until it is down, then goes to the backup, my suggestion it should do a round robin.

Note, the proxy should also contain sticky connection, this why the client will keep connecting to the same server, so it can get pushes from the server.