cancel
Showing results for 
Search instead for 
Did you mean: 

Port issues - SMP and Agentry

Murali_Shanmu
Active Contributor
0 Kudos

Hi,

I have installed SMP 2.3 and also a Dev Agentry server 6.1. I am not able to get both to work together at the same time. When I start the SMP 2.3 server and then try to start the Agentry Dev Server, I get (Socket Error), EADDRINUSE. I am not sure why this happens as the Port for Agentry Dev Server is 7089 and for the one inside SMP is 7003.

Below are the details of the Agentry.ini file for the below locations.

Agentry Server inside SMP (C:\SAP\MobilePlatform\Servers\AgentryServer)

[ANGEL Front End Ports]

1=7003

[TCP Front End]

listenOn=7001

[Web Server Front End]

listenOn=80

Agentry Application inside SMP (C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\com.sap.workmanager60)

[ANGEL Front End Ports]

1=7003

[TCP Front End]

listenOn=7001

[Web Server Front End]

listenOn=80

Agentry Dev Server Standalone (C:\Agentry\WM60DevServer)

[ANGEL Front End Ports]

1=7089

[TCP Front End]

listenOn=7001

[Web Server Front End]

listenOn=80

Thanks,

Murali

Tags edited by: Michael Appleby

Accepted Solutions (1)

Accepted Solutions (1)

jason_latko
Active Contributor
0 Kudos

Murali,

Look at the TCP settings in the config entries you posted, they both use port 7001.  Look through your Agentry.ini and JavaBE.ini files for any other port entries that may be conflicting, and modify them to use different ports in all cases.

Jason Latko - Senior Product Developer at SAP

Murali_Shanmu
Active Contributor
0 Kudos

Thanks Jason.

I changed the TCP setting to 7004 in SMP and turned it on. Next, I tried to start the Agentry Dev Server and it still gave the same error

Event: 17, 10, 0.0.0.0:7089 open

Event: 17, 10, ANGEL Front End v6.1.0.3

Exception: 09:32:02 02/19/2014 : 2 (Socket Error), EADDRINUSE (EADDRINUSE, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn

I could not find a port number in any of the javaBE.ini file

Thanks,

Murali

nancy_burke
Explorer
0 Kudos

Hi Murali,

Check your nonstandard options entry in Agentry.ini.  Do you have a port defined there that you may also have defined in Angel or TCP/IP?  You must have unique ports defined for these entries.  There are several knowledgebase articles on Eaddrinuse:  here is one 1813018.

Run: netstat -a to find what is using your port.  Then locate that application to determine what's running.

Nancy Burke

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Murali,

I suspect that you also need to check the [HTTPXML-2] section of the Agentry.ini and look for the listenOn port number (8282 by default I believe).  This is the port that the Agentry server will use to listen for server events.  It also has to be unique.

The [TCP Front End] listenOn setting of 7001 can be ignored and left at 7001 as that connection type is not active by default.

It looks like you already have the [ANGEL Front End Ports] numbers set to unique values which is the other port that may be a conflict.

--Bill

Murali_Shanmu
Active Contributor
0 Kudos

Thanks guys. I have been using netstat but didn't really understand where to look for the right information.

When I issued Netstat -a -n -o

Prot  Local Address      Foreign Address    State       PID
  TCP  0.0.0.0:7003       0.0.0.0:0          LISTENING   10016
  TCP 0.0.0.0:8000       0.0.0.0:0          LISTENING   10512
  TCP 0.0.0.0:8001       0.0.0.0:0          LISTENING   10512
  TCP 0.0.0.0:8282       0.0.0.0:0          LISTENING   7004
  TCP 0.0.0.0:8282       0.0.0.0:0          LISTENING   10016
  TCP 0.0.0.0:8283       0.0.0.0:0          LISTENING   7004

It tells me the ports which are currently being used. It took me a while to spot the above ones from the huge list.

To find the services which are tied to the corresponding process, I issued

Tasklist /svc /FI "PID eq 7004"

It revealed that port 8282 and 8283 were being used by SCC and Agentry(inside SMP).

Hence, I changed the [HTTPXML-2] port to 8285 in Agentry Dev server and started it. I actually changed this to 8283 yesterday and it didn't work. Now I know the reason.

Thanks,

Murali.

nancy_burke
Explorer
0 Kudos


Nice work!!!  You are now the netstat expert

Former Member
0 Kudos

On a side note what you can do next time is go "netstat -a -n -o > ports.txt"
This will create a file called "Ports.txt" at the location the command line window is at when the line is called.  Then you just open the file and do a search.

or even "netstat -a | find "7003"

This will show all the lines that have 7003 on it.

Answers (1)

Answers (1)

0 Kudos

Thanks All, had the same issue now its resolved.