The server might not stop completely when stopping the server from the Servers view

When you stop the server from the Servers View, the server might not completely stop. The Servers View displays as Stopped but the server process might be in a non-responsive state. The non-responsive state usually occurs when artifacts such as your application or the workbench remains holding onto references to classes on the server. The following are example scenarios:

Important: Applicable to WebSphere® Application Server traditional
  • Applications that are in endless loops, or application hold on references to some classes on the server
  • Applications that make Cloudscape or Derby database connection without cleaning up their connection
  • Using the Test Connection button in the New Connection wizard of the data tools to open a connection to a Cloudscape or Derby database without disconnecting from the database
Restriction: Multiple connections to a single Cloudscape or Derby database are not supported due to a Cloudscape or Derby configuration restriction. If you maintain the database connection to the database from the Database Explorer and a server tries to make another Cloudscape or Derby connection through a data source, the second connection is going to fail. As a result, you need to close the connection from the Database Explorer before a server can establish a connection to the Cloudscape or Derby database.
To work around the problem, you to need use the functions from your operating system to stop the Java™ process on which the server is running. Alternatively, you can restart the workbench to force the reference to be released. The last example scenario that is described in the third bullet, you can use the Database Explorer view to connect and then disconnect from the Cloudscape or Derby database connection.
Icon that indicates the type of topic Reference topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: rcloudderby.html