[ome-users] Beta 3.1.1 does not start
josh.moore at gmx.de
josh.moore at gmx.de
Wed Oct 15 19:10:39 BST 2008
Hi Alexandre,
There are lots of non-OMERO errors in there.
2008-10-14 16:48:22,498 WARN [org.jboss.system.ServiceController]
(main) Problem starting service
jboss:service=Hypersonic,database=localDB java.sql.SQLException: The
database is already in use by another process:
org.hsqldb.persist.NIOLockFile at 15abddad[file
=/usr/local/omero-Beta3.1.1/jboss-4.2.3.GA/serve
r/default/data/hypersonic/localDB.lck, exists=true, locked=false,
valid=false, fl =null]:
...
2008-10-15 10:53:04,658 ERROR
[org.jboss.aop.deployment.AspectDeployer] (JBoss Shutdown Hook) failed
to stop java.io.FileNotFoundException:
/usr/local/omero-Beta3.1.1/jboss-4.2.3.GA/server/default/tmp/deploy/tmp29404ejb3-interceptors-aop.xml
Is it possible that your zip got corrupted or that you interrupted the
server abruptly at some point? One thing you might try is to delete
the jboss-4.2.3.GA and recreate it.
~J.
Alexandre Cunha writes:
> Hi Josh,
>
> Thanks for responding. Attached is the log file, gzipped.
> Please let me know if you can spot our mistake.
>
> Best,
> - Alex.
>
>
> josh.moore at gmx.de wrote:
> > Hello Alexandre,
> >
> > The error that you and Mario reported will show up any time the server
> > doesn't start, and is not directly related to the upgrade. I'm
> > assuming the database upgrade script completed successfully for
> > you. If so, could you perhaps send us the contents of
> > jboss-4.2.3.GA/server/default/log/server.log Thanks!
> >
> > Best wishes,
> > ~Josh.
> >
> > Alexandre Cunha writes:
> > > Mario,
> > >
> > > Just now after revisiting the recent emails sent to ome-users list I
> > > realized that the problem I just reported is actually the same one you
> > > reported yesterday (msg below). We did upgrade postgres,
> > >
> > > cunha [68] : psql -V
> > > psql (PostgreSQL) 8.3.4
> > > contains support for command-line editing
> > >
> > > and have Java 1.6
> > >
> > > cunha [69] : java -version
> > > java version "1.6.0_07"
> > > Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> > > Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
> > >
> > > so I am wondering if in fact the upgrade is sufficient to solve the
> > > problem or there is something else that needs to be worked on (?).
> > >
> > > Cheers,
> > > - Alex.
> > >
> > >
> > > Mario Valle wrote:
> > > > Dear all,
> > > > inital testing of 3.0.1 were successful. Now upgraded to 3.1.1 and no
> > > > way to start the server.
> > > > OK, I was not able to upgrade the database due the SQL syntax error
> > > > (covered on another mail on the list).
> > > > I do not know if the hanging of the server during initialization is due
> > > > to the incomplete upgrade or not. But here it is.
> > > >
> > > > The last line of the server log is:
> > > >
> > > > 10:30:41,434 INFO [Log4jService$URLWatchTimerTask] Configuring from
> > > > URL: resource:jboss-log4j.xml
> > > >
> > > > If I try to connect using the WebAdmin interface, the message is:
> > > >
> > > > Connection failure: Error creating bean with name 'init' defined in
> > > > class path resource [ome/client/spring.xml]: Cannot resolve reference to
> > > > bean 'managed-ome.api.ISession' while setting bean property
> > > > 'sessionService'; nested exception is
> > > > org.springframework.beans.factory.BeanCreationException: Error creating
> > > > bean with name 'managed-ome.api.ISession': FactoryBean threw exception
> > > > on object creation; nested exception is ome.client.OutOfService: Cannot
> > > > initialize service proxy
> > > >
> > > > Thanks for your help!
> > > > mario
> >
More information about the ome-users
mailing list