J2EE Engine Problem Analysis Scenarios 

The following problem analysis scenarios are available for the J2EE Engine:

●      Error Messages While Connecting to the Standalone Log Viewer Server

●      Visual Administrator: Logon Failure

●      Config Tool Hangs after Upgrade

●      Ping Timeout – Connection to Server Is Lost

●      J2EE Engine of Instance <xxx> Did Not Come Up After 800 Seconds

●      Monitoring Information Not Available in CCMS (RZ20)

●      No CEN Information Available in SLD

●      Disabling Monitors Using the SAP NetWeaver Administrator

●      „Application Stopped“ While Requesting an Application

●      Application Already In Use

●      No Container Available For J2EE Module

●      Warnings During Application Deployment

●      SDM Deployment Fails

●      SDM Undeployment Fails

●      Offline Deploy Hangs

●      Deploy Tool Connection Problems

●      ClassCastException Occurs After Lookup Operation

●      Wrong Lookup From Another Cluster

●      Return of an Unexpected Class Type After a Lookup Operation

●      Getting Initial Context Using IIOP Fails

●      Getting New Initial Context Using P4 Fails

●      Startup of an Application with CMP Entity Beans Fails

●      Unable to Get a Connection From a Data Source

●      Response Code 415 When Requesting a Web Service

●      Obtaining a Single Document WSDL

●      Missing Stack Trace in the Response SOAP Fault Message

●      Web Service Client Applications Throw XMLMarshallException

●      Lost Authentication Data in a Web Service Endpoint Implementation

●      JMS Client Cannot Create Connection

●      Messages are not Received by the JMS Consumers

For more information about the J2EE Engine, see Java Technology in SAP Web Application Server.