Issues with adding, removing, or publishing applications to the server
You can encounter problems and limitations when you try to add, remove, or publish an application to the server. Issues include, among others, publishing failures due to duplicate class errors and trying to publish an application from the work bench that was installed by the administrative console.
- Troubleshooting if a problem is related to the workbench or the application server
If you encounter errors or problems when you are running your application on the server by using the development workbench, try reproducing the problem by using only the tools that are provided by the application server without the use of the development workbench. For example, to reproduce the problem on WebSphere® Application Server, try installing and publishing the enterprise (EAR) application by using only the administrative console, see the Installing enterprise application files with the console topic available in the information center for WebSphere Application Server. - Limitation on Java 2 security application policy on WebSphere Application Servers
The ${application} policy in the Java™ 2 policy security files (for example was.policy) applies only to the EAR project. - Removal of a module shared in multiple projects
If a module is shared among multiple projects that run on a WebSphere Application Server and one of the projects is removed from the server, other projects must be restarted before they can access the resources, such as bean classes, in the project. - Changing a Web or EJB project results in an application to be restarted with option Never publish automatically
When the publishing option Never publish automatically is enabled with the publishing setting for WebSphere Application Server Run server with resources within the workspace enabled, the WAR can still be restarted even without a publishing taking place. This problem is caused by automatic class reloading in WebSphere Application Server. - Limitations of Microsoft SQL Server JDBC driver when publishing to a remote WebSphere Application Server
It is a known problem that when you are publishing to a remote WebSphere Application Server by using a Microsoft SQL JDBC driver, you might get the following error. This error prevents you from making a database connection: - Publishing fails with duplicate class error
When you are publishing an application to a remote or local WebSphere Application Server running with the Run server with resources on Server publishing setting, you might encounter the following error message: - Unable to use the workbench to publish the same application that was installed by using the administrative console
An application that is published by using the workbench might display a different application name on the server, as the same application installed by using the administrative console from WebSphere Application Server.
Parent topic: Limitations and troubleshooting tips for Server tools

