Startup Issues

The following describes some possible problems with application startup. The two most common reasons for the inability to start an application server which worked previously are the following:

#1 Startup difficulties for Solaris installations only

When you started the application as root previously and are now trying to start as another user (such as dorado). Startup fails because root did the prior startup, the dorado user does not have permission to write to the deploy directory.

Workaround:

1. Stop any dorado process.

2. As root, run chown dorado -R * from $OWARE_USER_ROOT (This recursively changes ownership to dorado)

3. Then chown root $OWARE_USER_ROOT/oware/bin/openFD_Solaris

4. Restart appserver

#2 Startup difficulties for both Solaris and Windows installations

If an application or mediation server goes down ungracefully for any reason the JMS message database may be corrupt in $OWARE_USER_ROOT\oware\jboss*\ser­ver\oware\data. When it becomes corrupted the application server will not start.

Workaround:

Removal of the data directory’s contents permits application or mediation server startup.

See Unix Issues for additional information about troubleshooting Linux and Solaris.

Initial Logon after installation fails

If, after installation, your attempt to logon to the application fails with message Connection to server failed in the Logon window.

The most likely cause is that the application server is not running. The status of the appserver can be indicated by an icon in the Windows System Tray. (see Windows Server Monitor).

If the icon is red or yellow, the client will be unable to connect. If it is red, right-click on it and select Start from the menu. The icon turns yellow as the application server starts. Wait until the icon is green, and repeat the logon procedure. If this does not work, contact technical support.

Logon Fails with Invalid Logon Message

When you enter your User Id and Password in logon dialog and click Logon, the Invalid Logon message appears. Ensure you are entering the correct User Id and Password and click Logon. If you have forgotten the User Id or the Password, or if another user has changed the Password for the User Id, you may have to re-install the software.

When the application client screen appears, you can change the password for the affected User Id with the Control Panel.

Client on separate machine fails

Distributed medserver or client failures to start can occur when multicast is disabled on your network. The workaround is to this property in oware­apps\installprops\lib installed.properties

oware.application.servers=<AS-IP>

AS-IP is the IP Address of the application server machine. You must do this on all client machines

Unsynchronized Clocks in Clustered Installations

All machines in a cluster, or distributed system, including clients must have synchronized system clocks. If this is not true, systems may start, but will not work correctly.

Other Failures on Startup

• Another instance of appserver/medserver may be running. Common error:

2005-06-25 08:47:51,968 ERROR [org.jboss.web.WebService] Starting failed

java.net.BindException: Address already in use: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

Solution: Stop appserver, and stop other appserver instance, then restart appserver.

• Best practice is to start or stop application server with the process monitor icon (installed by the application), when it is installed as a service. Stopping, starting or Restarting the service through OS service manager is not recommended. If the Redcell status icon in the tray is green and you restart procman (“process manager”) from Windows’ Control Panel services, an error message saying the service did not stop properly appears. The tray icon then turns white. Since the application server is still running, when you try to restart the service again, the icon turns red.

To restore the Process monitor icon to function correctly and show status, stop all Java and WMI processes in the process manager. A system reboot also re-initializes the OWProcMan (process monitor). Note that the service name may be different if your package has been specifically branded. The executable path for the service is \....\oware\bin\owprocman.exe.

More Failures on Startup

• Failure to connect with database can occur when

–The Oracle instance not running

–Oracle lacks connectivity

–Oracle database is not built

–MySQL not running (it should start automatically)

–Firewall blocks ports the database needs.

• Changed properties files

–Delete the contents of oware\temp

• Connection to appserver fails

–Appserver has not fully started. Look for >>>>> Oware Application Server initialization COMPLETE. <<<<< in the server.log

Login Failures

• Invalid Logon

–Incorrect User name or password

–Default is User admin, no password

–User has changed and forgotten password

• Account is inactive

–User has set up Application Security Policy so passwords or accounts have expiration date

–Use different account