8.10.3 Errors Caused by Failure to Start PL/extJava

If an error occurs during instance startup because PL/extJava has failed to start, check the error messages output to the logs below and investigate the cause of the error by referring to "Messages Output by PL/extJava" in Messages. Refer to "Appendix G PL/extJava Log Information" for information on the location of these logs.

Event log

Symfoware Server server log
Container server log
Container Java VM log
Domain server log
Domain Java VM log

Some common causes of this error (and their corresponding corrective actions) are listed below:

A fault may have occurred on the disk where the domain root is placed, or the disk may have becomes corrupted by an incorrect operation.
If that is the case, perform the following procedure to restore it
If a backup of PL/extJava has been obtained
Refer to "7.3.7.2 Restore Method" and restore PL/extJava accordingly.
If a backup of PL/extJava has not been obtained
Perform the following procedure.
1. Stop applications
  Stop applications that are using the database.
2. Stop the instance
  Stop the instance, refer to 2.1 Starting and Stopping an Instance" for details.
  If the instance fails to stop, refer to "8.11 Actions in Response to Failure to Stop an Instance".
3. Recover the failed disk
  If the disk is defective, replace the disk, and then recover the volume configuration information.
4. Delete the domain root directory
5. Change the settings in the postgresql.conf file
  Delete the following parameters from the postgresql.conf file.
  - plextjava.http_port
  - plextjava.start_command
  - plextjava.stop_command
  - plextjava.forcible_stop_command
6. Delete the domain root information
  If "FUJITSU PCMI(isje6-componentId)" remains in services, execute the sc command as shown below to delete the "FUJITSU PCMI(isje6-componentId)" service.
```
> sc delete "FUJITSU PCMI(isje6-componentId)"
```
  Delete the files listed below.
  - symfowareServerInstallDir/java/etc/domain.conf
  - symfowareServerInstallDir/java/etc/domain1_container.conf
  Example
  componentId has the following format:
```
STFSYMOIDB + versionLevel + firstDigitOfArchitecture
```
  - versionLevel: Version/level of Symfoware Server
  firstDigitOfArchitecture: First digit of product architecture, that is "3" for the 32-bit version, and "6" for the 64-bit version
```
STFSYMOIDB12106
```
7. Recreate PL/extJava
  Recreate PL/extJava after executing the pgx_jadmin command for PL/extJava and storing the Java applications. Refer to "Chapter 7 Setting up and Operating PL/extJava " for information on creating PL/extJava.
8. Start the instance
  Refer to 2.1 Starting and Stopping an Instance" for information on how to start an instance.
  If the instance fails to stop, refer to "8.10 Actions in Response to Instance Startup Failure".
9. Resume applications
  Resume applications that are using the database.
If a message was output indicating that the address cannot be assigned to the container server log or the domain server log, the specified port number may be in use by another server.
If that is the case, change the port numbers and then restart the instance (refer to "7.2.1 Preparing Port Numbers" and "7.3.3.3 Changing Port Numbers" for details).
If a message was output to the server log of Symfoware Server indicating that the Java EE DAS service has failed to start, but a corresponding message indicating the cause of the failure has not been output to the domain server log, the cached information may not be up to date.
If that is the case, delete the file below and then restart the instance.
```
domainRoot\domains\domain1\osgi-cache\felix
```
If a message was output indicating that there are PL/extJava processes already running, there may be processes still running after the PCMI service that monitors processes ended in an error.
If that is the case, perform the following procedure to forcibly terminate the unnecessary processes, and then restart the instance.
1. End server instances(Java VM)
  Forcibly terminate any processes listed in the file below and that are still running, then delete the file (perform this step for all server instances(Java VM)).
```
domainRoot\nodes\localhost-domain1\serverInstance(JavaVM)Name\config\pid
```
2. End Java EE DAS service processes
  Forcibly terminate any processes listed in the file below and that are still running, then delete the file.
```
domainRoot\domains\domain1\config\pid
```
3. End web server processes
  Forcibly terminate any processes listed in the file below and that are still running, then delete the file.
```
symfowareServerInstallDir\java\ahs22\plextjava\domain1\logs\httpd.pid
```
4. End PCMI service processes
  Use the method below to check if there are PCMI service processes still running - if there are, forcibly terminate them, and then restart the instance.
  - Windows Task Manager