Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » OSEE » Ubuntu (Unix) Postgresql. OSEE Server Not starting?
Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #537706] Thu, 03 June 2010 12:28 Go to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
My Question is: Based on the server log, did it start correctly & if not where would I start to find out the root cause?
Below you will see the following:
1) My Server Setup
2) Start up Script
3) Console output from server statup
4) Server Log file


My Environment setup:

ubuntu-10.04-server-i386 in a Virtual Machine,
Postgresql 8.4.4 (Has been configured for OSEE)

Start up Script:
java -Dosee.log.default=INFO -Declipse.ignoreApp=true -Dorg.osgi.service.http.port=8089 -Dosgi.compatibility.bootdelegation=true -Xms40m -Xmx512m -Dosee.db.connection.id=postgresqlLocalhost -Dosee.application.server.data="/home/gis2gps/oseeAppServer_postgres_0.9.1/data " -Dequinox.ds.debug=true -jar org.eclipse.osgi.jar -console


Here is the start up output for the OSEE Server:

I see an exception referencing "osee_server_lookup" what is it?




osgi> Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.DbConnectionInf ormation bind (70)
binding org.eclipse.osee.demo.db.connection.DemoDbConnectionInfo@ae533a

Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.parser.DbConfig Parser getAllDbServices (50)
in getAllDbServices 3

Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.DbConnectionInf ormation bind (74)
osee.microdoc: jdbc:postgresql://78.46.71.230:5432/OSEE : user=osee

Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.DbConnectionInf ormation bind (74)
postgresqlLocalhost: jdbc:postgresql://localhost:5432/OSEE : user=osee

Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.DbConnectionInf ormation bind (74)
derby: jdbc:derby://127.0.0.1:1621/DerbyDatabase; : user=osee

Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.DbConnectionInf ormation bind (70)
binding org.eclipse.osee.framework.database.internal.UriDbConnection Info @1f1235b

Adding: org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @7c3885
Thu Jun 03 05:14:28 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler addServerTask (41)
Adding task: Clean up join tables

Thu Jun 03 05:14:29 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties getOseeApplicationServerData (69)
Application Server Data: [/home/gis2gps/oseeAppServer_postgres_0.9.1/data]

Registered servlet '/osee/manager'
Registered servlet '/osee/resource'
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/index'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/branch'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Registered servlet '/osee/install/info'
Registered servlet '/osee/cache'
Registered servlet '/osee/model'
Thu Jun 03 05:14:31 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore getOseeVersionsByServerId (195)
Server lookup table is not initialized

Thu Jun 03 05:14:31 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
SEVERE org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (158)
This is the nested exception
org.postgresql.util.PSQLException: ERROR: relation "osee_server_lookup" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorRespons e(QueryExecutorImpl.java:1608)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer yExecutorImpl.java:1343)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut orImpl.java:343)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(Abs tractJdbc2Statement.java:2668)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:14 9)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:17 2)
at org.eclipse.osee.framework.database.core.ConnectionHandler.r unBatchUpdate(ConnectionHandler.java:81)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore.deregisterWithDb(ApplicationServerDataStore.j ava:74)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.writeToDataStore(InternalOseeServerInfo.java:114)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateRegistration(InternalOseeServerInfo.java:12 2)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager.executeLookupRegistration(ApplicationServerMana ger.java:87)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1.run(ApplicationServerManager.java:56)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)

Thu Jun 03 05:14:31 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore deregisterWithDb (77)
Server lookup table not initialized

Thu Jun 03 05:14:31 PDT 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
SEVERE org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (158)
This is the nested exception
org.postgresql.util.PSQLException: ERROR: relation "osee_server_lookup" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorRespons e(QueryExecutorImpl.java:1608)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer yExecutorImpl.java:1343)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut orImpl.java:343)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(Abs tractJdbc2Statement.java:2668)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:14 9)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:17 2)
at org.eclipse.osee.framework.database.core.ConnectionHandler.r unBatchUpdate(ConnectionHandler.java:81)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore.registerWithDb(ApplicationServerDataStore.jav a:94)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.writeToDataStore(InternalOseeServerInfo.java:115)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateRegistration(InternalOseeServerInfo.java:12 2)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager.executeLookupRegistration(ApplicationServerMana ger.java:87)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1.run(ApplicationServerManager.java:56)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)

Thu Jun 03 05:14:31 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore registerWithDb (97)
Server lookup table not initialized

Thu Jun 03 05:14:32 PDT 2010 org.eclipse.osee.framework.search.engine.internal.SearchEngi neTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable run (45)
Tagging on Server Startup was not run.


Server Log file:
!SESSION 2010-06-03 05:25:00.171 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -console

!ENTRY org.eclipse.osgi 4 0 2010-06-03 05:25:00.646
!MESSAGE Bundle plugins/org.eclipse.osee.framework.oracle@3:start not found.

!ENTRY org.eclipse.osgi 2 1 2010-06-03 05:25:00.865
!MESSAGE NLS missing message: SERVICE_REFERENCE_BOUND in: org.eclipse.equinox.internal.ds.SCRmessages

[Updated on: Thu, 03 June 2010 18:10]

Report message to a moderator

Re: Ubuntu Postgresql. OSEE Server Not starting? [message #537821 is a reply to message #537706] Thu, 03 June 2010 18:04 Go to previous messageGo to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
Wow, simular!
Link
Re: Ubuntu Postgresql. OSEE Server Not starting? [message #538053 is a reply to message #537821] Fri, 04 June 2010 16:57 Go to previous messageGo to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
I'm compressing the Virtual Machine into a rar file.
Is there anyone out there that has an FTP site I can put it on so someone can look into this?

the file is 3.34 GB

[Updated on: Fri, 04 June 2010 17:52]

Report message to a moderator

Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #538291 is a reply to message #537706] Mon, 07 June 2010 09:08 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
This may not be the whole problem, but it looks to be like you are pointing the binary data repository at the same place as the database.

Is ="/home/gis2gps/oseeAppServer_postgres_0.9.1/data" the location of your PostgreSQL data? If so, this should not be where osee.application.server.data is set. osee.application.server.data specifies the location of the binary data (i.e. large lumps of data from attributes such as Native Content or Word OLE Content which are zipped and stored outside the database to prevent excessivedatabase growth and poor backup performance), not the database. PostgreSQL handles the database location itself.

You can ommit the definition and OSEE will put it in the home directory of the user running the server, which is probably the best thing to do until you have things up and running. You can move it afterwards.

Also, why are you using such a long command line? The arguments should already be set in the application server's config.ini.

[Updated on: Mon, 07 June 2010 09:09]

Report message to a moderator

Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #543529 is a reply to message #538291] Tue, 29 June 2010 17:07 Go to previous messageGo to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
The script is from the install of the server, did not create that myself..
Was following the Users Guide to get where I am ...
Thank you for your insights, will try and figure this out.

Even with the removal of the external datastore I'm still getting the error...
Ya fun.
Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #543546 is a reply to message #537706] Tue, 29 June 2010 18:00 Go to previous messageGo to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
After reading I noticed I had client & server version of 0.9.1
so I upgraded both..
While starting the server for Postgres, I'm getting the following:
osgi> Registered servlet '/osee/manager'
Registered servlet '/osee/resource'
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/index'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/branch'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Registered servlet '/osee/install/info'
Registered servlet '/osee/cache'
Registered servlet '/osee/model'
Registered servlet '/osee/unsubscribe'
Registered servlet '/osee/ats'
Tue Jun 29 10:53:47 PDT 2010 org.eclipse.osee.framework.database.internal.Activator
SEVERE org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (155)
This is the nested exception
org.postgresql.util.PSQLException: ERROR: relation "osee_server_lookup" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorRespons e(QueryExecutorImpl.java:1608)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer yExecutorImpl.java:1343)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut orImpl.java:343)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(Abs tractJdbc2Statement.java:2668)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:14 8)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:16 9)
at org.eclipse.osee.framework.database.core.ConnectionHandler.r unBatchUpdate(ConnectionHandler.java:85)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore.deregisterWithDb(ApplicationServerDataStore.j ava:74)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.writeToDataStore(InternalOseeServerInfo.java:114)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateRegistration(InternalOseeServerInfo.java:12 2)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager.executeLookupRegistration(ApplicationServerMana ger.java:90)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1.run(ApplicationServerManager.java:59)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)

Tue Jun 29 10:53:47 PDT 2010 org.eclipse.osee.framework.database.internal.Activator
SEVERE org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (155)
This is the nested exception
org.postgresql.util.PSQLException: ERROR: relation "osee_server_lookup" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorRespons e(QueryExecutorImpl.java:1608)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer yExecutorImpl.java:1343)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut orImpl.java:343)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(Abs tractJdbc2Statement.java:2668)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:14 8)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.runBatchUpdate(OseeDatabaseServiceImpl.java:16 9)
at org.eclipse.osee.framework.database.core.ConnectionHandler.r unBatchUpdate(ConnectionHandler.java:85)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore.registerWithDb(ApplicationServerDataStore.jav a:94)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.writeToDataStore(InternalOseeServerInfo.java:115)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateRegistration(InternalOseeServerInfo.java:12 2)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager.executeLookupRegistration(ApplicationServerMana ger.java:90)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1.run(ApplicationServerManager.java:59)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)

Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #543547 is a reply to message #537706] Tue, 29 June 2010 18:01 Go to previous messageGo to next message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
then I try to Initialize the database
Initialization script is is from the documentation :

../eclipse/eclipse -nosplash -application org.eclipse.osee.framework.database.init.configClient -console -vmargs -XX:MaxPermSize=256m -Xmx512m -Dosee.application.server=http://127.0.0.1:8089

Yet It seems as if its trying to start another server instance......
and I get the following:


osgi> 2010-06-29 10:54:42.247::WARN: failed SelectChannelConnector@0.0.0.0:80
java.net.SocketException: Permission denied
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI mpl.java:137)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java :77)
at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChan nelConnector.java:216)
at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectC hannelConnector.java:315)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy cle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:233)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy cle.java:50)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager.up dated(HttpServerManager.java:109)
at org.eclipse.equinox.http.jetty.internal.Activator.start(Acti vator.java:60)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1 .run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:774)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:352)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:370)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1068)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:464)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:248)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:445)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
2010-06-29 10:54:42.248::WARN: failed Server@11dba45
java.net.SocketException: Permission denied
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI mpl.java:137)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java :77)
at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChan nelConnector.java:216)
at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectC hannelConnector.java:315)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy cle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:233)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy cle.java:50)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager.up dated(HttpServerManager.java:109)
at org.eclipse.equinox.http.jetty.internal.Activator.start(Acti vator.java:60)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1 .run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:774)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:352)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:370)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1068)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:464)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:248)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:445)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
Registered servlet '/osee/manager'
Registered servlet '/osee/resource'
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/index'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/branch'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Registered servlet '/osee/install/info'
Registered servlet '/osee/cache'
Registered servlet '/osee/model'
Registered servlet '/osee/unsubscribe'
Registered servlet '/osee/ats'
Tue Jun 29 10:54:47 PDT 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
SEVERE org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1 run (61)
No DB connection information provided
java.lang.IllegalStateException: No DB connection information provided
at org.eclipse.osee.framework.database.internal.DbConnectionInf ormation.getSelectedDatabaseInfo(DbConnectionInformation.jav a:62)
at org.eclipse.osee.framework.database.core.DatabaseInfoManager .getDefault(DatabaseInfoManager.java:31)
at org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider.getDatabaseInfo(ServerDatabaseProvider.java:31)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.getDatabaseInfoProvider(OseeDatabaseServiceImp l.java:47)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.getDefaultConnectionPool(OseeDatabaseServiceIm pl.java:51)
at org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl.getStatement(OseeDatabaseServiceImpl.java:86)
at org.eclipse.osee.framework.database.core.ConnectionHandler.g etStatement(ConnectionHandler.java:53)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore.getOseeVersionsByServerId(ApplicationServerDa taStore.java:186)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateVersionsFromDataStore(InternalOseeServerInf o.java:62)
at org.eclipse.osee.framework.core.server.internal.InternalOsee ServerInfo.updateRegistration(InternalOseeServerInfo.java:12 0)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager.executeLookupRegistration(ApplicationServerMana ger.java:90)
at org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager$1.run(ApplicationServerManager.java:59)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)

[Updated on: Tue, 29 June 2010 18:03]

Report message to a moderator

Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #544495 is a reply to message #543547] Fri, 02 July 2010 21:49 Go to previous message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
Dear Al,

Because of the issues that you and other Linux users have been experiencing, I decided to do a test using my home computer which runs Mandriva 2010.

Please verify the steps you have been through against the following, which I have verified works up to the point of successfully creating a demo database.

Install Eclipse 3.5.2
Download the 0.9.4 client from the OSEE downloads page
Choose it as an archive in the Eclipse update manager and install it
This will install the OSEE client and everything else it needs EXCEPT the PostgreSQL driver
Download the PostgreSQL driver from the OSEE downloads page
Choose it as an archive in the Eclipse update manager and install it

Download the 0.9.4 server from the OSEE downloads page and unzip it
Unzip the PostgreSQL driver
Copy the two files from the plugins folder in the PostgreSQL driver to the plugins folder of the server

Create an empty PostgreSQL database per the instructions on the OSEE web site
Start the application server, ignoring any messages about tables not existing

In the directory containing your OSEE eclipse, execute the following:

eclipse -application org.eclipse.osee.framework.database.init.configClient -vmargs -Xmx512m -Dosee.log.default=INFO -Dosee.application.server=http://localhost:8089 -Dosee.authentication.protocol=trustAll -Dosee.prompt.on.db.init=false -Dosee.choice.on.db.init="OSEE Demo Database"

This is proven to create a functional demo database under both Windows and Linux (tested on Mandriva 2010)

I have not yet connected an OSEE client to this database under Linux, but this is the output you should then get on next starting the server:

[mark@quiet org.eclipse.osee.server_postgresql_0.9.4_incubation]$ ./runPostgresqlLocal.sh

osgi> Fri Jul 02 22:47:53 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler addServerTask (41)
Adding task: Clean up join tables

Fri Jul 02 22:47:53 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties getOseeApplicationServerData (69)
Application Server Data: [/home/mark]

Registered servlet '/osee/manager'
Registered servlet '/osee/resource'
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/index'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/branch'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Registered servlet '/osee/install/info'
Registered servlet '/osee/cache'
Registered servlet '/osee/model'
Registered servlet '/osee/unsubscribe'
Registered servlet '/osee/ats'
Fri Jul 02 22:47:56 BST 2010 org.eclipse.osee.framework.search.engine.internal.SearchEngi neTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable run (42)
Tagging on Server Startup was not run.

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.database.internal.Activator
INFO org.eclipse.osee.framework.database.internal.core.OseeConnec tionPoolImpl getConnection (77)
DbConnection: [jdbc:postgresql://localhost:5432/OSEE] - [1]

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.database.internal.Activator
INFO org.eclipse.osee.framework.database.internal.core.OseeConnec tionPoolImpl getConnection (77)
DbConnection: [jdbc:postgresql://localhost:5432/OSEE] - [2]

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager executeLookupRegistration (92)
Application Server: [f694be1eb779113f05692b171146a61d] registered.


All the best,

Mark
Re: Ubuntu Postgresql. OSEE Server Not starting? [message #576850 is a reply to message #537821] Fri, 04 June 2010 16:57 Go to previous message
al  is currently offline al
Messages: 22
Registered: June 2010
Junior Member
I'm compressing the Virtual Machine into a rar file.
Is there anyone out there that has an FTP site I can put it on so someone can look into this?
Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #577019 is a reply to message #543547] Fri, 02 July 2010 21:49 Go to previous message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
Dear Al,

Because of the issues that you and other Linux users have been experiencing, I decided to do a test using my home computer which runs Mandriva 2010.

Please verify the steps you have been through against the following, which I have verified works up to the point of successfully creating a demo database.

Install Eclipse 3.5.2
Download the 0.9.4 client from the OSEE downloads page
Choose it as an archive in the Eclipse update manager and install it
This will install the OSEE client and everything else it needs EXCEPT the PostgreSQL driver
Download the PostgreSQL driver from the OSEE downloads page
Choose it as an archive in the Eclipse update manager and install it

Download the 0.9.4 server from the OSEE downloads page and unzip it
Unzip the PostgreSQL driver
Copy the two files from the plugins folder in the PostgreSQL driver to the plugins folder of the server

Create an empty PostgreSQL database per the instructions on the OSEE web site
Start the application server, ignoring any messages about tables not existing

In the directory containing your OSEE eclipse, execute the following:

eclipse -application org.eclipse.osee.framework.database.init.configClient -vmargs -Xmx512m -Dosee.log.default=INFO -Dosee.application.server=http://localhost:8089 -Dosee.authentication.protocol=trustAll -Dosee.prompt.on.db.init=false -Dosee.choice.on.db.init="OSEE Demo Database"

This is proven to create a functional demo database under both Windows and Linux (tested on Mandriva 2010)

I have not yet connected an OSEE client to this database under Linux, but this is the output you should then get on next starting the server:

[mailto:mark@quiet org.eclipse.osee.server_postgresql_0.9.4_incubation]$ ./runPostgresqlLocal.sh

osgi> Fri Jul 02 22:47:53 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler addServerTask (41)
Adding task: Clean up join tables

Fri Jul 02 22:47:53 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties getOseeApplicationServerData (69)
Application Server Data: [/home/mark]

Registered servlet '/osee/manager'
Registered servlet '/osee/resource'
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/index'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/branch'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Registered servlet '/osee/install/info'
Registered servlet '/osee/cache'
Registered servlet '/osee/model'
Registered servlet '/osee/unsubscribe'
Registered servlet '/osee/ats'
Fri Jul 02 22:47:56 BST 2010 org.eclipse.osee.framework.search.engine.internal.SearchEngi neTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable run (42)
Tagging on Server Startup was not run.

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.database.internal.Activator
INFO org.eclipse.osee.framework.database.internal.core.OseeConnec tionPoolImpl getConnection (77)
DbConnection: [jdbc:postgresql://localhost:5432/OSEE] - [1]

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.database.internal.Activator
INFO org.eclipse.osee.framework.database.internal.core.OseeConnec tionPoolImpl getConnection (77)
DbConnection: [jdbc:postgresql://localhost:5432/OSEE] - [2]

Fri Jul 02 22:47:58 BST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager executeLookupRegistration (92)
Application Server: [f694be1eb779113f05692b171146a61d] registered.


All the best,

Mark
Previous Topic:OSEE 0.9.4 Installation
Next Topic:Application server starts with errors
Goto Forum:
  


Current Time: Sat Sep 20 08:12:27 GMT 2014

Powered by FUDForum. Page generated in 0.14046 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software