We have copied a working Ebase 3.4 (31102007) Environment from a Windows 2003 sever to SuseLinux 10.
On this server are:
Apache Tomcat Version 5.0.18
Java 1.4.2
This worked fine for a few days. Since then, when starting the Ebase server it can't find the UFS repository and throws this error:
Wed Jan 30 09:25:39: Error : Error getting connection from datasource UFSREPOSITORY, SQLException in StandardPoolDataSource:getConnection exception: java.sql.SQLException: SQLException in StandardPoolDataSource:getConnection no connection available java.sql.SQLException: Cannot get connection for URL jdbc:derby:UFS;create=false : Database 'UFS' not found.
I have tried to fix this by restoring the DB folder from a backup. But this didn't work.
Any ideas on how to fix this problem?
Thanks in advance!
Start up problem: Error getting connection from datasource
Moderators: Jon, Steve, Ian, Dave
- dvanhussel
- Ebase User
- Posts: 161
- Joined: Fri Oct 19, 2007 12:45 pm
- Location: Haarlem, the Netherlands
- Sarah
- Ebase User
- Posts: 63
- Joined: Fri Sep 07, 2007 2:42 pm
- Location: Sandy, UK
- Contact:
If your new system was working OK to start with, it sounds like something must have been changed. We've experienced this problem for different reasons, including:
***For information, please can I add that we don't recommend Java 1.4.2 with Ebase version 3.4 as there are some incompatibilities - we recommend using Java 1.5.***
- 1. an incorrect URL to the database in the ufs.xml file
2. the database isn't running or has been stopped
3. two copies of the ufs.xml file are in the UfsServer/tomcat/conf/Catalina/localhost folder. If there are two copies, they will both be accessed by the system (including the older one with incorrect information) whatever the names of the files are.
4. the datasource name in the ufs.xml not matching the datasource name in the database settings within Ebase Designer
***For information, please can I add that we don't recommend Java 1.4.2 with Ebase version 3.4 as there are some incompatibilities - we recommend using Java 1.5.***
0 x
- dvanhussel
- Ebase User
- Posts: 161
- Joined: Fri Oct 19, 2007 12:45 pm
- Location: Haarlem, the Netherlands
Thanks!
It was in fact the URL in ufs.xml (it was 'just' UFS and is now /usr/ebase_o/UfsServer/DB)
Now the server starts, en works, fine.
The next problem I run into is that when I try to start EbaseDesigner, I get the following error:
Wed Jan 30 15:56:01: Error : Error detected by the designer server component:
java.lang.SecurityException: Unable to locate a login configuration
It was in fact the URL in ufs.xml (it was 'just' UFS and is now /usr/ebase_o/UfsServer/DB)
Now the server starts, en works, fine.
The next problem I run into is that when I try to start EbaseDesigner, I get the following error:
Wed Jan 30 15:56:01: Error : Error detected by the designer server component:
java.lang.SecurityException: Unable to locate a login configuration
0 x
- Sarah
- Ebase User
- Posts: 63
- Joined: Fri Sep 07, 2007 2:42 pm
- Location: Sandy, UK
- Contact:
This is a common problem when setting up Ebase, and means that the path to the Ebase login file is incorrect.Wed Jan 30 15:56:01: Error : Error detected by the designer server component:
java.lang.SecurityException: Unable to locate a login configuration
There is a post on this Forum entitled 'Unable to login to Ebase Designer after upgrading' that explains how to solve it: http://forum.ebasetech.com/forum/viewto ... ight=login
Please can you let us know how you get on with this?
0 x
- dvanhussel
- Ebase User
- Posts: 161
- Joined: Fri Oct 19, 2007 12:45 pm
- Location: Haarlem, the Netherlands
It turned out that the system admin 'introduced' a new user wich was used to start Java from start.sh
As a result the JAVA_OPTS where not corectly exported for this user. We now export the JAVA_OPTS in startup.sh
In fact this also solves the problem with the UFS repository as its location is set also in the JAVA_OPTS.
Thank you for your help!
As a result the JAVA_OPTS where not corectly exported for this user. We now export the JAVA_OPTS in startup.sh
In fact this also solves the problem with the UFS repository as its location is set also in the JAVA_OPTS.
Thank you for your help!
0 x
Who is online
Users browsing this forum: No registered users and 62 guests