Problem:

• Product Name: Borland Enterprise Server
• Product Version: 6.x
• Product Component: SonicMQ JMS
• Platform/OS version: All
• JDK/Compiler version: JDK 1.4.2 and above

This article describes on why SonicMQ installation fails while re-installing BES and provides the steps to follow to install it successfully.

Resolution:

It is likely that BES unistallation did not remove SonicMQ installation for the first time, hence during subsequent installations it fails to install SonicMQ.

1. SonicMQ may silently fail to install, and the Borland Enterprise Server installer may not report this failure. To verify this problem, check the file <install_root>/jms/sonic/silent.log. If it contains:

Install started on Mon Nov 19 13:23:43 PST 2001
ERROR: in Configuration Process!: Mon Nov 19 13:23:50 PST 2001
Configuration directory missing. Mon Nov 19 13:23:50 PST 2001
ERROR: Installation encountered errors. Mon Nov 19 13:23:50 PST 2001

this may be the cause. You may also see:

Exception in thread "main" java.lang.NoClassDefFoundError:
progress/message/tools/IBrokerManagerListener
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)

To correct the problem, take these steps.

- Uninstall Borland Enterprise Server:
Make sure you have sufficient temporary space in your home directory. On Unix and Linux, your home directory is used for temporary space. On Windows platforms, your user profile directory is used. This is typically on the same drive as the system root, and the value is typically contained in the environment variable %USERPROFILE%.
 
- Reinstall Borland Enterprise Server:
Verify SonicMQ installation, either run the server or, check <install_root>/jms/sonic/silent.log

The SonicMQ installer will leave temporary files and directories in your home directory on Unix and Linux, or in your user profile directory on NT. These directories typically have a name with a pattern like "ismp*". These directories may safely be deleted after installation.

 

2. Uninstalling Borland Enterprise Server
You must take the following steps when uninstalling Borland Enterprise Server to make sure SonicMQ is uninstalled properly.

- Uninstall SonicMQ, using SonicMQ's uninstaller:
You can access the Windows uninstaller through the Programs Menu or using the batch file <install_root>/jms/sonic/uninstall.bat. You can access the Unix or Linux uninstaller using the shell scripts <install_root>/jms/sonic/uninstall.sh. The SonicMQ uninstaller will prompt you about deleting a large number of files. It is safe to say yes to all these requests.
 
- Uninstall Borland Enterprise Server:
 The uninstaller is available at <install_root/UninstallerData/uninstall.exe on Windows and <install_root>/UninstallerData/uninstall on Unix and Linux.

It is safe to delete all remaining files under <install_root>/