Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » OSEE » Ubuntu Postgresql. OSEE Server Not starting?
Ubuntu Postgresql. OSEE Server Not starting? [message #576818] Thu, 03 June 2010 08:28 Go to next message
Eclipse UserFriend
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) Console output from server statup
3) Server Log file


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

Console output from server statup:
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 mailto: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 mailto: org.eclipse.osee.framework.database.internal.UriDbConnection Info @1f1235b

Adding: mailto: 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/mailto: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
Re: Ubuntu Postgresql. OSEE Server Not starting? [message #576837 is a reply to message #576818] Thu, 03 June 2010 14:04 Go to previous messageGo to next message
Eclipse UserFriend
Wow, simular!
http://www.eclipse.org/forums/index.php?t=msg&th=168493& amp;start=0&
Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #576865 is a reply to message #576818] Mon, 07 June 2010 05:08 Go to previous messageGo to next message
Eclipse UserFriend
This may not be the whole probelm, 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.
Re: Ubuntu (Unix) Postgresql. OSEE Server Not starting? [message #576928 is a reply to message #576865] Tue, 29 June 2010 13:07 Go to previous messageGo to next message
Eclipse UserFriend
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 #576942 is a reply to message #576818] Tue, 29 June 2010 14:00 Go to previous messageGo to next message
Eclipse UserFriend
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 #576969 is a reply to message #576818] Tue, 29 June 2010 14:01 Go to previous message
Eclipse UserFriend
then I try to Initialize the database and I get the following:
osgi> 2010-06-29 10:54:42.247::WARN: failed mailto: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 mailto: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)
Previous Topic:OSEE 0.9.1
Next Topic:OSEE 0.9.4 Installation
Goto Forum:
  


Current Time: Tue Jul 08 00:29:53 EDT 2025

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly