cancel
Showing results for 
Search instead for 
Did you mean: 

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Former Member
0 Kudos

Hello Experts.

I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.

It has been installed successfully and does start up, however I get some annoying error messages during start up.

It seems that the server is running - I can succesfully synchronize to an ATE client.

Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.

Errors from the startup.log:

13:26:00 05/05/2014: HTTP-XML Back End Back End: Started

13:26:00 05/05/2014: Server: Starting threads.

13:26:00 05/05/2014:    1 initial threads.  Threads will auto-scale.

13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3

13:26:00 05/05/2014: Starting front ends

13:26:00 05/05/2014: ANGEL Front End: Starting threads.

13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

13:26:00 05/05/2014:    3 initial threads.  Threads will auto-scale.

13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523

13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open

13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3

13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546

13:26:00 05/05/2014: Event: 0, 23, 4

13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.

13:26:01 05/05/2014: Agentry Application startup complete

Can anybody help with the meaning and implications of these errors ?

Thank you.

Søren Hansen.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

1) Use the SP04 Server, it is in the SMP 2.3 SDK

2)  (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

- This shows the port is already in use.  Are there any other Agentry Server (AgentrySever.exe) running on the server?

Former Member
0 Kudos

Damn... I missed one port

You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.

Thanks Steve.

For others:

Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.

Now the server starts without errors.

[ANGEL Front End Ports]
1=7523

[TCP Front End]
listenOn=7521

[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n

[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525

Søren Hansen.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Just to note.  The [TCP Front End] port is no longer used by default and there for legacy purposes.  It can be ignored in 99% of the cases.

--Bill

Former Member
0 Kudos

To go on Bills point, the TCP Section is only looked at when the [Front Ends] of the Agentry.ini has "n=tcpvine.dll"

Answers (0)