An attempt to connect with the SFO server has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: SFO server name
dd....dd: Address and port number of the Naming Service on the SFO server

Description

An attempt to connect to the SFO server has failed.

Take action based on the following causes:

• The SFO server is not running.
• Some error occurred in the communication path with the SFO server.
• The IP address or the port number of the CORBA Naming Service invoked in the SFO server specified in the user property file is wrongly specified.
• The option -nosecurity is not specified in the cjstartsv command during the startup of the SFO server.
• The memory of SFO server is insufficient.
• The negotiation cannot be completed within time.

Action

Check the error message output in the J2EE server or the SFO server, and also the working state of the SFO server, and ascertain the cause of failure in connecting.

Take the following actions depending upon the cause:

When the SFO server is not running

Start up the SFO server, and then start the J2EE application.

When a problem exists in the communication path with the SFO server

Remove the problem and then restart the J2EE application.

When the IP address or the port number of the CORBA Naming Service invoked in the SFO server is specified wrongly

Stop the J2EE server once, and then after setting the correct information in the user property file, start the J2EE server.

If an attempt to negotiate with the SFO server has failed:

Specify the correct settings for the J2EE server based on the message KDJE34207-Eor KDJE34246-E output in the message log, and for the SFO server based on the message KDJE34008-E, KDJE34026-E, or KDJE34003-I output in the message log. When the settings of the Web application are changed, you must restart the J2EE application, and when the server ID is changed, you must restart the J2EE server.

When the option "-nosecurity" is not specified in the command cjstartsv during the startup of the SFO server

Specify the -nosecurity option, restart the SFO server, and then start the J2EE application.

When the memory required in the SFO server is insufficient

Revise the estimation of memory required in the SFO server.

When the negotiation has timed out

Check the working state of the SFO server and the memory usage of the machine on which the SFO server is running, as well as CPU usage. In the case of the occurrence of a problem, remove the cause, and then restart the J2EE application.