General troubleshooting
If you encounter
a problem when trying to start a Web server from the Servers view,
try the following tips:
- Stop and restart the workbench.
- List the processes that are running on the server. There should
be one javaw.exe process for the workbench and one
for each Web server. Stop these processes. Then, restart your workbench
and start the server by using the Servers view.
- Verify that you can start the Web server from outside of the workbench.
Delete all obsolete Web services from the Web server. Stop the server
manually and then start it from the Servers view in the workbench.
- If the preceding tips do not work, launch the Web server's administration
console and manually remove all of the deployed Web services. In the
Servers view in the workbench, remove the Web server instance and
add a new one. Then, redeploy the Web services.
Troubleshooting deployments on WebSphere Application
Server Community Edition Version 2.1 servers
When
creating a Web service for an WebSphere® Application Server
Community Edition Version 2.1 server, ensure that the case-sensitive
values of the artifact.dataSourceArtifactId and artifact.dataSourceGroupId parameters
match those that you used when you created the database pool for the
Web server. By default, dataSourceArtifactId is
set to database_name, and artifact.dataSourceGroupId is
set to console.dbpool.
If you need to remove
a database pool, select J2EE Connectors menu option on the left side
of the Administrative Console. Select the database pool from the list
of pools. Click Uninstall.
Ensure that
JAR files are installed correctly.
Troubleshooting deployments on Apache Tomcat Version
5.5 and Version 6 servers
When creating a Web service for
an Apache Tomcat Version 5.5 or Version 6 (all releases) server, ensure
that the case-sensitive value of the artifact.DataSourceGlobalName parameter
matches the value that you used when you defined the database pool.
By default, artifact.DataSourceGlobalName is
set to jdbc/database_name.