Eclipse Community Forums: OSEE

Home » Eclipse Projects » OSEE » OSEE 0.9.1(Unable to establish Client Communication with OSEE Server)

Thu, 18 February 2010 06:00

Eclipse User

Hi,

I have been able to successfully configure and run the OSEE client and server 0.7.1 and have been trying to integrate the components for OSEE 0.9.1.

The existing setup with 0.7.1 already has a postgresql data base configured for OSEE and initialised.

I have downloaded all the packages required for OSEE 0.9.1 and have launched the server, but i do not see the server getting any connection pool size from the database.

When i launch the client the following errors occur:
1. Reason: http://xyz:8089/osee/session?operation=create

http://xyz:8089/osee/session?operation=create
http://xyz:8089/osee/session?operation=create
Error during POST - status code:
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:216)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticate(InternalClientSessionManager.j ava:111)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticateAsGuest(InternalClientSessionMa nager.java:103)
org.eclipse.osee.framework.core.client.ClientSessionManager. authenticateAsGuest(ClientSessionManager.java:99)
org.eclipse.osee.framework.skynet.core.ClientUser.executeGue stLogin(ClientUser.java:105)
org.eclipse.osee.framework.skynet.core.ClientUser.populateCu rrentUser(ClientUser.java:82)
org.eclipse.osee.framework.skynet.core.ClientUser.getMainUse r(ClientUser.java:50)
org.eclipse.osee.framework.skynet.core.UserManager.getUser(U serManager.java:63)
org.eclipse.osee.framework.skynet.core.OseeGroup.isCurrentUs erMember(OseeGroup.java:75)
org.eclipse.osee.framework.skynet.core.SystemGroup.isCurrent UserMember(SystemGroup.java:42)
org.eclipse.osee.framework.skynet.core.access.AccessControlM anager.isOseeAdmin(AccessControlManager.java:609)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.isAdm in(ArtifactDecorator.java:108)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.check ActionsCreated(ArtifactDecorator.java:92)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.addAc tions(ArtifactDecorator.java:119)
org.eclipse.osee.framework.ui.skynet.ArtifactExplorer.create PartControl(ArtifactExplorer.java:336)
org.eclipse.ui.internal.ViewReference.createPartHelper(ViewR eference.java:367)
org.eclipse.ui.internal.ViewReference.createPart(ViewReferen ce.java:226)
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:595)
org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActi ve(WorkbenchPage.java:4212)
org.eclipse.ui.internal.WorkbenchPage$18.runWithException(Wo rkbenchPage.java:3271)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:803)
org.eclipse.ui.internal.Workbench$28.runWithException(Workbe nch.java:1384)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
org.eclipse.equinox.launcher.Main.run(Main.java:1311)
caused by
Error during POST - status code: [200]
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:163)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:211)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticate(InternalClientSessionManager.j ava:111)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticateAsGuest(InternalClientSessionMa nager.java:103)
org.eclipse.osee.framework.core.client.ClientSessionManager. authenticateAsGuest(ClientSessionManager.java:99)
org.eclipse.osee.framework.skynet.core.ClientUser.executeGue stLogin(ClientUser.java:105)
org.eclipse.osee.framework.skynet.core.ClientUser.populateCu rrentUser(ClientUser.java:82)
org.eclipse.osee.framework.skynet.core.ClientUser.getMainUse r(ClientUser.java:50)
org.eclipse.osee.framework.skynet.core.UserManager.getUser(U serManager.java:63)
org.eclipse.osee.framework.skynet.core.OseeGroup.isCurrentUs erMember(OseeGroup.java:75)
org.eclipse.osee.framework.skynet.core.SystemGroup.isCurrent UserMember(SystemGroup.java:42)
org.eclipse.osee.framework.skynet.core.access.AccessControlM anager.isOseeAdmin(AccessControlManager.java:609)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.isAdm in(ArtifactDecorator.java:108)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.check ActionsCreated(ArtifactDecorator.java:92)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.addAc tions(ArtifactDecorator.java:119)
org.eclipse.osee.framework.ui.skynet.ArtifactExplorer.create PartControl(ArtifactExplorer.java:336)
org.eclipse.ui.internal.ViewReference.createPartHelper(ViewR eference.java:367)
org.eclipse.ui.internal.ViewReference.createPart(ViewReferen ce.java:226)
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:595)
org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActi ve(WorkbenchPage.java:4212)
org.eclipse.ui.internal.WorkbenchPage$18.runWithException(Wo rkbenchPage.java:3271)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:803)
org.eclipse.ui.internal.Workbench$28.runWithException(Workbe nch.java:1384)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
org.eclipse.equinox.launcher.Main.run(Main.java:1311)
caused by

org.eclipse.osee.framework.jdk.core.util.HttpProcessor.getCo ntentType(HttpProcessor.java:218)
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:154)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:211)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticate(InternalClientSessionManager.j ava:111)
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticateAsGuest(InternalClientSessionMa nager.java:103)
org.eclipse.osee.framework.core.client.ClientSessionManager. authenticateAsGuest(ClientSessionManager.java:99)
org.eclipse.osee.framework.skynet.core.ClientUser.executeGue stLogin(ClientUser.java:105)
org.eclipse.osee.framework.skynet.core.ClientUser.populateCu rrentUser(ClientUser.java:82)
org.eclipse.osee.framework.skynet.core.ClientUser.getMainUse r(ClientUser.java:50)
org.eclipse.osee.framework.skynet.core.UserManager.getUser(U serManager.java:63)
org.eclipse.osee.framework.skynet.core.OseeGroup.isCurrentUs erMember(OseeGroup.java:75)
org.eclipse.osee.framework.skynet.core.SystemGroup.isCurrent UserMember(SystemGroup.java:42)
org.eclipse.osee.framework.skynet.core.access.AccessControlM anager.isOseeAdmin(AccessControlManager.java:609)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.isAdm in(ArtifactDecorator.java:108)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.check ActionsCreated(ArtifactDecorator.java:92)
org.eclipse.osee.framework.ui.skynet.ArtifactDecorator.addAc tions(ArtifactDecorator.java:119)
org.eclipse.osee.framework.ui.skynet.ArtifactExplorer.create PartControl(ArtifactExplorer.java:336)
org.eclipse.ui.internal.ViewReference.createPartHelper(ViewR eference.java:367)
org.eclipse.ui.internal.ViewReference.createPart(ViewReferen ce.java:226)
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:595)
org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActi ve(WorkbenchPage.java:4212)
org.eclipse.ui.internal.WorkbenchPage$18.runWithException(Wo rkbenchPage.java:3271)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:803)
org.eclipse.ui.internal.Workbench$28.runWithException(Workbe nch.java:1384)
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:134)
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3855)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3476)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
org.eclipse.equinox.launcher.Main.run(Main.java:1311)

2. Problem Occured:
OTE Bulk load persistence has encountered problems
http://xyz:8089/osee/session?operation=create
Error during POST [http://xyz:8089/osee/session?

3. OSEE Error:
Seesion is invalid authentication required.

Please let me know if i have missed out any steps in setting up the client or server.

Re: OSEE 0.9.1 [message #516554 is a reply to message #515282]

Wed, 24 February 2010 06:55

Eclipse User

Hi Kumar,

There are some changes to the database organisation between 0.7 and 0.9. This means that you cannot just take a 0.7 database and use the 0.9 application server with it.

It is not clear to me from your post whether you have just a test database initialised for 0.7 or if you have real data you want to migrate.

If the former, the best thing will be to just re-initialise the database using the 0.9 application server.

If the latter, there are a number of steps that you will need to go through. We can get into the detail later if this is what you need to do.

All the best,

Mark

Re: OSEE 0.9.1 [message #516803 is a reply to message #515282]

Thu, 25 February 2010 04:03

Eclipse User

Hello Mark,

Thank you for the repsonse. I have been working on the test database of 0.7 version. As suggested by you I have tried re-initialising the test data base with
eclipse -nosplash -application
org.eclipse.osee.framework.database.configClient -console -vmargs
-XX:MaxPermSize=256m -Xmx512m

but got and errror
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "org.eclipse.osee.framework.database.configClient" could not be found in the registry.

Probably the configClient was meant for 0.7 version only...

I also tried using:
eclipse -nosplash -application org.eclipse.osee.framework.database.init.configClient -console -vmargs -XX:MaxPe
rmSize=256m -Xmx512m -Dosee.application.server=http://localhost:8089 -Dosee.authentication.protocol=trustAll

this step passes the OSEE Application Server Validation [PASSED]

but i got the following error log:
Exception: http://localhost:8089/osee/session?operation=create

eclipse.buildId=M20090917-0800
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application org.eclipse.osee.framework.database.init.configClient
Command-line arguments: -os win32 -ws win32 -arch x86 -application org.eclipse.osee.framework.database.init.configClient -console

!ENTRY org.eclipse.osgi 4 0 2010-02-25 13:22:14.756
!MESSAGE Application error
!STACK 1
org.eclipse.osee.framework.core.exception.OseeAuthentication Exception: http://localhost:8089/osee/session?operation=create
at org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:216)
at org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.authenticate(InternalClientSessionManager.j ava:111)
at org.eclipse.osee.framework.core.client.ClientSessionManager. authenticate(ClientSessionManager.java:103)
at org.eclipse.osee.framework.database.init.DatabaseInitializat ionOperation.execute(DatabaseInitializationOperation.java:64 )
at org.eclipse.osee.framework.database.init.DatabaseInitializat ionOperation.executeConfigureFromJvmProperties(DatabaseIniti alizationOperation.java:289)
at org.eclipse.osee.framework.database.init.ConfigDatabase.star t(ConfigDatabase.java:19)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: java.io.IOException: Error during POST [http://localhost:8089/osee/session?operation=create] - status code: [200]
at org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:163)
at org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:211)
... 17 more
Caused by: java.lang.NullPointerException
at org.eclipse.osee.framework.jdk.core.util.HttpProcessor.getCo ntentType(HttpProcessor.java:218)
at org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:154)
... 18 more

I have a postgresql database running on the windows machine and all the 3 database, client and server are on the same machine. I am aslo using a connection.xml to specify the postgresql database connection.

Please let me know if I am using the right command to re-intialize the database.

Best regards,
Kumar

Re: OSEE 0.9.1 [message #516927 is a reply to message #516554]

Thu, 25 February 2010 09:23

Eclipse User

Hi Kumar,

The command for initialisation has changed and I updated the FAQ ( http://wiki.eclipse.org/OSEE/Users_Guide/Getting_Started#Dat abase_Initialization) a few weeks ago to indicate that.

You worked out correctly the command that needs to be used for 0.9 so I suspect that isn't the reason for your error. It may be worth trying the command without the trustAll element so that you are exactly replicating what I know normally works just in case that causes a problem.

What does the application server window show when you get the error please?

All the best,

Mark

Re: OSEE 0.9.1 [message #517079 is a reply to message #515282]

Fri, 26 February 2010 01:36

Eclipse User

Hello Mark,

As suggested by you i tried the initialisation without trust all element and ended up in error.

For server launch "plugins/org.eclipse.equinox.launcher_<VersionForYourEclipse >.jar" has been suggested in the OSEE site but it cannot be found in the server package. Instead I am using the "org.eclipse.osgi.jar"
One other observation is that when the server launches i do not see a log of it fetching the Postgresql data pool size as it happens with 0.7 version.

Is there a way to find out if the server has completed the launch successfully?

Find below the server window log:

E:\OSEE\Server>java -Dorg.osgi.service.http.port=8089 -Dosee.check.tag.queue.on.startup=true -Dosee.db.connection.id=postgresq
lLocalhost -jar org.eclipse.osgi.jar -console

osgi> Fri Feb 26 11:54:13 IST 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@e49dcd

Fri Feb 26 11:54:13 IST 2010 org.eclipse.osee.framework.database.internal.InternalActivat or
INFO org.eclipse.osee.framework.database.internal.parser.DbConfig Parser getAllDbServices (50)
in getAllDbServices 3

Fri Feb 26 11:54:13 IST 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

Fri Feb 26 11:54:13 IST 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

Fri Feb 26 11:54:13 IST 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

Fri Feb 26 11:54:13 IST 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 @113beb5

Adding: org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @13e0aba
Fri Feb 26 11:54:13 IST 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 Feb 26 11:54:14 IST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties getOseeApplicationServerData (69)
Application Server Data: [C:\Documents and Settings\kumar]

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'
Fri Feb 26 11:54:21 IST 2010 org.eclipse.osee.framework.search.engine.internal.SearchEngi neTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable run (36)
On Start-Up Tagging - [0] tag queue items.

Fri Feb 26 11:54:22 IST 2010 org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.internal.ApplicationS erverManager executeLookupRegistration (89)
Application Server: [b3cf7053629a9440de9afbffe80e193e] registered.

Fri Feb 26 11:55:37 IST 2010 org.eclipse.osee.framework.manager.servlet.MasterServletActi vator
SEVERE org.eclipse.osee.framework.manager.servlet.SessionManagement Servlet doPost (95)
Error processing session request [ org.eclipse.equinox.http.servlet.internal.HttpServletRequest Adaptor @18e609b]
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(Unknown Source)
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-02-26 11:55:37.812::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)

Please do let me know the cause of the problem and the workaround.

regards,
Kumar

Re: OSEE 0.9.1 [message #523004 is a reply to message #515282]

Wed, 24 March 2010 14:15

Eclipse User

Sorry Kumar, I have been unable to replicate your problem. I think it is going to take one of the developers to understand what is happening.

The only possible suggestion I can make is that one of our client machines was reporting the java.lang.IllegalStateException: STREAM error when a disk corruption had occurred. Reinstalling the client from the zip file solved that problem.

All the best,
Mark

Re: OSEE 0.9.1 [message #526276 is a reply to message #517079]

Fri, 09 April 2010 08:42

Eclipse User

Kumar, I have the same problem。

Re: OSEE 0.9.1 [message #529980 is a reply to message #526276]

Tue, 27 April 2010 17:38

Eclipse User

i'm having the same problem as well... any chance to shed some light on possible solution?

Re: OSEE 0.9.1 [message #533144 is a reply to message #529980]

Wed, 12 May 2010 08:05

Eclipse User

I installed OSEE 0.9.1 and it works fine without any problems. The database initialization prompts were acting a bit funny though. However, it initialized correctly after few attempts.

Here are the commands I used to initialize and start OSEE.

OSEE application server

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="c:\OSEE\0.9.1\Data" -Dequinox.ds.debug=true -jar org.eclipse.osgi.jar -console

Database initialization

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

Client
eclipse -nl en -vmargs -Xmx512m -Dosee.application.server=http://localhost:8089 -Dosee.authentication.protocol=trustALL -consoleLog

Thanks to OSEE team for the new releases.

Nirmal

Re: OSEE 0.9.1 [message #535239 is a reply to message #533144]

Fri, 21 May 2010 13:08

Eclipse User

Please see also related thread http://www.eclipse.org/forums/index.php?t=msg&th=168493& amp;start=0&

Kumar - do you have any internationalisation settings, such as use of , rather than . for decimal point?

Re: OSEE 0.9.1 [message #539947 is a reply to message #515282]

Mon, 14 June 2010 07:17

Eclipse User

Dear Kumar,

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: OSEE 0.9.1 [message #576596 is a reply to message #526276]

Tue, 27 April 2010 17:38

Eclipse User

i'm having the same problem as well... any chance to shed some light on possible solution?

Re: OSEE 0.9.1 [message #576639 is a reply to message #576596]

Wed, 12 May 2010 08:05

Eclipse User

Re: OSEE 0.9.1 [message #576762 is a reply to message #576639]

Fri, 21 May 2010 13:08

Eclipse User

Previous Topic:	OSEE 0.9.1
Next Topic:	Ubuntu Postgresql. OSEE Server Not starting?

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Apr 20 18:11:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter