Initialization of Dispatcher failed

Question

NW2007 CRM 5.0SR2
Oracle 10.2.0.2 /Sun Solaris 10
After applying SP13 to the Java stack, when logging into the portal  I get :
503 Service Unavailable
Servlet [prt] will be unavailable for undefined time
Details:   javax.servlet.UnavailableException: Initialization of Dispatcher failed.
The dispatcher is running, I can connect to the J2EE Engine Start page.
Oracle is running, and the listener is running.
I've restarted the j2ee instance many times, yet the problem persists.
Any Ideas.
And in the default.trc file:
com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap
erver#sap.com/irj#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GUEST#0##n/a##918e8330e52c11dcbc9d0003SAPEngine
ba4d72e4#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###application [irj] Processing HTTP request to servlet [with erro
gateway] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: unavaila
Servlet [prt] is currently unavailable.
        at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:174)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at com.sap.portal.navigation.Gateway.service(Gateway.java:126)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)                                 ionMessag
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSess
ionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed
        at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:371)
        at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)
        at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)
        at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
        ... 19 more

Answer 1

Here's what the dispatcher for the portal is saying:
Error occurred while reading message from R/3 dispatcher. The J2EE engine will be shut down
. Please check if the R/3 dispatcher is running and then restart the J2EE engine
Couldn't send INVALIDATE_ETAG to R/3 dispatcher. Exception is : java.net.SocketException: Socket closed
The dev_disp file in the work directory show's it's connected?
Mon Mar  3 06:26:48 2008
J2EE server info
  start = TRUE
  state = STARTED
  pid = 12194
  argv[0] = /usr/sap/CRD/DVEBMGS00/exe/jcontrol
  argv[1] = jcontrol
  argv[2] = pf=/usr/sap/CRD/SYS/profile/CRD_DVEBMGS00_crmdev
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64998
  argv[5] = -DSAPSYSTEM=00
  argv[6] = -DSAPSYSTEMNAME=CRD
  argv[7] = -DSAPMYNAME=crmdev_CRD_00
  argv[8] = -DSAPPROFILE=/usr/sap/CRD/SYS/profile/CRD_DVEBMGS00_crmdev
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Mon Mar  3 06:28:30 2008
J2EE server info
  start = TRUE
  state = ACTIVE
  pid = 12194
  http = 50000
  https = 50001
  load balance = 1
  start_lazy = 0
  start_control = SAP J2EE startup framework