P3
Brian Smithey(###@###.###) installed the S1A7 bits downloaded from sun.com and was trying to use the JDBC sample application.He ran into a problem, when he started the pointbase from a different directory. I cut n paste his email about the description of the problem.
For more info,pl contact Brian or me.
uday.
here is the offline discussion:
=====================================
Hey Uday, I think I figured out the problem!
When I was starting pointbase, I was in some random directory (NOT the
pointbase/server directory), and was starting the server using the
absolute pathname to the server startup script. As root, I was doing:
/opt/SUNWappserver7/pointbase/server/StartServer.sh
When I did a cd into the /opt/SUNWappserver7/pointbase/server directory
and started the server with:
./StartServer.sh
it worked fine, using the database file in .../pointbase/server/databases.
I think I know why this is happening. In the .../pointbase/server
directory, there is a file called pointbase.ini. This is likely
a pointbase config file. The first line in the file says:
database.home=databases
I suspect that the pointbase server is using the value of this
property to locate the database files. Since the value is not
an absolute path (does not start with '/'), the server probably
ends up doing something like
open("databases/sun-appserv-samples.dbn")
If you are in the pointbase/server directory, that works fine.
If the working directory of the server is NOT pointbase/server,
then that command fails. My guess is that be default, if it
can't find the database files using that property value, it
just creates a directory called /pointbase, and uses that as
its "home". Then it tacked on the value of the property, which
is why we saw your sampleUday database created in /pointbase/databases.
Too bad it doesn't log a message to the console or something!
Would you suggest to the QA engineer to try their test again, and
this time, change to some random directory (like /tmp) and start
the pointbase server script using an absolute path? See if that
works, or fails the same way mine did. If it fails, they should
be able to copy the db files to /pointbase/databases and make it
work, as I did yesterday.
This is a pretty serious problem, the "Getting Started" documentation
implies that you can start the server from any directory -- they give
the example of starting the server using:
Execute: <appserver_install_dir>/pointbase/server/StartServer.sh
It doesn't come right out and say that you can be in any directory
that you want, but it also doesn't insist that you cd into the
pointbase/server directory before starting the server. And the
example above for starting the server, using an absolute path,
led me to believe that you could start it from anywhere.
Brian
###@###.### 2002-11-19
###@###.### 2003-04-07
For more info,pl contact Brian or me.
uday.
here is the offline discussion:
=====================================
Hey Uday, I think I figured out the problem!
When I was starting pointbase, I was in some random directory (NOT the
pointbase/server directory), and was starting the server using the
absolute pathname to the server startup script. As root, I was doing:
/opt/SUNWappserver7/pointbase/server/StartServer.sh
When I did a cd into the /opt/SUNWappserver7/pointbase/server directory
and started the server with:
./StartServer.sh
it worked fine, using the database file in .../pointbase/server/databases.
I think I know why this is happening. In the .../pointbase/server
directory, there is a file called pointbase.ini. This is likely
a pointbase config file. The first line in the file says:
database.home=databases
I suspect that the pointbase server is using the value of this
property to locate the database files. Since the value is not
an absolute path (does not start with '/'), the server probably
ends up doing something like
open("databases/sun-appserv-samples.dbn")
If you are in the pointbase/server directory, that works fine.
If the working directory of the server is NOT pointbase/server,
then that command fails. My guess is that be default, if it
can't find the database files using that property value, it
just creates a directory called /pointbase, and uses that as
its "home". Then it tacked on the value of the property, which
is why we saw your sampleUday database created in /pointbase/databases.
Too bad it doesn't log a message to the console or something!
Would you suggest to the QA engineer to try their test again, and
this time, change to some random directory (like /tmp) and start
the pointbase server script using an absolute path? See if that
works, or fails the same way mine did. If it fails, they should
be able to copy the db files to /pointbase/databases and make it
work, as I did yesterday.
This is a pretty serious problem, the "Getting Started" documentation
implies that you can start the server from any directory -- they give
the example of starting the server using:
Execute: <appserver_install_dir>/pointbase/server/StartServer.sh
It doesn't come right out and say that you can be in any directory
that you want, but it also doesn't insist that you cd into the
pointbase/server directory before starting the server. And the
example above for starting the server, using an absolute path,
led me to believe that you could start it from anywhere.
Brian
###@###.### 2002-11-19
###@###.### 2003-04-07