|
Re: Getting client/server running - worked for me [message #15437 is a reply to message #15304] |
Thu, 21 May 2009 21:27   |
Ray Joseph Messages: 87 Registered: July 2009 |
Member |
|
|
Mark,
Thank you very much for the effort to post the process. With your help, I
found many holes in my attempts. But I still am not running. I have
tried it on three different machines.
The process hangs after entering the script at the app_server directory.
The transaction looks like:
C:\osee\app_server_0.7.0>java -Dosee.log.default=INFO -Dorg.osgi.service.http.p
rt=8089 -Dosgi.compatibility.bootdelegation=true -Xmx512m
-Dequinox.ds.debug=t
ue -Dosee.connection.info.uri="C:\osee\app_server_0.7.0\connection.xml "
-Dosee.
b.connection.id=OSEE -jar org.eclipse.osgi_3.4.0.v20080326.jar -console
osgi> May 21, 2009 9:58:40 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1394894
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
May 21, 2009 9:58:40 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@134a7d8
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.UriDbConnect ionInfo
geDbInformation (36)
Loading connection info from: [C:\osee\app_server_0.7.0\connection.xml]
Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @6f7d2
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler
adServerTask (41)
Adding task: Clean up join tables
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeAppicationServerData (54)
Application Server Data: [C:\Documents and Settings\rjoseph]
Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Registered servlet '/osee/resource'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Thu May 21 09:58:43 CDT 2009
org.eclipse.osee.framework.search.engine.intenal.SearchEngin eTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable
run45)
Tagging on Server Startup was not run.
Thu May 21 09:59:00 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
deregisterWithDb (63)
Server lookup table not initialized
Thu May 21 09:59:20 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
registerWithDb (80)
Server lookup table not initialized
_______________
It hangs at this point.
the PG_log has no entries during this time.
It looks like there is a problem registering with the Db. I assume this
is the PostgreSQL. Any suggestions on how to move forward?
Addditionally, I already have SVN and TSVN running on all the machines
that I have tried to run osee. Is there a possibility that there is a
clash here? When I close the command window where the script hangs, the
Windows Task Manager shows that the postgres.exe process runs for a short
duration and then stops. I guess this means that the closure is
interacting with PostgreSQL. The pg log does not show any activity during
the osee process.
Thanks,
Ray
|
|
|
|
|
|
Re: Getting client/server running - worked for me [message #573942 is a reply to message #15304] |
Thu, 21 May 2009 21:27  |
Ray Joseph Messages: 87 Registered: July 2009 |
Member |
|
|
Mark,
Thank you very much for the effort to post the process. With your help, I
found many holes in my attempts. But I still am not running. I have
tried it on three different machines.
The process hangs after entering the script at the app_server directory.
The transaction looks like:
C:\osee\app_server_0.7.0>java -Dosee.log.default=INFO -Dorg.osgi.service.http.p
rt=8089 -Dosgi.compatibility.bootdelegation=true -Xmx512m
-Dequinox.ds.debug=t
ue -Dosee.connection.info.uri="C:\osee\app_server_0.7.0\connection.xml "
-Dosee.
b.connection.id=OSEE -jar org.eclipse.osgi_3.4.0.v20080326.jar -console
osgi> May 21, 2009 9:58:40 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1394894
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
May 21, 2009 9:58:40 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@134a7d8
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.UriDbConnect ionInfo
geDbInformation (36)
Loading connection info from: [C:\osee\app_server_0.7.0\connection.xml]
Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @6f7d2
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler
adServerTask (41)
Adding task: Clean up join tables
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeAppicationServerData (54)
Application Server Data: [C:\Documents and Settings\rjoseph]
Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Registered servlet '/osee/resource'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Thu May 21 09:58:43 CDT 2009
org.eclipse.osee.framework.search.engine.intenal.SearchEngin eTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable
run45)
Tagging on Server Startup was not run.
Thu May 21 09:59:00 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
deregisterWithDb (63)
Server lookup table not initialized
Thu May 21 09:59:20 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
registerWithDb (80)
Server lookup table not initialized
_______________
It hangs at this point.
the PG_log has no entries during this time.
It looks like there is a problem registering with the Db. I assume this
is the PostgreSQL. Any suggestions on how to move forward?
Addditionally, I already have SVN and TSVN running on all the machines
that I have tried to run osee. Is there a possibility that there is a
clash here? When I close the command window where the script hangs, the
Windows Task Manager shows that the postgres.exe process runs for a short
duration and then stops. I guess this means that the closure is
interacting with PostgreSQL. The pg log does not show any activity during
the osee process.
Thanks,
Ray
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02473 seconds