cancel
Showing results for 
Search instead for 
Did you mean: 

WAS Java not coming up after maintaining the wrong hostname in p4 via visua

0 Kudos

Dear Experts,

We have 701 Solman installed and utilizing it for CTS. After the hardware fail over the CTS functionality stopped woking, then we refered the Note 1389833 - Deployment to a 7.10 or higher J2EE engine does not work and made the changes accordingly,

while making changes the ip was mistyped and now the java server is not coming up.

Due the problem in java visula admin also is not up and we unable to revert the entry.

Please find the error message in java dispatcher

#1.#00145E776DCA0010000000030039609A0004B2CA5AAA2124#1322482081079#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_13##0#0#Error#1#/System/Server#Java###Core service p4 failed. J2EE Engine cannot be started.

[EXCEPTION]

#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket on 145.17.50.189 and port 50004. Exception: The socket name is not available on this system.', Arguments: []> : Can't furceBundle, key com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket on 145.17.50.189 and port 50004. Exception: The socket name is not available on this system.

at com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor.<init>(TransportMonitor.java:219)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:98)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)

Kindly help in how to revert the value 0.0.0.0 for p4 if visual admin is not available.

Regards

Balamurugan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please check the entries in the table J2EE_CONFIGENTRY for field VSTR.

If you find the wrong IP there, take a backup of this table (copy the entries to a dumy table) and then update the entry with the correct ip.

Regards,

Amit.

Answers (6)

Answers (6)

0 Kudos

Dear Amit,

thank you for the valuable solution, it worked.

The Java came up after updating the correct ip address.

Regards

Bala

0 Kudos

Hello experts,

Please tell me the table in database which has the value of p4.

Only if i change the value at DB level i will be able to start up the Java instance.

I checked for the possibilities from configtoool/profile parameter nothing seems to work.

Regards

Balamurugan

0 Kudos

hi,

Yes i have taken instance restart for java and also complete restart.

Regards

Balamurugan

Former Member
0 Kudos

Hello Bala,

Please check the hostname of p4 in the instance profile parameter icm/server_port_X.

Please take a look at note 609603, if you haven't gone through it yet.

Thanks,

Siva Kumar

Edited by: Siva Kumar Arivinti on Nov 30, 2011 11:29 PM

0 Kudos

Dear Experts.

I have tried those option via configtool but still the dispatcher is down with the same message.

any other option, plz

Regards

Balamurugan

Former Member
0 Kudos

Hi Bala,

Did you save the changes and restart the system?

Thanks,

Siva Kumar

Edited by: Siva Kumar Arivinti on Nov 30, 2011 9:06 PM

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Start your DB and then start config tool there change the P4 hostname/IP which you entered wrong. After changes saved, try to restart the system.

Thanks

Sunny

Former Member
0 Kudos

Hello Bala,

Since you have maintained wrong P4 hostname, Visual admin won't come up now as it uses P4 properties.

Please check if you can revert the changes from configuration tool.

Thanks,

Siva Kumar