EJBDeploy fails with "java.lang.IllegalStateException: Unable to acquire application service."
This error can occur when running ejbdeploy.bat or ejbdeploy.sh scripts from the command line, or it can be seen in the logs of other IBM software that make use of ejbdeploy.
Besides IllegalStateException, the following is another possible EJBDeploy error(s):
* Error executing deployment: org.eclipse.core.runtime.CoreException. Error is Plug-in com.ibm.etools.ejbdeploy was unable to load class com.ibm.etools.ejbdeploy.batch.plugin.BatchEx
org.eclipse.core.runtime.CoreException: Plug-in com.ibm.etools.ejbdeploy was unable to load class com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.
This problem may occur when Enterprise JavaBeans Deploy is updated as part of a Fix Pack install and there are files in the EJB Deploy configuration directory from the previous EJB Deploy install.
Resolving the problem
To resolve this problem, delete all of the files in the EJB Deploy configuration directory except for the config.ini file.
To determine the location of the EJB Deploy configuration directory, run the ejbdeploy command with the -log option like this:
cd "C:\Program Files\IBM\WebSphere\AppServer\bin"
ejbdeploy.bat input_EAR working_DIR output_EAR -log
./ejbdeploy.sh input_EAR working_DIR output_EAR -log
In the commands, input_EAR is the input EAR file, output_EAR is the output EAR file, and working_DIR is the temporary working directory.
Similar ejbdeploy commands can be issued on any other platforms on which IBM WebSphere Application Server V6.1 is supported. This is also applicable to WebSphere Application Server v7.x.
The output of the ejbdeploy command, with -log option, will show the location of the EJB Deploy configuration directory. Go do that directory and delete all files except for the config.ini file. Now, re-run your ejbdeploy command and it should no longer have the error.
As an example, on a Linux platform with WebSphere Application Server Network Deployment (ND) installed in /usr/WebSphere/AppServer , you may have two locations:
The second location corresponds to the deployment manager machine/profile.
|Application Servers||WebSphere Application Server||Linux, Windows||126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 6.1|