cancel
Showing results for 
Search instead for 
Did you mean: 

P4 connection refused

Former Member
0 Kudos

Hi guys,

Ive a problem when configuring Solution Manager Diagnostics in order to get EWA for my NW2004s pure Java Development system.

The issue is, after installing succesfully SMD and Introscope Agent, when running Setup Wizard for managed systems in Diagnostics.

Logs says:

An error occured while communicating with Message Server 10.193.4.54:50000 through the host ovdev : Error to retrieve the process from Message Server (detail: java.io.IOException: AttachToMessageServe

r(): No answer from message server within 60 sec.); nested exception is:

java.io.IOException: AttachToMessageServer(): No answer from message server within 60 sec.(cause=java.io.IOException AttachToMessageServer(): No answer from message server within 60 sec.)

Please check Message Server host/port, or enter the P4 ports in cluster table.

Detailed log i found says:

Step SSO Details

Failed to connect, P4 port=50004 User=Administrator SID=VD1 Instance Number=null

Error to established the p4 connection for sid [VD1]; nested exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)](cause=com.sap.engine.services.jndi.persistent.exceptions.NamingException Exception while trying to get InitialContext.)

Open/Close Exception stack trace Exceptions

com.sap.smdagent.plugins.connectors.p4.exceptions.P4ConnectionException: Error to established the p4 connection for sid [VD1]; nested exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)]

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:71)

at com.sap.smd.agent.plugins.remotesetup.SetupManager.newP4ctx(SetupManager.java:119)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:123)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:85)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)

at java.lang.Thread.run(Thread.java:534)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)]

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.<init>(InitialContext.java:195)

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:50)

... 8 more

Caused by: java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)

at com.sap.engine.transport.ClientPortsManager.getRealSocket(ClientPortsManager.java:150)

at com.sap.engine.services.rmi_p4.LoadBalancerImpl.getAllAccessPoints(LoadBalancerImpl.java:76)

at com.sap.engine.interfaces.cross.CrossObjectBroker.getDestination(CrossObjectBroker.java:92)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:339)

... 13 more

I have tested P4 connection via Visual admin, as suggested in other post and it works fine. Last night we have restarted both servers (VD1,development server, and VS1, solution manager server). I still dont know if i can get more detailed info.

Any ideas?

Regards!!

Victor

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

HI,

open the ports from solman to Java system on OS side. That will do .

Former Member
0 Kudos

Could you please let us know in clear ,what you mean by opening the ports from Solman to Java system.

Do you mean the ports in /etc/services file.

Thank you.

Former Member
0 Kudos

Thanks for the quick response.

I ve run command "netstat | grep 50004"

in my DEV server and the output is

"tcp 0 0 ovdev.65528 ovtst.50004 ESTABLISHED

tcp 0 0 ovdev.59538 ovdev.50004 ESTABLISHED

tcp 0 0 ovdev.50004 ovdev.59538 ESTABLISHED

tcp 0 0 ovdev.50004 ovtst.64766 TIME_WAIT

"

being ovdev my dev server and ovtst my solman server

So i think service is working fine...

Edited by: Basis Basis on Aug 12, 2008 4:33 PM

Former Member
0 Kudos

Had same issue..try restarting the SMD agent on satellite system and then execute setup.

Also you can check whether the correct P4 port is used, which can be checked in Instance details for satellite system on SLD.

Hope that helps.