In the JAX-WS engine on the Web Service, when the J2EE server starts the J2EE application, the Web Service is initialized. Specifically, the following processing is executed:

• Generation of mapping the information between the URL and the Web Service Implementation Class or the Provider Implementation Class for performing Web Service discovery
• If a WAR file does not contain request beans, response beans, or the JavaBeans classes of fault beans required to start POJO Web Services or if an EAR file does not contain request beans, response beans, or the EAR file does not contain the JavaBeans classes of fault beans required to start an EJB Web Service, the JAX-WS engine dynamically generates the JavaBeans classes.
• Checking of WSDL for issuing the Meta data (for a Web Service Implementation Class)
• Reading of the handler chain setup file and initialization of the handler when the handler is associated with the Web Service Implementation Class or the Provider Implementation Class
  (Also, includes the invocation of the method annotated using the javax.annotation.PostConstruct annotation if such a method exists)
  

When the initialization of the Web Service starts, the KDJW40001-I message is output in the log and standard output. If Web Service initialization ends normally, the KDJW40003-I message is output in the log and standard output. If an error occurs during Web Service initialization and if the initialization fails, the KDJW40002-E message and the error message that caused the error is output in the log and standard error output.

If an error occurs during Web Service initialization, an error is output in the log, but the startup of the J2EE application continues and ends normally. However, since the initialization failed, the deployed Web Service does not work. In this case, check if the KDJW40002-E message is output. If an error is output, correct the problem and deploy the Web Service again.

When starting a J2EE server, it might be difficult to investigate in a J2EE application why Web Service could not be initialized, when the deployed J2EE application is started automatically. In such cases, you can identify the J2EE application name and the context root name by checking logs shown in the section 39.3.1 Types of log, and operation logs of the J2EE server.

The following is an example of checking the output contents of the message KDJE39103-E including com.cosminexus.xml.ws.transport.http.servlet.WSServletContextListener:

0095 2009/12/18 13:48:36.471     HEJB             0125FEFA 004413EE KDJE39103-E           An exception javax.xml.ws.WebServiceException was raised in notification of the listener class com.cosminexus.xml.ws.transport.http.servlet.WSServletContextListener. (J2EE application = Sample_application_fromwsdl, context root = /fromjava)

When a log such as the one shown above is output, an attempt to initialize the Web Service within the WAR file that is associated with the context root name fromjava and included in the J2EE application Sample_application_fromwsdl will fail.

If there is a problem with the user program, basically an error corresponding to the message KDJE39103-E occurs. However, check the following error messages also, as and when required:

• KDJE39100-E
• KDJE39101-E
• KDJE39102-E

For the operation logs of the J2EE server, see 5.2 Log contents of Application Server in the uCosminexus Application Server Maintenance and Migration Guide. Also for the above messages, see 7.2. Messages from KDJE30000 to KDJE39999 in the manual uCosminexus Application Server Messages.

In the JAX-WS engine on the Web Service, when the J2EE server ends the J2EE application, the Web Service is destroyed. Specifically, the following processing is executed:

• Deletion of mapping information between the URL and the Web Service Implementation Class or the Provider Implementation Class for performing Web Service discovery
• Destruction of the handler when the handler is associated with the Web Service Implementation Class or the Provider Implementation Class
  (Also includes the invocation of the method annotated using the javax.annotation.PreDestory annotation if such a method exists)
  

When the destruction of the Web Service starts, the KDJW40004-I message is output in the log and standard output. If Web Service destruction ends successfully, the KDJW40006-I message is output in the log and standard output. If an error occurs during Web Service destruction and if the destruction fails, the KDJW40015-E message and the error message that caused the error is output in the log and standard error output.

If an error occurs during Web Service destruction, an error is output in the log, but the end processing of the J2EE application continues and ends normally. In this case, check if the KDJW40015-E message is output and if an error is output, correct the problem.