[ome-users] Beta 3.1.1 does not start

[josh.moore at gmx.de]

Alexandre Cunha writes:
 > Hi Josh,

Hi.

 > Thanks for replying. We are doing a brand new installation, from 
 > scratch, so we are not upgrading any database. 

Understood. I misunderstood your email, sorry.

 > Hopefully the log file I sent you reveal our mistakes!

Actually, whether from a fresh install or an upgrade, it still looks
like JBoss has got itself into a very unhealthy state. Can you try
re-creating that directory and then repeat these steps:

  cd ~/Desktop/omero-Beta3.1/omero 
  export JBOSS_HOME=~/Desktop/omero-Beta3.1/jboss-4.2.3.GA
  java omero deploy
  $JBOSS_HOME/bin/run.sh 

Thanks,
~Josh.

 > Cheers,
 > - 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
 > >