cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry error. Already Logged in on another node in cluster with the same device.

Former Member
0 Kudos
261

Hi All

I have two versions of SAP Work Manager Application on our SMP server:

Production and Development

When I created and customized development verion of  SAP Work Manager Application

I can't connect to any of Applications

When I try to connect to Production version

https://192.168.0.107:8081/SAPWM

I get next error log:


Logging user into server

Already Logged In Elsewhere

He worked up to this.

When I try to connect to Development version

https://192.168.0.107:8081/SAPWM_ROUNDS

I get next error log:



Logging user into server

Communications error (14)

Connection failed

Ending transmission

I created Production version SAP Work Manager using "SAP Management Cockpit" and published it using

SAPWorkMgr621Deployment-20150514.2243.zip file

in "Publish Agentry App" edit box with "Browse..." button.

I also created SAPWM_ROUNDS application for development purpose.

I didn't publish zip file but copied contents of SAPWorkMgr621Deployment-20150514.2243.zip file into the folder

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM_ROUNDS\

Then I restarted SMP.

In the C:\SAP\MobilePlatform3\Server\log\agentry we have next files

Dev Def Load Loop Thread-4104.log

events.log

messages.log

startup.log

Dev Def Load Loop Thread-4104.log file


2016/04/06 14:15:16.727: Opening log file

2016/04/06 14:15:16.727: + Thread=4104

2016/04/06 14:15:16.727:   + Application=SAPWM_ROUNDS

2016/04/06 14:15:16.727:     + Load Loop=Development

2016/04/06 14:15:16.727:       Failed to create change notification for 'C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM_ROUNDS\Application\Development' definitions directory

2016/04/06 14:15:16.792: Closing log file

events.log


04/06/2016 14:15:12, 0,         0,         0, Thr       1300, New files opened events.log, messages.log

04/06/2016 14:15:12, 0,         0,         2, Thr       1300, Loading the Agentry Runtime's public/private key for password exchanges.

04/06/2016 14:15:12, 0,         0,         2, Thr       1300, Key pair loaded successfully.

04/06/2016 14:15:12, 0,         0,         2, Thr       1300, Agentry Startup

04/06/2016 14:15:12, 0,         1,         4, Thr       1300, Agentry Server Agent v130.7.0.4

04/06/2016 14:15:13, 0,        20,       150, Thr       5112, Loading Development application definitions

04/06/2016 14:15:16, 0,        23,         4, Thr       5112, Loaded Java-1 (Java v130.7.0.4) from ag3javabe.dll

04/06/2016 14:15:16, 0,        20,       152, Thr       5112, Loading Development application definitions for default localization

04/06/2016 14:15:16, 0,        20,       151, Thr       5112, Finished loading Development application definitions

04/06/2016 14:15:16, 0,        17,        14, Thr       1300, FlightBooking v130.7.0.4

04/06/2016 14:15:16, 0,        20,         4, Thr       1300, FlightBooking v130.7.0.4

04/06/2016 14:15:16, 0,        21,         4, Thr       1300, SAPWM62 v130.7.0.4

04/06/2016 14:15:16, 0,        22,         4, Thr       1300, SAPWM_NEW v130.7.0.4

04/06/2016 14:15:16, 1,         0,       250, Thr       4104, The path could not be found, ..\crossplatform\win32\FileSystemWatcher.cpp#95:Syclo::FileSystemWatcher::resetNotifications

04/06/2016 14:15:16, 0,        23,         4, Thr       1300, SAPWM_ROUNDS v130.7.0.4

04/06/2016 14:15:16, 0,        17,        10, Thr       1300, FlightBooking v130.7.0.4

04/06/2016 14:15:16, 0,         0,         0, Thr       1300, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-04-06-141502

04/06/2016 14:15:16, 0,         0,        23, Thr       1300, Agentry startup is complete.

04/06/2016 14:15:21, 0,        21,         5, Thr       1300, SAPWM62

04/06/2016 14:15:22, 0,        21,       150, Thr       3036, Loading Production application definitions using file "SAPWM-v1-0-0-app"

04/06/2016 14:15:22, 0,        21,       152, Thr       3036, Loading Production application definitions for default localization

04/06/2016 14:15:29, 0,        24,         4, Thr       3036, Loaded HTTP-XML Back End (HTTPXML v130.7.0.4) from ag3httpxmlbe.dll

04/06/2016 14:15:32, 0,        23,         4, Thr       3036, Loaded Java Back End (Java v130.7.0.4) from ag3javabe.dll

04/06/2016 14:15:33, 0,        21,       153, Thr       3036, Finished loading Production application definitions for default localization

04/06/2016 14:15:33, 0,        21,       151, Thr       3036, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

04/06/2016 14:15:33, 0,        17,        14, Thr       1300, SAPWM62 v130.7.0.4

04/06/2016 14:15:33, 0,        21,         4, Thr       1300, SAPWM62 v130.7.0.4

04/06/2016 14:15:33, 0,        17,        10, Thr       1300, SAPWM62 v130.7.0.4

04/06/2016 14:15:37, 0,        22,         5, Thr       1300, SAPWM_NEW

04/06/2016 14:15:37, 0,        22,       150, Thr       4232, Loading Production application definitions using file "SAPWM-v1-0-0-app"

04/06/2016 14:15:37, 0,        22,       152, Thr       4232, Loading Production application definitions for default localization

04/06/2016 14:15:44, 0,        24,         4, Thr       4232, Loaded HTTP-XML Back End (HTTPXML v130.7.0.4) from ag3httpxmlbe.dll

04/06/2016 14:15:47, 0,        23,         4, Thr       4232, Loaded Java Back End (Java v130.7.0.4) from ag3javabe.dll

04/06/2016 14:15:47, 0,        22,       153, Thr       4232, Finished loading Production application definitions for default localization

04/06/2016 14:15:48, 0,        22,       151, Thr       4232, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

04/06/2016 14:15:48, 0,        17,        14, Thr       1300, SAPWM_NEW v130.7.0.4

04/06/2016 14:15:48, 0,        22,         4, Thr       1300, SAPWM_NEW v130.7.0.4

04/06/2016 14:15:48, 0,        17,        10, Thr       1300, SAPWM_NEW v130.7.0.4

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:15:48, 1,         2,        48, Thr       4232, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

04/06/2016 14:20:42, 0,         0,         6, Thr       5108, dbolshakov: Already Logged in on another node in cluster with the same device.

04/06/2016 14:28:09, 0,         0,         6, Thr       5108, dbolshakov: Already Logged in on another node in cluster with the same device.

startup.log


14:15:02 04/06/2016: Starting Agentry (64-bit Windows)

14:15:12 04/06/2016: Reading system ini file.

14:15:12 04/06/2016: Starting log file.

14:15:12 04/06/2016: Loading message groups.

14:15:12 04/06/2016: Starting threads.

14:15:12 04/06/2016:    1 initial threads.  Threads will auto-scale.

14:15:12 04/06/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.

14:15:12 04/06/2016: Event: 0, 2, Key pair loaded successfully.

14:15:12 04/06/2016: Starting Agentry: Agentry Server Agent v130.7.0.4

14:15:12 04/06/2016: Event: 0, 2, Agentry Startup

14:15:12 04/06/2016: Loading 0 front ends

14:15:12 04/06/2016: Starting Agentry Server Agent

14:15:12 04/06/2016: Agentry Server Agent: Starting threads.

14:15:12 04/06/2016:    1 initial threads.  Threads will auto-scale.

14:15:12 04/06/2016: Agentry Server Agent: Adding messages.

14:15:12 04/06/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4

14:15:12 04/06/2016: Loading agent from ag3.dll

14:15:12 04/06/2016: Starting FlightBooking

14:15:12 04/06/2016: FlightBooking: reading config file

14:15:13 04/06/2016: Event: 20, 150, Loading Development application definitions

14:15:14 04/06/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll

14:15:14 04/06/2016: BackendSAPConnection: Reading configuration information.

14:15:14 04/06/2016: BackendSAPConnection: Setting name to 'Java-1'.

14:15:14 04/06/2016: Java-1: Initialized.

14:15:14 04/06/2016: Java-1: Java Virtual Machine already initialized.

14:15:16 04/06/2016: Java-1: Initialized.

14:15:16 04/06/2016: Event: 23, 4, Loaded Java-1 (Java v130.7.0.4) from ag3javabe.dll

14:15:16 04/06/2016: Event: 20, 152, Loading Development application definitions for default localization

14:15:16 04/06/2016: Event: 20, 151, Finished loading Development application definitions

14:15:16 04/06/2016: FlightBooking: Starting threads.

14:15:16 04/06/2016:    1 initial threads.  Threads will auto-scale.

14:15:16 04/06/2016: Loading front end from angelvine

14:15:16 04/06/2016: FlightBooking: loading configuration

14:15:16 04/06/2016: Event: 17, 14, FlightBooking v130.7.0.4

14:15:16 04/06/2016: Event: 20, 4, FlightBooking v130.7.0.4

14:15:16 04/06/2016: Loading agent from ag3.dll

14:15:16 04/06/2016: Starting SAPWM62

14:15:16 04/06/2016: Event: 21, 4, SAPWM62 v130.7.0.4

14:15:16 04/06/2016: Loading agent from ag3.dll

14:15:16 04/06/2016: Starting SAPWM_NEW

14:15:16 04/06/2016: Event: 22, 4, SAPWM_NEW v130.7.0.4

14:15:16 04/06/2016: Loading agent from ag3.dll

14:15:16 04/06/2016: Starting SAPWM_ROUNDS

14:15:16 04/06/2016: SAPWM_ROUNDS: reading config file

14:15:16 04/06/2016: Exception: 14:15:16 04/06/2016 : 0 (General), File system exception (The path could not be found, ), ..\crossplatform\win32\FileSystemWatcher.cpp#95:Syclo::FileSystemWatcher::resetNotifications

14:15:16 04/06/2016: SAPWM_ROUNDS: Starting threads.

14:15:16 04/06/2016:    1 initial threads.  Threads will auto-scale.

14:15:16 04/06/2016: Event: 23, 4, SAPWM_ROUNDS v130.7.0.4

14:15:16 04/06/2016: Starting front ends

14:15:16 04/06/2016: Starting front end FlightBooking

14:15:16 04/06/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking

14:15:16 04/06/2016: Event: 17, 10, FlightBooking v130.7.0.4

14:15:16 04/06/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-04-06-141502

14:15:16 04/06/2016: Event: 0, 23, Agentry startup is complete.

Accepted Solutions (1)

Accepted Solutions (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

When creating your development instance and copying the files from the zip to the folder did you remember to edit the Agentry.ini to change DevelopmentSever to True?

Did you also change the urlPath to be unique for your development version?

--Bill

Former Member
0 Kudos

In the file

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM_ROUNDS\Agentry.ini

The value of developmentServer=True

I didn't set it to True. But it is True. Don't know when it became True.

We have 4 Agentry Applications on SMP server.

All Values of urlPath are unique.

Former Member
0 Kudos

For the Rounds app after you copied the information from the zip to the folder, did you publish a development version to the application folder?

The zip files contain a production version of the application, not the development.  This comes from the Editor and not the zip file.

Former Member
0 Kudos

Do I need to publish application from

SAPWorkMgr621Deployment-20150514.2243.zip file

in "Publish Agentry App" edit box with "Browse..." button

from SAP Management Cockpit.

Or I need to publish it from Eclipse via "Publish this Egentry Application to an Agentry Server"

?

Former Member
0 Kudos

If you want a development version, you need to publish from the editor, and select Development.  This will not create a zip file that upload, but will put the application right into the application folder

Former Member
0 Kudos

After publishing Project from Eclipse and restarting SMP

SAPWM_ROUNDS started to work.

SAPWM still don't work

with error - Already Logged In Elsewhere


Perhaps the problem in the SAPWM is not related to the problem in SAPWM_ROUNDS.


bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Already logged in elsewhere indicates your server thinks you are connected already from another device.

In the cockpit under users select Agentry and see what if any users are listed.  If you see your username for the SAPWM app you can disconnect the user and then try logging in again.

--Bill

Answers (0)