Problem with clloudscape rmi jdbc driver

Question

I am using Cloudscape rmi jdbc driver, where Cloudscape runs as
a separate server. I am using WL6.1 running on Red Hat Linux
7.1. I defined a Cloudscape connection pool and data source. I
have to start Cloudscape before WebLogic or I get the following
exception:
<Feb 18, 2002 11:39:42 PM EST> <Error> <JDBC> <Cannot startup
connection pool "EStoreConnectionPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Connection refused to host: localhost;
nested exception is:
java.net.ConnectException: Connection refused
at RmiJdbc.RJDriver.connect(RJDriver.java:149)
at java.sql.DriverManager.getConnection
(DriverManager.java:512)
etc.
No surprises here: However if I start Cloudscape first and
WebLogic second, I get the following message in Weblogic:
Starting WebLogic Server ....
<Feb 19, 2002 12:58:21 AM EST> <Notice> <Management>
<Loading configuration file ./config/mydomain/config.xml ...>
<Feb 19, 2002 12:58:43 AM EST> <Notice> <WebLogicServer>
<Starting WebLogic Admin Server "myserver" for domain "mydomain">
<Feb 19, 2002 12:59:00 AM EST> <Notice> <Management>
<Starting discovery of Managed Server... This feature is on by
default, you may turn this off by passing
-Dweblogic.management.discover=false>
This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
It is a violation of the license agreement to deploy this version
in a production application.
For information about licensing Cloudscape for application
deployment, contact [email protected] or call
888/595-2821 ext. 7664.
Additional licensing information can be found at
http://www.cloudscape.com/licensing.
<Feb 19, 2002 12:59:31 AM EST> <Notice> <Management>
<Application Poller started for development server.>
<Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
<ListenThread listening on port 7001>
<Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
<SSLListenThread listening on port 7002>
<Feb 19, 2002 12:59:32 AM EST> <Notice> <WebLogicServer>
<Started WebLogic Admin Server "myserver" for domain "mydomain"
running in Development Mode>
The console running cloudscape then contains this message:
This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
It is a violation of the license agreement to deploy this version
in a production application.
For information about licensing Cloudscape for application
deployment, contact [email protected] or call
888/595-2821 ext. 7664.
Additional licensing information can be found at
http://www.cloudscape.com/licensing.
Tue Feb 19 00:56:43 EST 2002: [RmiJdbc]
COM.cloudscape.core.JDBCDriver registered in DriverManager
Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] Binding RmiJdbcServer...
Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] No installation of RMI
Security Manager...
Tue Feb 19 00:56:46 EST 2002: [RmiJdbc] RmiJdbcServer bound in
rmi registry
WARNING: Cloudscape (instance
c013800d-00ec-1cf6-94ca-007f00000100) is
attempting to boot the database
/app/cloudscape_3.6/database/acme/estore even
though cloudscape (instance c013800d-00ec-1cca-ed1d-007f00000100)
may still be active. Only one instance of cloudscape should boot
a database at a time. Severe and non-recoverable corruption can
result and may have already occurred.
Well, it looks like I'm damned if I do and damned if I don't.
Any suggestions?

Answer 1

Actually, it happened because Cloudscape was not properly shut down. Thanks for
responding. I was having some troble with the stopCS script, but its OK now.
"Laurent Goldsztejn" <[email protected]> wrote:
>
Hi Douglass,
The evaluation version of Cloudscape is limited to one concurrent user
per session,
so only one instance of cloudscape can be running at a time. The problem
reported
here can occur if you try to run more than once instance of any product
that
uses Cloudscape -- including WLS or Cloudview. This evaluation version
of Cloudscape
is intended for test purposes only.
This error can also occur on Solaris if you stop the server using ctrl-C
or ctrl-D,
which causes a database lock to remain in place after the server has
stopped.
You can get rid of it by deleting $BEA_HOME/wlserver6.1/samples/eval/cloudscape/data/demo/db.lck
The safest way to stop the server is to use the Admin console or the
SHUTDOWN
command from the command line.
Laurent Goldsztejn
Developer Relations Engineer
BEA Support