Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » OSEE » Install problems
Install problems [message #12601] Sat, 18 April 2009 02:53 Go to next message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
I am looking for a requirements management/ configuration management tools
and osee seemed to be just the sort of thing I was looking for.

I am relatively new to the eclipse world and can't seem to get osee
running.
I am using Windows XP.

I have downloaded postgresql and installed successfully.
I added the osee user and created the database as per these instructions:

http://www.eclipse.org/osee/documentation/installation/postg resql_install.php

I have downloaded eclipse, and it starts fine.
I have downloaded OSEE 0.7.0 Integration build and installed the
dependencies listed here:
http://www.eclipse.org/osee/documentation/installation/requi rements.php

When I try to initialize the database with the DbInit application as
indicated here
http://www.eclipse.org/osee/documentation/installation/db_in it.php

I get a Runtime error that DbInit is not found. The log file is below.

Can anyone help me?

Thanks in advance.

!SESSION 2009-04-17 20:12:54.250
-----------------------------------------------
eclipse.buildId=M20090211-1700
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application
org.eclipse.osee.framework.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console

!ENTRY org.eclipse.osgi 4 0 2009-04-17 20:12:59.390
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry. The applications available are:
org.eclipse.ant.core.antRunner, org.eclipse.equinox.app.error,
org.eclipse.equinox.p2.artifact.repository.mirrorApplication ,
org.eclipse.equinox.p2.director.app.application,
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator,
org.eclipse.equinox.p2.metadata.repository.mirrorApplication ,
org.eclipse.equinox.p2.reconciler.application,
org.eclipse.help.base.infocenterApplication,
org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool,
org.eclipse.ui.ide.workbench, org.eclipse.update.core.standaloneUpdate,
org.eclipse.update.core.siteOptimizer, org.eclipse.ant.ui.antRunner,
org.eclipse.birt.report.debug.core.ReportDebugger,
org.eclipse.birt.report.engine.ReportExecutor,
org.eclipse.datatools.connectivity.console.profile.StorageFi leEditor,
org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger,
org.eclipse.emf.codegen.ecore.Generator,
org.eclipse.emf.importer.ecore.Ecore2GenModel,
org.eclipse.emf.importer.java.Java2GenModel,
org.eclipse.emf.importer.rose.Rose2GenModel,
org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter,
org.eclipse.pde.build.Build,
org.eclipse.pde.junit.runtime.uitestapplication,
org.eclipse.pde.junit.runtime.legacytestapplication,
org.eclipse.pde.junit.runtime.coretestapplication,
org.eclipse.pde.junit.runtime.coretestapplicationnonmain,
org.eclipse.wst.jsdt.core.JavaCodeFormatter,
org.eclipse.wst.server.preview.preview,
org.eclipse.osee.framework.database.configClient,
org.eclipse.osee.framework.database.availableDbTasks,
org.eclipse.osee.framework.jini.JiniLookup,
org.eclipse.osee.framework.messaging.event.skynet.EventServi ce.
at
org.eclipse.equinox.internal.app.EclipseAppContainer.startDe faultApp(EclipseAppContainer.java:242)
at
org.eclipse.equinox.internal.app.MainApplicationLauncher.run (MainApplicationLauncher.java:29)
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:386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Re: Install problems [message #12648 is a reply to message #12601] Mon, 20 April 2009 16:29 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
This may be of no help at all for your situation, as I installed OSEE from
http://osee.microdoc.com/node/2 and I am just a new user like yourself.

However, I failed to initialise the database because I didn't start the
server first before running oseeDbInitLocalc.exe. I'm wondering whether
your problem is something similar and you need to get the local OSEE
database server running first before you try the init.

Just a thought,

Mark
Re: Install problems [message #12690 is a reply to message #12648] Mon, 20 April 2009 20:30 Go to previous messageGo to next message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
I have tried that, both using the oseeDbInitLocalc.exe, the
oseeAppServerRemotc.exe program and the runServer-PgSqlLocalAll.sh script.

Also tried java updates, switching to earlier version of postgresql
(8.2.13).
Did all the create user, create database, create schema stuff on the
database for osee. Was careful about the uppercasee 'OSEE' database name.
Have tried stopping and restarting the database.

Have tried this on my work machine and my machine at home.
Eclipse starts fine.
Postgreql starts fine.

Running OseeLocal, or oseePostgresMicro results in JVM termination exit
code -1
I think it might be memory - I have only 1.5 G on this machine but only
713K free.

I tried on a third machine with more memory and it appears to work.


Thanks for help. Your success at least told me that there is something
wrong here.


Rob
Re: Install problems [message #12712 is a reply to message #12648] Mon, 20 April 2009 20:44 Go to previous messageGo to next message
Donald Dunne is currently offline Donald Dunne
Messages: 192
Registered: July 2009
Senior Member
That is correct, sounds like the Application Server has not been launched.

Follow instructions at http://osee.microdoc.com/node/2

I have updated the documentation page at
http://www.eclipse.org/osee/documentation/index.php to show the launch step.
Re: Install problems [message #12779 is a reply to message #12712] Tue, 21 April 2009 03:00 Go to previous messageGo to next message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
Still no joy with the server start.

When I run the script runServer-PgSqlLocalAll I get a bunch of messages
printed out on the server.

The log is shown below. Spams something about Tagging on Server Startup
was not run and Server lookup table not initialized - not sure if this is
bad or not, but I think it likely is.

I have messed with firewall settings, even turning the firewall off.


osgi> Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @1ffc686
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Mon Apr 20 20:45:15 MDT 2009
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

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeApplicationServerData (54)
Application Server Data: [C:\Documents and Settings\Rob]

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'
Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.db.connection.internal.InternalAc tivator
INFO org.eclipse.osee.framework.db.connection.OseeConnectionPool
getConnection (71)
getConnection - jdbc:postgresql://localhost:5432/OSEE - connection pool
size [1]

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
deregisterWithDb (63)
Server lookup table not initialized

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
registerWithDb (80)
Server lookup table not initialized

Mon Apr 20 20:45:18 MDT 2009
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.
Re: Install problems [message #12799 is a reply to message #12779] Tue, 21 April 2009 11:51 Go to previous messageGo to next message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
I am experiencing the exact same problems. In reference to the OSEE -
Database Initialization Instructions:

1. Database has been installed: check

2. Database server is running: I have confirmed the database server is
running (pgAdmin III): OSEE database with osee owner.

3. A file system path has been selected for binary data storage: I do not
know how to select this path but I am assuming the default is sufficient

4. An application server is running:
a)Within the app_server_0.7.0-2009-02-19_08_49 directory in a command
console:

C:\dump\app_server_0.7.0-2009-02-19_08_49>java -Dosee.log.default=INFO
-Dorg.osgi.service.http.port=8089 -Dosgi.compatibility.bootdelegation=true
-Xmx512m -Dosee.db.connection.id=postgresqlLocalhost -Dequinox.ds.debug=true
-jar org.eclipse.osgi_3.4.0.v20080326.jar -console

osgi> 21-Apr-2009 8:32:38 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1d009b4
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
21-Apr-2009 8:32:39 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@544ec1
Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @39443f
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
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'
Tue Apr 21 08:32:45 ADT 2009
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

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeApplicationServerData (54)
Application Server Data: [C:\Documents and Settings\trent]

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.db.connection.internal.InternalAc tivator
INFO org.eclipse.osee.framework.db.connection.OseeConnectionPool
getConnection (71)
getConnection - jdbc:postgresql://localhost:5432/OSEE - connection pool
size [1]

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
deregisterWithDb (63)
Server lookup table not initialized

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
registerWithDb (80)
Server lookup table not initialized

Tue Apr 21 08:32:48 ADT 2009
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.



osgi> Tue Apr 21 08:42:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
WARNING
org.eclipse.osee.framework.core.server.internal.task.CleanJo inTablesServerTask
run (59)
org.postgresql.util.PSQLException: ERROR: relation "osee_join_artifact"
does not exist
org.eclipse.osee.framework.db.connection.exception.OseeDataS toreException:
org.postgresql.util.PSQLException: ERROR: relation "osee_join_artifact"
does not
exist
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:100)
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:57)
at
org.eclipse.osee.framework.core.server.internal.task.CleanJo inTablesServerTask.run(CleanJoinTablesServerTask.java:56)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executor s.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(Future Task.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java: 150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.postgresql.util.PSQLException: ERROR: relation
"osee_join_artifact" 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:194)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(Abstract Jdbc2Statement.java:451)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags (AbstractJdbc2Statement.java:350)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(Ab stractJdbc2Statement.java:304)
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:98)
... 11 more


The stack trace shows up after the application server launch due to what?
and when? unsure.

Database initialization attempt generates the same error as Rob
Re: Install problems [message #12819 is a reply to message #12690] Tue, 21 April 2009 11:55 Go to previous messageGo to next message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
What are oseeDbInitLocalc.exe and oseeAppServerRemotc.exe? What package
are they in and why/when do you use them?

Note I am having the exact same problems as Rob and I am trying to
determine the solution.

Thanks,
Trent
Re: Install problems [message #13440 is a reply to message #12779] Tue, 21 April 2009 15:02 Go to previous messageGo to next message
Ryan D. Brooks is currently offline Ryan D. Brooks
Messages: 100
Registered: July 2009
Senior Member
Rob,

The quick answer is that the messages you see indicate that the server
started correctly.

The first word in the log messages indicates the severity (i.e. INFO).
The messages you are noticing about Tagging and Server lookup table not
initialized are of type INFO and do not represent a problem. The several
lines such that start with "Registered servlet" indicate the successful
start-up of various OSEE services.

The server is up and running and the next step is to initialize the
database. The message about the Server lookup table not initialized is
due to the database tables not yet existing (they are created during the
database initialization).

I see there is another post about the database initialization, so I will
reply to that one with more information.

Thanks,
Ryan


Thanks,
Ryan Brooks
Re: Install problems [message #13476 is a reply to message #13440] Tue, 21 April 2009 16:37 Go to previous messageGo to next message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
Ryan,

Not meaning to shang-hai Rob's problems but I have been investigating the
same issue.

I can confirm your statements that the application server is fine - I
confirmed by using the tutorial db init command "oseeDbInitLocalc.exe" and
then continuing with the tutorial via both the tutorial instance of
eclipse plus my own instance of eclipse with all of the dependencies
installed and the command line parameters of "-vmargs -Xmx512m
-Dosee.application.server=http://localhost:8089
-Dosee.authentication.protocol=demo".

I then repeated the problem of not being able to run the original DbInit
command "C:\eclipse>eclipse -nosplash -application
org.eclipse.osee.framework.application.server.DbInit -console -vmargs
-XX:MaxPermSize=256m -Xmx512m -Dosgi.compatibility.bootdelegation=true
-Dequinox.ds.debug=true -Dorg.osgi.service.http.port=8089
-Dosee.local.application.server=true
-Dosee.db.connection.id=postgresqlLocalhost" with the result of the
originally reported errors.

Any thoughts?

Trent
Re: Install problems [message #13497 is a reply to message #13476] Tue, 21 April 2009 23:21 Go to previous messageGo to next message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
Here is what we found out.
(A fellow that works with me that has eclipse experience arrived at the
following solution.)

Install postgresql as per the instructions.
Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
run oseeDbInitLocalc.exe
run oseeLocalc.exe

DO NOT run oseePostgresMicro.exe - if you do, this is what causes the
problem, and you must shutdown the osee server (i.e. exit the
runServer-PgSqlLocalAll.sh)

If you try to run oseeLocal or oseeDbInitLocalc after the running of
oseePostgresMicroc without first exiting runServer-PgSqlLocalAll, then the
problem does not get resolved.

Anyways, this has got me up and running that will allow me to give this a
whirl.

Thanks all for the input and help.

Rob
Re: Install problems [message #13518 is a reply to message #13497] Wed, 22 April 2009 03:27 Go to previous messageGo to next message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
Rob wrote:

...
> Install postgresql as per the instructions.
> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
> run oseeDbInitLocalc.exe
> run oseeLocalc.exe
...

I agree that these steps will provide a running eclipse instance with
which you can learn the osee capabilities and actions available.

However it doesn't get me a clean initialized database that I can use for
my own purposes using my own installation of eclipse/plugins/and tools.

I am still wondering what could cause the problem documented in the first
message of this thread, i.e. the failure of the documented DbInit step
located at
" http://www.eclipse.org/osee/documentation/installation/db_in it.php"
(which I see is now retired).

Comments anyone?

Trent
Re: Install problems [message #13557 is a reply to message #13518] Wed, 22 April 2009 16:35 Go to previous messageGo to next message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
I don't think not executing oseePostgresMicroc.exe will stop us from
initializing our own database , according to my understanding all it does
is pre-initialize database by connecting to external server (May be the
university example Don explained in his screen cast)...what you can do in
documentation (http://osee.microdoc.com/node/2) for OSEE client launch
options follow step 2 "Local Application Server with Local PostgreSql
Database" instead of step 1 "Pre-initialized Database".

Anyways i was also looking at oseePostgresMicro configuration settings and
i thought there could be two possibilities why this error is occuring:

1) There is "http://osee.microdoc.com:8089/" parameter passed to
application server. I am more thinking there is something wrong there, may
be they(developers) removed data from the 8089 port. In the installation
documentation, they say

"Launch the OSEE Eclipse client using <install dir>\oseePostgresMicroc.exe
to connect to the Microdoc repository. You must have access to port 5432
to be able to connect"
So i am guessing if we change the port number from 8089 to 5432 in
configuration settings it should work...

2) In the version 0.7.0 the
"org.eclipse.osee.framework.application.server.DbInit" is not registering
(or) doesn't exist. I am not sure where this file should be, i have
checked appserver plugins and it doesn't exist there and i think it should
be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
or something else

Anyways i would try the case 1 by myself soon and can tell you what
happened...
I just thought of sharing this...

I would really appreciate if developers can answer this connection to
pre-initialized database problem. Also in the documentation
(http://osee.microdoc.com/node/2) you have indicated run populate demo
action, but i am missing it, can you provide me some detail guidance where
that demo action is?
Re: Install problems [message #13646 is a reply to message #13557] Fri, 24 April 2009 20:42 Go to previous messageGo to next message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
Venkat Mantripragada wrote:

> I don't think not executing oseePostgresMicroc.exe will stop us from
> initializing our own database , according to my understanding all it does
> is pre-initialize database by connecting to external server (May be the
> university example Don explained in his screen cast)...what you can do in
> documentation (http://osee.microdoc.com/node/2) for OSEE client launch
> options follow step 2 "Local Application Server with Local PostgreSql
> Database" instead of step 1 "Pre-initialized Database".

> Anyways i was also looking at oseePostgresMicro configuration settings and
> i thought there could be two possibilities why this error is occuring:

> 1) There is "http://osee.microdoc.com:8089/" parameter passed to
> application server. I am more thinking there is something wrong there, may
> be they(developers) removed data from the 8089 port. In the installation
> documentation, they say

> "Launch the OSEE Eclipse client using <install dir>oseePostgresMicroc.exe
> to connect to the Microdoc repository. You must have access to port 5432
> to be able to connect"
> So i am guessing if we change the port number from 8089 to 5432 in
> configuration settings it should work...

> 2) In the version 0.7.0 the
> "org.eclipse.osee.framework.application.server.DbInit" is not registering
> (or) doesn't exist. I am not sure where this file should be, i have
> checked appserver plugins and it doesn't exist there and i think it should
> be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
> or something else

> Anyways i would try the case 1 by myself soon and can tell you what
> happened...
> I just thought of sharing this...

> I would really appreciate if developers can answer this connection to
> pre-initialized database problem. Also in the documentation
> (http://osee.microdoc.com/node/2) you have indicated run populate demo
> action, but i am missing it, can you provide me some detail guidance where
> that demo action is?
There you go, if you replace the db_init with the below statement, it
works, I have successfully populate my OSEE 0.7 with the john hopkins demo
data...

eclipsec -application org.eclipse.osee.framework.database.configClient
-vmargs -Xmx256m -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"
Re: Install problems [message #13688 is a reply to message #13497] Mon, 27 April 2009 13:53 Go to previous messageGo to next message
SR Mising name is currently offline SR Mising name
Messages: 3
Registered: July 2009
Junior Member
I have tried and it appears that there are three different installation
instructions in some shape or form because microdocs doesn't match eclipse
and what is in the brief from eclipsecon2009 is a little different as well.

Following your steps when I run the oseedbinitlocalc.exe file eclipse
throws an error log which is:

!SESSION 2009-04-27 09:48:36.093
-----------------------------------------------
eclipse.buildId=M20080911-1700
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.configClient
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.database.configClient -console -debug

!ENTRY org.eclipse.osgi 4 0 2009-04-27 09:48:37.578
!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:215)
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:98)
at
org.eclipse.osee.framework.database.initialize.DatabaseIniti alizationOperation.execute(DatabaseInitializationOperation.j ava:68)
at
org.eclipse.osee.framework.database.initialize.DatabaseIniti alizationOperation.executeConfigureFromJvmProperties(Databas eInitializationOperation.java:294)
at
org.eclipse.osee.framework.database.ConfigDatabase.start(Con figDatabase.java:32)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
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:386)
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: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.io.IOException: Error during POST
[http://localhost:8089/osee/session?operation=create] - status code: [500]
at
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:116)
at
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:210)
... 17 more
Caused by: java.lang.Exception: HTTP/1.1 500 Internal Server Error
at
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:108)
... 18 more
Re: Install problems [message #13750 is a reply to message #13518] Tue, 28 April 2009 21:11 Go to previous message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
Trent Johnson wrote:

> Rob wrote:

> ...
>> Install postgresql as per the instructions.
>> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
>> run oseeDbInitLocalc.exe
>> run oseeLocalc.exe
> ...

> I agree that these steps will provide a running eclipse instance with
> which you can learn the osee capabilities and actions available.

> However it doesn't get me a clean initialized database that I can use for
> my own purposes using my own installation of eclipse/plugins/and tools.

> I am still wondering what could cause the problem documented in the first
> message of this thread, i.e. the failure of the documented DbInit step
> located at
> " http://www.eclipse.org/osee/documentation/installation/db_in it.php"
> (which I see is now retired).

> Comments anyone?

> Trent

***************************-------************************** *****

Sorry i got this wrong , Trent is right. We cannot get a clean database by
following any of steps in microdoc or in the retired link. when we execute
statement specified in
http://www.eclipse.org/osee/documentation/installation/db_in it.php i get
the following error:

************************************************************ ***********
!SESSION 2009-04-28 14:49:34.705
-----------------------------------------------
eclipse.buildId=M20080911-1700
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.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console

!ENTRY org.eclipse.osgi 4 0 2009-04-28 14:49:38.096
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry.
************************************************************ ******************

The only way to solve the problem is getting the file through Update
manager in eclipse, then only eclipse will register. But, where is the
file? which one should i update to get this file?

If anybody knows the solution, please provide it. An updated documentation
is greatly appreciated.

Please note: The documentation for running a demo database, screen casts,
wiki is very good, i got understanding of the tool by using demo data. But
when i want to start piloting this good tool in our company, there is no
clear documentation on where to start for a clean installation.

Thank you.
Re: Install problems [message #572580 is a reply to message #12601] Mon, 20 April 2009 16:29 Go to previous message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
This may be of no help at all for your situation, as I installed OSEE from
http://osee.microdoc.com/node/2 and I am just a new user like yourself.

However, I failed to initialise the database because I didn't start the
server first before running oseeDbInitLocalc.exe. I'm wondering whether
your problem is something similar and you need to get the local OSEE
database server running first before you try the init.

Just a thought,

Mark
Re: Install problems [message #572623 is a reply to message #12648] Mon, 20 April 2009 20:30 Go to previous message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
I have tried that, both using the oseeDbInitLocalc.exe, the
oseeAppServerRemotc.exe program and the runServer-PgSqlLocalAll.sh script.

Also tried java updates, switching to earlier version of postgresql
(8.2.13).
Did all the create user, create database, create schema stuff on the
database for osee. Was careful about the uppercasee 'OSEE' database name.
Have tried stopping and restarting the database.

Have tried this on my work machine and my machine at home.
Eclipse starts fine.
Postgreql starts fine.

Running OseeLocal, or oseePostgresMicro results in JVM termination exit
code -1
I think it might be memory - I have only 1.5 G on this machine but only
713K free.

I tried on a third machine with more memory and it appears to work.


Thanks for help. Your success at least told me that there is something
wrong here.


Rob
Re: Install problems [message #572650 is a reply to message #12648] Mon, 20 April 2009 20:44 Go to previous message
Donald Dunne is currently offline Donald Dunne
Messages: 192
Registered: July 2009
Senior Member
That is correct, sounds like the Application Server has not been launched.

Follow instructions at http://osee.microdoc.com/node/2

I have updated the documentation page at
http://www.eclipse.org/osee/documentation/index.php to show the launch step.
Re: Install problems [message #572711 is a reply to message #12712] Tue, 21 April 2009 03:00 Go to previous message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
Still no joy with the server start.

When I run the script runServer-PgSqlLocalAll I get a bunch of messages
printed out on the server.

The log is shown below. Spams something about Tagging on Server Startup
was not run and Server lookup table not initialized - not sure if this is
bad or not, but I think it likely is.

I have messed with firewall settings, even turning the firewall off.


osgi> Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @1ffc686
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Mon Apr 20 20:45:15 MDT 2009
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

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeApplicationServerData (54)
Application Server Data: [C:\Documents and Settings\Rob]

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'
Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.db.connection.internal.InternalAc tivator
INFO org.eclipse.osee.framework.db.connection.OseeConnectionPool
getConnection (71)
getConnection - jdbc:postgresql://localhost:5432/OSEE - connection pool
size [1]

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
deregisterWithDb (63)
Server lookup table not initialized

Mon Apr 20 20:45:15 MDT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
registerWithDb (80)
Server lookup table not initialized

Mon Apr 20 20:45:18 MDT 2009
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.
Re: Install problems [message #572725 is a reply to message #12779] Tue, 21 April 2009 11:51 Go to previous message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
I am experiencing the exact same problems. In reference to the OSEE -
Database Initialization Instructions:

1. Database has been installed: check

2. Database server is running: I have confirmed the database server is
running (pgAdmin III): OSEE database with osee owner.

3. A file system path has been selected for binary data storage: I do not
know how to select this path but I am assuming the default is sufficient

4. An application server is running:
a)Within the app_server_0.7.0-2009-02-19_08_49 directory in a command
console:

C:\dump\app_server_0.7.0-2009-02-19_08_49>java -Dosee.log.default=INFO
-Dorg.osgi.service.http.port=8089 -Dosgi.compatibility.bootdelegation=true
-Xmx512m -Dosee.db.connection.id=postgresqlLocalhost -Dequinox.ds.debug=true
-jar org.eclipse.osgi_3.4.0.v20080326.jar -console

osgi> 21-Apr-2009 8:32:38 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1d009b4
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
21-Apr-2009 8:32:39 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
21-Apr-2009 8:32:39 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@544ec1
Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @39443f
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
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'
Tue Apr 21 08:32:45 ADT 2009
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

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeApplicationServerData (54)
Application Server Data: [C:\Documents and Settings\trent]

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.db.connection.internal.InternalAc tivator
INFO org.eclipse.osee.framework.db.connection.OseeConnectionPool
getConnection (71)
getConnection - jdbc:postgresql://localhost:5432/OSEE - connection pool
size [1]

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
deregisterWithDb (63)
Server lookup table not initialized

Tue Apr 21 08:32:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStore
registerWithDb (80)
Server lookup table not initialized

Tue Apr 21 08:32:48 ADT 2009
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.



osgi> Tue Apr 21 08:42:45 ADT 2009
org.eclipse.osee.framework.core.server.CoreServerActivator
WARNING
org.eclipse.osee.framework.core.server.internal.task.CleanJo inTablesServerTask
run (59)
org.postgresql.util.PSQLException: ERROR: relation "osee_join_artifact"
does not exist
org.eclipse.osee.framework.db.connection.exception.OseeDataS toreException:
org.postgresql.util.PSQLException: ERROR: relation "osee_join_artifact"
does not
exist
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:100)
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:57)
at
org.eclipse.osee.framework.core.server.internal.task.CleanJo inTablesServerTask.run(CleanJoinTablesServerTask.java:56)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executor s.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(Future Task.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java: 150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu tureTask.run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa dPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.postgresql.util.PSQLException: ERROR: relation
"osee_join_artifact" 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:194)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(Abstract Jdbc2Statement.java:451)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags (AbstractJdbc2Statement.java:350)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(Ab stractJdbc2Statement.java:304)
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.r unPreparedUpdate(ConnectionHandler.java:98)
... 11 more


The stack trace shows up after the application server launch due to what?
and when? unsure.

Database initialization attempt generates the same error as Rob
Re: Install problems [message #572739 is a reply to message #12690] Tue, 21 April 2009 11:55 Go to previous message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
What are oseeDbInitLocalc.exe and oseeAppServerRemotc.exe? What package
are they in and why/when do you use them?

Note I am having the exact same problems as Rob and I am trying to
determine the solution.

Thanks,
Trent
Re: Install problems [message #572830 is a reply to message #12779] Tue, 21 April 2009 15:02 Go to previous message
Ryan D. Brooks is currently offline Ryan D. Brooks
Messages: 100
Registered: July 2009
Senior Member
Rob,

The quick answer is that the messages you see indicate that the server
started correctly.

The first word in the log messages indicates the severity (i.e. INFO).
The messages you are noticing about Tagging and Server lookup table not
initialized are of type INFO and do not represent a problem. The several
lines such that start with "Registered servlet" indicate the successful
start-up of various OSEE services.

The server is up and running and the next step is to initialize the
database. The message about the Server lookup table not initialized is
due to the database tables not yet existing (they are created during the
database initialization).

I see there is another post about the database initialization, so I will
reply to that one with more information.

Thanks,
Ryan


Thanks,
Ryan Brooks
Re: Install problems [message #572878 is a reply to message #13440] Tue, 21 April 2009 16:37 Go to previous message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
Ryan,

Not meaning to shang-hai Rob's problems but I have been investigating the
same issue.

I can confirm your statements that the application server is fine - I
confirmed by using the tutorial db init command "oseeDbInitLocalc.exe" and
then continuing with the tutorial via both the tutorial instance of
eclipse plus my own instance of eclipse with all of the dependencies
installed and the command line parameters of "-vmargs -Xmx512m
-Dosee.application.server=http://localhost:8089
-Dosee.authentication.protocol=demo".

I then repeated the problem of not being able to run the original DbInit
command "C:\eclipse>eclipse -nosplash -application
org.eclipse.osee.framework.application.server.DbInit -console -vmargs
-XX:MaxPermSize=256m -Xmx512m -Dosgi.compatibility.bootdelegation=true
-Dequinox.ds.debug=true -Dorg.osgi.service.http.port=8089
-Dosee.local.application.server=true
-Dosee.db.connection.id=postgresqlLocalhost" with the result of the
originally reported errors.

Any thoughts?

Trent
Re: Install problems [message #572909 is a reply to message #13476] Tue, 21 April 2009 23:21 Go to previous message
Rob is currently offline Rob
Messages: 8
Registered: July 2009
Junior Member
Here is what we found out.
(A fellow that works with me that has eclipse experience arrived at the
following solution.)

Install postgresql as per the instructions.
Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
run oseeDbInitLocalc.exe
run oseeLocalc.exe

DO NOT run oseePostgresMicro.exe - if you do, this is what causes the
problem, and you must shutdown the osee server (i.e. exit the
runServer-PgSqlLocalAll.sh)

If you try to run oseeLocal or oseeDbInitLocalc after the running of
oseePostgresMicroc without first exiting runServer-PgSqlLocalAll, then the
problem does not get resolved.

Anyways, this has got me up and running that will allow me to give this a
whirl.

Thanks all for the input and help.

Rob
Re: Install problems [message #572930 is a reply to message #13497] Wed, 22 April 2009 03:27 Go to previous message
Trent Johnson is currently offline Trent Johnson
Messages: 14
Registered: July 2009
Junior Member
Rob wrote:

...
> Install postgresql as per the instructions.
> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
> run oseeDbInitLocalc.exe
> run oseeLocalc.exe
...

I agree that these steps will provide a running eclipse instance with
which you can learn the osee capabilities and actions available.

However it doesn't get me a clean initialized database that I can use for
my own purposes using my own installation of eclipse/plugins/and tools.

I am still wondering what could cause the problem documented in the first
message of this thread, i.e. the failure of the documented DbInit step
located at
" http://www.eclipse.org/osee/documentation/installation/db_in it.php"
(which I see is now retired).

Comments anyone?

Trent
Re: Install problems [message #572981 is a reply to message #13518] Wed, 22 April 2009 16:35 Go to previous message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
I don't think not executing oseePostgresMicroc.exe will stop us from
initializing our own database , according to my understanding all it does
is pre-initialize database by connecting to external server (May be the
university example Don explained in his screen cast)...what you can do in
documentation (http://osee.microdoc.com/node/2) for OSEE client launch
options follow step 2 "Local Application Server with Local PostgreSql
Database" instead of step 1 "Pre-initialized Database".

Anyways i was also looking at oseePostgresMicro configuration settings and
i thought there could be two possibilities why this error is occuring:

1) There is "http://osee.microdoc.com:8089/" parameter passed to
application server. I am more thinking there is something wrong there, may
be they(developers) removed data from the 8089 port. In the installation
documentation, they say

"Launch the OSEE Eclipse client using <install dir>\oseePostgresMicroc.exe
to connect to the Microdoc repository. You must have access to port 5432
to be able to connect"
So i am guessing if we change the port number from 8089 to 5432 in
configuration settings it should work...

2) In the version 0.7.0 the
"org.eclipse.osee.framework.application.server.DbInit" is not registering
(or) doesn't exist. I am not sure where this file should be, i have
checked appserver plugins and it doesn't exist there and i think it should
be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
or something else

Anyways i would try the case 1 by myself soon and can tell you what
happened...
I just thought of sharing this...

I would really appreciate if developers can answer this connection to
pre-initialized database problem. Also in the documentation
(http://osee.microdoc.com/node/2) you have indicated run populate demo
action, but i am missing it, can you provide me some detail guidance where
that demo action is?
Re: Install problems [message #573080 is a reply to message #13557] Fri, 24 April 2009 20:42 Go to previous message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
Venkat Mantripragada wrote:

> I don't think not executing oseePostgresMicroc.exe will stop us from
> initializing our own database , according to my understanding all it does
> is pre-initialize database by connecting to external server (May be the
> university example Don explained in his screen cast)...what you can do in
> documentation (http://osee.microdoc.com/node/2) for OSEE client launch
> options follow step 2 "Local Application Server with Local PostgreSql
> Database" instead of step 1 "Pre-initialized Database".

> Anyways i was also looking at oseePostgresMicro configuration settings and
> i thought there could be two possibilities why this error is occuring:

> 1) There is "http://osee.microdoc.com:8089/" parameter passed to
> application server. I am more thinking there is something wrong there, may
> be they(developers) removed data from the 8089 port. In the installation
> documentation, they say

> "Launch the OSEE Eclipse client using <install dir>oseePostgresMicroc.exe
> to connect to the Microdoc repository. You must have access to port 5432
> to be able to connect"
> So i am guessing if we change the port number from 8089 to 5432 in
> configuration settings it should work...

> 2) In the version 0.7.0 the
> "org.eclipse.osee.framework.application.server.DbInit" is not registering
> (or) doesn't exist. I am not sure where this file should be, i have
> checked appserver plugins and it doesn't exist there and i think it should
> be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
> or something else

> Anyways i would try the case 1 by myself soon and can tell you what
> happened...
> I just thought of sharing this...

> I would really appreciate if developers can answer this connection to
> pre-initialized database problem. Also in the documentation
> (http://osee.microdoc.com/node/2) you have indicated run populate demo
> action, but i am missing it, can you provide me some detail guidance where
> that demo action is?
There you go, if you replace the db_init with the below statement, it
works, I have successfully populate my OSEE 0.7 with the john hopkins demo
data...

eclipsec -application org.eclipse.osee.framework.database.configClient
-vmargs -Xmx256m -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"
Re: Install problems [message #573125 is a reply to message #13497] Mon, 27 April 2009 13:53 Go to previous message
SR Mising name is currently offline SR Mising name
Messages: 3
Registered: July 2009
Junior Member
I have tried and it appears that there are three different installation
instructions in some shape or form because microdocs doesn't match eclipse
and what is in the brief from eclipsecon2009 is a little different as well.

Following your steps when I run the oseedbinitlocalc.exe file eclipse
throws an error log which is:

!SESSION 2009-04-27 09:48:36.093
-----------------------------------------------
eclipse.buildId=M20080911-1700
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.configClient
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.database.configClient -console -debug

!ENTRY org.eclipse.osgi 4 0 2009-04-27 09:48:37.578
!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:215)
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:98)
at
org.eclipse.osee.framework.database.initialize.DatabaseIniti alizationOperation.execute(DatabaseInitializationOperation.j ava:68)
at
org.eclipse.osee.framework.database.initialize.DatabaseIniti alizationOperation.executeConfigureFromJvmProperties(Databas eInitializationOperation.java:294)
at
org.eclipse.osee.framework.database.ConfigDatabase.start(Con figDatabase.java:32)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
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:386)
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: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.io.IOException: Error during POST
[http://localhost:8089/osee/session?operation=create] - status code: [500]
at
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:116)
at
org.eclipse.osee.framework.core.client.internal.InternalClie ntSessionManager.internalAcquireSession(InternalClientSessio nManager.java:210)
... 17 more
Caused by: java.lang.Exception: HTTP/1.1 500 Internal Server Error
at
org.eclipse.osee.framework.jdk.core.util.HttpProcessor.post( HttpProcessor.java:108)
... 18 more
Re: Install problems [message #573187 is a reply to message #13518] Tue, 28 April 2009 21:11 Go to previous message
Venkat Mantripragada is currently offline Venkat Mantripragada
Messages: 8
Registered: July 2009
Junior Member
Trent Johnson wrote:

> Rob wrote:

> ...
>> Install postgresql as per the instructions.
>> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
>> run oseeDbInitLocalc.exe
>> run oseeLocalc.exe
> ...

> I agree that these steps will provide a running eclipse instance with
> which you can learn the osee capabilities and actions available.

> However it doesn't get me a clean initialized database that I can use for
> my own purposes using my own installation of eclipse/plugins/and tools.

> I am still wondering what could cause the problem documented in the first
> message of this thread, i.e. the failure of the documented DbInit step
> located at
> " http://www.eclipse.org/osee/documentation/installation/db_in it.php"
> (which I see is now retired).

> Comments anyone?

> Trent

***************************-------************************** *****

Sorry i got this wrong , Trent is right. We cannot get a clean database by
following any of steps in microdoc or in the retired link. when we execute
statement specified in
http://www.eclipse.org/osee/documentation/installation/db_in it.php i get
the following error:

************************************************************ ***********
!SESSION 2009-04-28 14:49:34.705
-----------------------------------------------
eclipse.buildId=M20080911-1700
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.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console

!ENTRY org.eclipse.osgi 4 0 2009-04-28 14:49:38.096
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry.
************************************************************ ******************

The only way to solve the problem is getting the file through Update
manager in eclipse, then only eclipse will register. But, where is the
file? which one should i update to get this file?

If anybody knows the solution, please provide it. An updated documentation
is greatly appreciated.

Please note: The documentation for running a demo database, screen casts,
wiki is very good, i got understanding of the tool by using demo data. But
when i want to start piloting this good tool in our company, there is no
clear documentation on where to start for a clean installation.

Thank you.
Previous Topic:Data dictionary (3rd attempt to post)
Next Topic:Installation w/ Qucik Start Tutorial
Goto Forum:
  


Current Time: Tue Sep 16 17:33:27 GMT 2014

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

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