[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [osee-dev] Installation
|
Seems like the database has not been created properly.
Check that the osee schema and osee role exist in your postgresql
instance.
Use the following instructions: (copied from the User Guide)
Configure PostgreSQL for OSEE
1. Launch pgAdmin (in windows Start->All
Programs->PostgreSQL*->pgAdmin III)
2. Double Click on PostgreSQL Database Server (listed under
Servers on the left hand side)
1. If you are prompted for a password type the password
selected during installation (user should be postgres by default)
3. Create an "osee" user
1. Right-click on Login Roles (at the bottom of the tree
on the left hand side) and select "New Login Role..."
2. Enter the following in the dialog:
Role Name: osee
Can login should be checked
Password: osee
Password (again): osee
For Role Priviledges - select the following:
Inherits rights from parent roles
Superuser
Can create database objects
Can modify catalog directly
3. Click 'OK'
4. You should now have an "osee" user under Login Roles
4. Expand the Databases item in the tree
1. Create the OSEE database right-clicking on Databases
and selecting "New Database..."
2. Enter the following in the dialog:
Name: OSEE
Owner: osee
Encoding: UTF-8
3. Click 'OK'
4. You should now have an "OSEE" Database under Databases
5. Click on OSEE and then expand it and expand Schemas
1. Create the "osee" schema:
1. Right click on Schemas and select "New Schema..."
2. Enter the following in the dialog:
Name: osee
Owner: osee
3. Click 'OK'
4. You should now have an "osee" schema under
schemas
Once you have completed this step, launch the application server. Then
launch the database initialization application.
Once the database initialization process completes, you should be able
to see new tables under the osee schema by using PgAdmin.
The database should now be ready for use. You can now launch the client.
-----Original Message-----
From: Scott Raley [mailto:sraley@xxxxxxxxxxx]
Sent: Monday, April 27, 2009 12:33 PM
To: 'OSEE Developers mailing list'
Subject: RE: [osee-dev] Installation
I do that after launching the application server. The application server
in the dos window just gives me the osgi> prompt and I don't see
anything else.
Using the osee_app_server.bat file from the conference download. Open
another dos window and execute what you just gave me and eclipse opens.
I go to window open ats perspective and get OSEE Service(s) Unavailable:
Application Server. Error: Connection refused: connect
Session Manager. Error:
http://localhost:8089/osee/session?operation=create
Session is invalid - authentication is required Session is invalid -
authentication is required
I made the passwords match what was in the conference pdf file so what
password is it saying is incorrect? PostgreSQL ?
-----Original Message-----
From: osee-dev-bounces@xxxxxxxxxxx [mailto:osee-dev-bounces@xxxxxxxxxxx]
On Behalf Of Escobar, Roberto E
Sent: Monday, April 27, 2009 3:26 PM
To: OSEE Developers mailing list
Subject: RE: [osee-dev] Installation
Scott,
The command-line for launching the database initialization application
is out of date. Use the following instead:
eclipse -nosplash -application
org.eclipse.osee.framework.database.configClient -console -vmargs
-XX:MaxPermSize=256m -Xmx512m
-Dosee.application.server=http://localhost:8089
Instructions have been updated in the docs.
________________________________
From: Scott Raley [mailto:sraley@xxxxxxxxxxx]
Sent: Sunday, April 26, 2009 10:01 AM
To: osee-dev@xxxxxxxxxxx
Subject: [osee-dev] Installation
Im trying to install for the first time. And I have issues when I'm
trying to initialize database I get an eclipse error.
Command line for 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
The log is this:
!SESSION 2009-04-26 12:48:23.718
-----------------------------------------------
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-26 12:48:24.593
!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.datatools.connectivity.console.profile.StorageFileEditor,
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.EventService.
at
org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(Ecl
ipseAppContainer.java:242)
at
org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplica
tionLauncher.java:29)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplicat
ion(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Eclip
seAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.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)
I have the components downloaded. Application server is in c:\osee and
eclipse is in c:\eclipse with the .zip available installed. PostgreSQL
is installed and running out of the box configuration, nothing special.
Its configured with the OSEE user, database and schema.
I'm starting up the application server using this (no workspace
configured, its using default):
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
In my dos window I get:
C:\osee>java -Dosee.log.default=INFO -Dorg.osgi.service.http.port=8089
-Dosgi.co
mpatibility.bootdelegation=true -Xmx512m
-Dosee.db.connection.id=postgresqlLocal
host -Dequinox.ds.debug=true -jar org.eclipse.osgi_3.4.0.v20080326.jar
-console
osgi> Apr 26, 2009 12:46:33 PM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
Apr 26, 2009 12:46:33 PM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1989f84
Apr 26, 2009 12:46:33 PM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
Apr 26, 2009 12:46:33 PM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
Apr 26, 2009 12:46:33 PM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@13ad085
Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Adding:
org.eclipse.osee.framework.core.server.internal.ServerDatabaseProvider@8
2764b
Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Sun Apr 26 12:46:33 EDT 2009
org.eclipse.osee.framework.core.server.CoreSer
verActivator
INFO
org.eclipse.osee.framework.core.server.internal.ServerTaskScheduler
add
ServerTask (41)
Adding task: Clean up join tables
Sun Apr 26 12:46:33 EDT 2009
org.eclipse.osee.framework.core.server.CoreSer
verActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeAppl
icationServerData (54)
Application Server Data: [C:\Documents and Settings\sraley]
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'
Sun Apr 26 12:46:33 EDT 2009
org.eclipse.osee.framework.core.server.CoreSer
verActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationServerDataSto
r
e deregisterWithDb (63)
Server lookup table not initialized
Sun Apr 26 12:46:33 EDT 2009
org.eclipse.osee.framework.core.server.CoreSer
verActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationServerDataSto
r
e registerWithDb (80)
Server lookup table not initialized
Sun Apr 26 12:46:36 EDT 2009
org.eclipse.osee.framework.search.engine.inter
nal.SearchEngineTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRunnable
run (
45)
Tagging on Server Startup was not run.
Sun Apr 26 12:56:33 EDT 2009
org.eclipse.osee.framework.core.server.CoreSer
verActivator
WARNING
org.eclipse.osee.framework.core.server.internal.task.CleanJoinTablesSe
rverTask run (59)
Unable to get a database connection:
org.eclipse.osee.framework.db.connection.exception.OseeDataStoreExceptio
n: Unabl
e to get a database connection:
at
org.eclipse.osee.framework.db.connection.OseeConnectionPool.getConnec
tion(OseeConnectionPool.java:75)
at
org.eclipse.osee.framework.db.connection.OseeDbConnection.getConnecti
on(OseeDbConnection.java:60)
at
org.eclipse.osee.framework.db.connection.OseeDbConnection.getConnecti
on(OseeDbConnection.java:45)
at
org.eclipse.osee.framework.db.connection.ConnectionHandler.runPrepare
dUpdate(ConnectionHandler.java:55)
at
org.eclipse.osee.framework.core.server.internal.task.CleanJoinTablesS
erverTask.run(CleanJoinTablesServerTask.java:56)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown
Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$101(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
runPeriodic(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.postgresql.util.PSQLException: FATAL: database "OSEE"
does not ex
ist
at
org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(Conn
ectionFactoryImpl.java:444)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(Conne
ctionFactoryImpl.java:99)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactor
y.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Conn
ection.java:124)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Conn
ection.java:30)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Conn
ection.java:29)
at
org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:386)
at org.postgresql.Driver.connect(Driver.java:260)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at
org.eclipse.osee.framework.postgresql.PostgresqlConnection.getConnect
ion(PostgresqlConnection.java:28)
at
org.eclipse.osee.framework.db.connection.OseeConnectionPool.getOseeCo
nnection(OseeConnectionPool.java:81)
at
org.eclipse.osee.framework.db.connection.OseeConnectionPool.getConnec
tion(OseeConnectionPool.java:69)
... 13 more
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.287 / Virus Database: 270.12.4/2080 - Release Date:
04/27/09 06:19:00
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev
