Top
Symfoware Server V12.1.0 Messages
FUJITSU Software

2.62.52 16551

could not execute the Java function at the application server: HTTP status code @1@ details: "@2@"

[Description]

The application server could not execute the Java function.

[System Processing]

Processing will be aborted.

[Action]

Check the Java function of registered in application server.

Check the details.

- The classpath is not found. (plextjava_lib_dir=%s2)

%s2: directory

The directory that stores the Java function is not in the application server.Check the directory and register the Java function.

- The return type is different. (%s3)

%s3: data type

The return value of the Java function is not corresponding to the CREATE FUNCTION definition. Check the data type of Java function.

- The method is not found. (%s4)

%s4: data type

The Java function to which the data type is corresponding is not found. Check the data type of Java function.

- The class is not found.(%s5)

%s5: class name

The Java function to which the class name is corresponding is not found. Check the class name of Java function.

- The method is not static modifier. (%s6)

%s6: Java function name

The Java function is not defined by "Static". Check the Java function definition.

here is no executed authority. (%s7)

%s7: Java function name

The Java function is not defined by "Public". Check the Java function definition.

- Java application throws exception(%s8).

%s8: exception

The exception was generated by the Java function. Check the Java function definition.

- no message

The following causes are thought.

-There is a possibility that the container is not made. Make the container in application server.

a) There is a possibility where the number of server instances is insufficient. Add server instance (JavaVM) to the application server.

b) There is a possibility that memory shortage occurs. Check the Java application.

c) There is a possibility that the time-out is generated. Check the Java application.

d) There is a possibility that abnormality occurs by the application server. Check the following logs.

- Event log (For Windows(R))/system log (For Linux).

- Server log of container

- JavaVM log of container

- Trace log of Web server

- Internal log of Web server