Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » OSEE » Application server starts with errors
Application server starts with errors [message #534670] Wed, 19 May 2010 19:41 Go to next message
Michael Bodenbach is currently offline Michael BodenbachFriend
Messages: 19
Registered: May 2010
Junior Member
Hello,

i tried to start the application server (oseeAppServer_postgres_0.9.1)
with the following :

java -Dosee.log.default=INFO -Declipse.ignoreApp=true -Dorg.osgi.service.http.port=8089 -Dosgi.compatibility.bootdelegation=true -Xms40m -Xmx512m -Dosee.db.cid=postgresqlLocalhost -Dosee.application.server.data=/home/michael/Eclipse/osee_da ta -Dequinox.ds.debug=true -jar org.eclipse.osgi.jar -console

Then i got the following console output:

osgi> Wed May 19 21:30:51 CEST 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@67071c84

Wed May 19 21:30:51 CEST 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.parser.DbConfig Parser getAllDbServices (50)
in getAllDbServices 3

Wed May 19 21:30:51 CEST 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

Wed May 19 21:30:51 CEST 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

Wed May 19 21:30:51 CEST 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

Wed May 19 21:30:51 CEST 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 @44ea5461

Adding: org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @37b994de
Wed May 19 21:30:51 CEST 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

Wed May 19 21:30:52 CEST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties getOseeApplicationServerData (69)
Application Server Data: [/home/michael/Eclipse/osee_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'
Wed May 19 21:30:54 CEST 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

Wed May 19 21:30:54 CEST 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
SCHWERWIEGEND org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (158)
This is the nested exception
org.postgresql.util.PSQLException: FEHLER: Relation »osee_server_lookup« existiert nicht
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)

Wed May 19 21:30:54 CEST 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

Wed May 19 21:30:54 CEST 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
SCHWERWIEGEND org.eclipse.osee.framework.database.internal.core.OseeDataba seServiceImpl runBatchUpdate (158)
This is the nested exception
org.postgresql.util.PSQLException: FEHLER: Relation »osee_server_lookup« existiert nicht
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)

Wed May 19 21:30:54 CEST 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

Wed May 19 21:30:56 CEST 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.



With that it is not possible to initialize the database.

I have configured the postgresql database like describes in the "Getting Stated" guide.

Any ideas?

Best regards,

Michael
Re: Application server starts with errors [message #534909 is a reply to message #534670] Thu, 20 May 2010 15:44 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Hello Michael.

Did you try running the database initialisation script after the point you have shown?
Whilst you have had exceptions, it looks like the application server has reached the point where it may still be able to accept a connection and initialise the tables, which would then remove the exceptions the next time it is started.

All the best,

Mark
Re: Application server starts with errors [message #535228 is a reply to message #534909] Fri, 21 May 2010 16:28 Go to previous messageGo to next message
Michael Bodenbach is currently offline Michael BodenbachFriend
Messages: 19
Registered: May 2010
Junior Member
Hello Mark.

Yes - i've tried.

I used:

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

An got:

osgi> Adding: org.eclipse.osee.framework.core.client.internal.ClientDataba seProvider @151ff451
OSEE Application Server Validation [PASSED]
Removing: org.eclipse.osee.framework.core.client.internal.ClientDataba seProvider @151ff451



And o nthe server side:

Fri May 21 18:20:08 CEST 2010 org.eclipse.osee.framework.manager.servlet.MasterServletActi vator
SCHWERWIEGEND org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet doPost (95)
Error processing session request [ org.eclipse.equinox.http.servlet.internal.HttpServletRequest Adaptor @7041a12f]
org.eclipse.osee.framework.core.exception.OseeWrappedExcepti on:
at org.eclipse.osee.framework.core.data.BaseExchangeData.loadfr omXml(BaseExchangeData.java:45)
at org.eclipse.osee.framework.core.data.OseeCredential.fromXml( OseeCredential.java:70)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.createSession(SessionManagementServlet.java:111)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)
Caused by: java.lang.IllegalStateException: Method getLocalName() cannot be called for START_DOCUMENT event.
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl. getLocalName(XMLStreamReaderImpl.java:330)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter $XMLReader.process(PropertyStoreWriter.java:158)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter $XMLReader.load(PropertyStoreWriter.java:147)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter .load(PropertyStoreWriter.java:48)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter .load(PropertyStoreWriter.java:52)
at org.eclipse.osee.framework.core.data.BaseExchangeData.loadfr omXml(BaseExchangeData.java:43)
... 24 more

2010-05-21 18:20:08.307::WARN: ERROR: /osee/session
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:595)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)



Michael

Re: Application server starts with errors [message #535238 is a reply to message #535228] Fri, 21 May 2010 17:07 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Hello Michael,

You appear to now be getting the same error as Kumar in this thread: http://www.eclipse.org/forums/index.php?t=msg&th=162878& amp;start=0&

I am wondering whether this could be due to some internationalisation issue. I am suspecting (no evidence to back this up) that Kumar may have some non-English settings in Windows and I see that you are configured in such a way that some of the error messages are in German.

Nirmal and I don't get the problem, so this is not a general OSEE issue, it is something down to individual installations.

All the best,

Mark
Re: Application server starts with errors [message #535879 is a reply to message #535238] Wed, 26 May 2010 07:55 Go to previous messageGo to next message
Michael Bodenbach is currently offline Michael BodenbachFriend
Messages: 19
Registered: May 2010
Junior Member
Hello Mark,

i have setup a new system in a virtual machine (Virtual Box) and install a new System with "Great Britain" regional settings. Bit the problem remains. Any other ideas?
When i have more time i will try to check out and build the server on my machine.

My installed system was not a Wondows. I use Kubuntu 10.04LTS on an AMD 64bit.
Could this be a problem?

Michael
Re: Application server starts with errors [message #539946 is a reply to message #535879] Mon, 14 June 2010 11:16 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Dear Michael,

OSEE 0.9.4 is now available. Because the database is not compatible with 0.9.1, I have needed to initialise a 0.9.4 database to allow import.

When the app server is started and before the init has bee run, repeated exceptions of the following form occur. This is normal because the database has no tables in it yet:

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

I then ran the init (option 1, to allow a test to be done on the client before using option 0 to import my real database). At the end of the init, on the server side, the following two exceptions were reported. However, stopping and restarting the application server yielded a functioning OSEE.

SEVERE org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet doPost (96)
Error processing session request [ org.eclipse.equinox.http.servlet.internal.HttpServletRequest Adaptor @1015495]
org.eclipse.osee.framework.core.exception.OseeInvalidAuthent icationProtocolException: Invalid protocol []
at org.eclipse.osee.framework.core.server.internal.Authenticati onManager.authenticate(AuthenticationManager.java:56)
at org.eclipse.osee.framework.core.server.internal.SessionManag er.createSession(SessionManager.java:144)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.createSession(SessionManagementServlet.java:113)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)

2010-06-14 12:12:57.703::WARN: ERROR: /osee/session
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:595)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)

I suggest you try downloading 0.9.4 to see whether you are then able to run.

All the best,

Mark
Re: Application server starts with errors [message #544496 is a reply to message #534670] Fri, 02 July 2010 21:51 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Dear Michael,

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 confirmed 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: Application server starts with errors [message #576715 is a reply to message #534670] Thu, 20 May 2010 15:44 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Hello Michael.

Did you try running the database initialisation script after the point you have shown?
Whilst you have had exceptions, it looks like the application server has reached the point where it may still be able to accept a connection and initialise the tables, which would then remove the exceptions the next time it is started.

All the best,

Mark
Re: Application server starts with errors [message #576740 is a reply to message #534909] Fri, 21 May 2010 16:28 Go to previous messageGo to next message
Michael Bodenbach is currently offline Michael BodenbachFriend
Messages: 19
Registered: May 2010
Junior Member
Hello Mark.

Yes - i've tried.

I used:

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

An got:

osgi> Adding: mailto: org.eclipse.osee.framework.core.client.internal.ClientDataba seProvider @151ff451
OSEE Application Server Validation [PASSED]
Removing: mailto: org.eclipse.osee.framework.core.client.internal.ClientDataba seProvider @151ff451



And o nthe server side:

Fri May 21 18:20:08 CEST 2010 org.eclipse.osee.framework.manager.servlet.MasterServletActi vator
SCHWERWIEGEND org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet doPost (95)
Error processing session request [mailto: org.eclipse.equinox.http.servlet.internal.HttpServletRequest Adaptor @7041a12f]
org.eclipse.osee.framework.core.exception.OseeWrappedExcepti on:
at org.eclipse.osee.framework.core.data.BaseExchangeData.loadfr omXml(BaseExchangeData.java:45)
at org.eclipse.osee.framework.core.data.OseeCredential.fromXml( OseeCredential.java:70)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.createSession(SessionManagementServlet.java:111)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)
Caused by: java.lang.IllegalStateException: Method getLocalName() cannot be called for START_DOCUMENT event.
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl. getLocalName(XMLStreamReaderImpl.java:330)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter $XMLReader.process(PropertyStoreWriter.java:158)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter $XMLReader.load(PropertyStoreWriter.java:147)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter .load(PropertyStoreWriter.java:48)
at org.eclipse.osee.framework.jdk.core.type.PropertyStoreWriter .load(PropertyStoreWriter.java:52)
at org.eclipse.osee.framework.core.data.BaseExchangeData.loadfr omXml(BaseExchangeData.java:43)
... 24 more

2010-05-21 18:20:08.307::WARN: ERROR: /osee/session
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:595)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)



Michael
Re: Application server starts with errors [message #576753 is a reply to message #535228] Fri, 21 May 2010 17:07 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Hello Michael,

You appear to now be getting the same error as Kumar in this thread: http://www.eclipse.org/forums/index.php?t=msg&th=162878& amp;start=0&

I am wondering whether this could be due to some internationalisation issue. I am suspecting (no evidence to back this up) that Kumar may have some non-English settings in Windows and I see that you are configured in such a way that some of the error messages are in German.

Nirmal and I don't get the problem, so this is not a general OSEE issue, it is something down to individual installations.

All the best,

Mark
Re: Application server starts with errors [message #576783 is a reply to message #576753] Wed, 26 May 2010 07:55 Go to previous messageGo to next message
Michael Bodenbach is currently offline Michael BodenbachFriend
Messages: 19
Registered: May 2010
Junior Member
Hello Mark,

i have setup a new system in a virtual machine (Virtual Box) and install a new System with "Great Britain" regional settings. Bit the problem remains. Any other ideas?
When i have more time i will try to check out and build the server on my machine.

My installed system was not a Wondows. I use Kubuntu 10.04LTS on an AMD 64bit.
Could this be a problem?

Michael
Re: Application server starts with errors [message #576890 is a reply to message #576783] Mon, 14 June 2010 11:16 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Dear Michael,

OSEE 0.9.4 is now available. Because the database is not compatible with 0.9.1, I have needed to initialise a 0.9.4 database to allow import.

When the app server is started and before the init has bee run, repeated exceptions of the following form occur. This is normal because the database has no tables in it yet:

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

I then ran the init (option 1, to allow a test to be done on the client before using option 0 to import my real database). At the end of the init, on the server side, the following two exceptions were reported. However, stopping and restarting the application server yielded a functioning OSEE.

SEVERE org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet doPost (96)
Error processing session request [mailto: org.eclipse.equinox.http.servlet.internal.HttpServletRequest Adaptor @1015495]
org.eclipse.osee.framework.core.exception.OseeInvalidAuthent icationProtocolException: Invalid protocol []
at org.eclipse.osee.framework.core.server.internal.Authenticati onManager.authenticate(AuthenticationManager.java:56)
at org.eclipse.osee.framework.core.server.internal.SessionManag er.createSession(SessionManager.java:144)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.createSession(SessionManagementServlet.java:113)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)

2010-06-14 12:12:57.703::WARN: ERROR: /osee/session
java.lang.IllegalStateException: STREAM
at org.mortbay.jetty.Response.getWriter(Response.java:595)
at org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet.doPost(SessionManagementServlet.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.osee.framework.core.server.internal.InternalOsee HttpServlet.service(InternalOseeHttpServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520)

I suggest you try downloading 0.9.4 to see whether you are then able to run.

All the best,

Mark
Re: Application server starts with errors [message #577028 is a reply to message #534670] Fri, 02 July 2010 21:51 Go to previous message
Mark D-B is currently offline Mark D-BFriend
Messages: 188
Registered: July 2009
Senior Member
Dear Michael,

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 confirmed 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:Ubuntu (Unix) Postgresql. OSEE Server Not starting?
Next Topic:Attention Linux users - 0.9.4 is proven to work under Mandriva 2010
Goto Forum:
  


Current Time: Wed Nov 26 11:54:17 GMT 2014

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

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