Starting and Shutting Down the Cloudconnector Server
Page 4 of 5

Shutting Down Cloudconnector

The Cloudconnector installation includes two shutdown scripts, located in $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. (Make sure your PATH includes this directory before you run the shutdown script.)

  • stopCS.bat (Windows)
  • stopCS.ksh (UNIX)

To shut down Cloudconnector, run the appropriate script from any directory on the client. Property shutting down Cloudconnector causes a checkpoint command to be issued, and minimizes the recovery procedures required upon the next startup (thereby reducing startup time). If you simply interrupt the running server with a ^C command, recovery will be run on the databases when they are rebooted.

For example, on Windows:

C:\> stopCS

In the client Window, a message similar to the following displays:

T3://127.0.0.1:7001 successfully shutdown
Shutdown sequence initiated

An example of the output you will see at the server console:

Fri Sep 10 13:34:54 PDT 1999:<I> <RJVM> Closing connection to localhost/127.0.0.1 -5754524976542505027
Fri Sep 10 13:34:54 PDT 1999:<I> <CliCon#|CloudscapeServer|2.936995306288> Connection to client for [CliCon: #|CloudscapeServer|2.936995306288] has been unexpectedly lost because t3 socket to -5754524976542505027C10.10.11.67 failed and could not be reconnected.
Initiating hard disconnect.
Fri Sep 10 13:34:54 PDT 1999:<I> <CliCon-#|CloudscapeServer|2.936995306288> Removing [CliCon: #|CloudscapeServer|2.936995306288 unbound] because of hard disconnect timeout
Fri Sep 10 13:35:06 PDT 1999:<I> <WebLogicServer> Invoking garbage collection
Fri Sep 10 13:35:06 PDT 1999:<I> <GC> GC: Before free/total=15071048/16777208 (89%)
Fri Sep 10 13:35:06 PDT 1999:<I> <GC> GC: After free/total=15685880/16777208 (93%)
Fri Sep 10 13:35:06 PDT 1999:<I> <WebLogicServer> Invoking garbage collection
Fri Sep 10 13:35:06 PDT 1999:<I> <GC> GC: Before free/total=15674504/16777208 (93%)
Fri Sep 10 13:35:06 PDT 1999:<I> <GC> GC: After free/total=15685464/16777208 (93%)

If Cloudscape has already shut down (for example, because an application used the shutdown=true form of the database connection URL), a warning message is issued:

The WebLogic Server at T3://127.0.0.1:7001 is not responding
because of [java.io.IOException: Bootstrap unable to get a t3 connection to loca
lhost/127.0.0.1].
Are you sure its running?
Ignoring request to disconnect client that is already disconnected.
java.io.IOException: Bootstrap unable to get a t3 connection to localhost/127.0.
0.1
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java
:230)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:201)
at weblogic.common.internal.DNSBasedRJVMFinder.findOrCreate(Compiled Cod
e)
at weblogic.common.internal.ServerURL.findOrCreateRJVM(ServerURL.java:15
6)
at weblogic.common.T3Client.connect(T3Client.java:382)
at weblogic.Admin.connect(Admin.java:133)
at weblogic.Admin.main(Compiled Code)
at weblogic.T3Admin.main(T3Admin.java:26)

Shutting Down Cloudconnector when User Authentication Is Enabled

When user authentication has been turned on in Cloudscape with the cloudscape.connection.requireAuthentication property, user credentials are required to shut down the server. To provide user credentials for the shutdown, edit the weblogic.properties file to provide valid arguments, as follows:

weblogic.system.shutdownArgs.CloudscapeShutdown=user=name,password=pwd

Using ;shutdown=true with Concurrent Embedded and Remote Access

If you attempt to shut down Cloudconnector via the jdbc:cloudscape:weblogic: URL and also have an embedded system booted in the client JVM, the shutdown may fail with the following message:

"Database name must not be specified"

To avoid this error, use a longer-form WebLogic database connection URL:

jdbc:weblogic:t3?weblogic.t3.driverURL=t3://hostname:portnumber
&weblogic.t3.serverClassName=COM.cloudscape.core.JDBCDriver
&weblogic.t3.serverURL=jdbc:cloudscape:;shutdown=true

Specify the URL as a single string with no white space, or represent line breaks as the parameter value in a DriverManager.getConnection request.