Dispatcher process on ABAP + JAVA system does not start.

[Former Member]

Hi all,

Dispatcher process on ABAP + JAVA system does not start.

Can someone help me to solve this issue in a ABAP+JAVA stack system?

service p4 ================= ERROR =================

Core service p4 failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres

s (errno:227)

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java

.util.PropertyResourceBundle, key Can't assign requested address (errno:227)

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.

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

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

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:78)

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

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres

s (errno:227)

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java

.util.PropertyResourceBundle, key Can't assign requested address (errno:227)

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.

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

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

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:78)

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

[Framework -> criticalShutdown] Core service p4 failed. J2EE Engine cannot be started.

Nov 9, 2011 6:41:09 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:6]_26] Fatal: Critical shutdown was invoked. Reason is: Core

service p4 failed. J2EE Engine cannot be started.

Please let me know if you need any further information in this regard.

with regards,

Raja

[blanca_serrano · Accepted solution]

Hello Raja,

Please review note 609603 and set the bindHost property accordingly.

Regards,

Blanca

[Former Member · Accepted solution]

Hi all,

Thanks to your replies.

The issue has been resolved by setting the correct value for the 'bindHost' variable in Configtool, as per the note : 609603

The instance has been restarted following the variable change.

Thanks a lot.

with regards,

Raja

[former_member188883]

Hi,

Core service p4 failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres

Please reboot the server to free up occupied ports. Later start the sap system.

Regards,

Deepak kori

[anja_engelhardt2]

Hi,

check whether the P4 port is already in use by some different application. Maybe there is an old dispatcher process running...

Anja