Troubleshooting Service Deployment Errors

When troubleshooting Sybase WorkSpace deployment errors, keep in mind that the deployment services are implemented in an intermediate layer between the GUI and the application server. The GUI remotely invokes the deployment services which in turn remotely invoke application server components.

Sybase WorkSpace service deployment maintains its own repository of deployed packages. Any attempt to undeploy a service package with Jagtool or EAServer Manager results in an improper undeployment.

Problem 1: General deployment errors occur when deploying a packaged service.

Solution 1: Use the following procedure to troubleshoot errors during deployment:

1. Save a copy of the <service package name>.svcpkg file.

   Sybase tech support may request this file.

2. Closely examine the causal chain of com.sybase.uo.management.ManagementException stack traces displayed in Sybase WorkSpace or the mtool command line utility.

3. Review these log files:

   
   
   • <installation directory>\Sybase\WorkSpace\Eclipse\workspace\.metadata\.log
   • <installation directory>\Sybase\WorkSpace\DevRuntimes\EAServer\SysMgmt\agent.log
   • <installation directory>\Sybase\WorkSpace\DevRuntimes\EAServer\bin\Jaguar.log
4. Enable the agent.log debug messages to obtain package deployment information in greater detail. Edit the <installation directory>\Sybase\WorkSpace \DevRuntimes\EAServer\SysMgmt\agent.cmd file, stop and restart the server, then redeploy the service package.
   Note:

   If you use long names for service files and the services package file, deployment may fail when the path to an intermediate generated file exceeds operating system limits. In this case, repackage the services with a package that uses a shorter file name.

Problem 2: A general deployment failure. When attempting to deploy a service package, the deployment fails and you receive the following error message in the server log file:

javax.naming.NamingException: NotFound:SOAPMessageListenerEJBLocal. Root exception is javax.naming.NamingException. Root exception is org.omg.CORBA.OBJECT_NOT_EXIST

Solution 2: EAServer creates CORBA skeletons that correspond to the components in the package. When the package name and the file path to the Sybase server are long, the EAServer skeleton name may exceed the maximum name length for Java classes (256 characters).

To correct the problem:

1. Undeploy the service package.
2. Shorten the service package name.
3. Repackage service package.
4. Redeploy the service package.

Problem 3: When attempting to deploy a service package, the deployment fails and the following occurs:

• The server log file reports the error:

  javax.naming.NamingException: <details of error> Root exception is org.omg.CORBA.OBJECT_NOT_EXIST

• In addition, the agent.log reports the following warning:

  WARN com.sybase.management.jmx.system.XMLLoader-processServiceNode: Failure starting the service <RMIRegistry>: java.rmi.server.ExportException: Port already in user:1099; nested exception is: java.net.BindException: Address already in use: JVM_Bind

• The SybAgent console may report the exception:

  Error shutting remote Agent down: javax.naming.NameNotFoundException.jrmp

Solution 3: This problem occurs when an attempt is made to start the Service Container runtime while a process other than SybAgent is already listening on the default TCP/IP port 1099. See Resolving an EAServer RMI Registry Port Conflict for instructions on resolving this conflict.