[ome-users] OMERO.server Upgrade Issue
josh.moore at gmx.de
josh.moore at gmx.de
Fri Nov 16 11:59:18 GMT 2007
Hi Oliver,
This is probably our black-sheep-issue #1. See
https://trac.openmicroscopy.org.uk/omero/ticket/444
for background, but essentially, this is a JBoss/Postgres warning and
nothing fatal. Unfortunately, the only way for us to prevent this
message is to add instructions on customizing JBoss or to ship a JBoss
package ourselves.
That doesn't change the fact that after a successful deployment:
(Rev: 1173) Ready.
your server shutdown. Can you confirm that you didn't hit Ctrl-C?
Then, there's one last issue which is, it doesn't look like you
are using the latest version. The upgrade should print out:
(Rev: 1701) Ready.
Any ideas on how that could be since you are clearly in a
"omero-3.0-Beta2.2" directory?
Best wishes,
~Josh
Oliver Mueller writes:
> Dear OMERO.server team,
>
> today I tried to upgrade the OMERO.server Beta 2.0 to Beta 2.2.
> I followed the OMERO.server Upgrade Instructions and everything seemed
> to work fine.
> But when I execute the run.sh, 'JBossManagedConnectionPool' throws a
> warning:
>
> 09:06:54,226 WARN [JBossManagedConnectionPool] Throwable while
> attempting to get a new connection: null
> org.jboss.resource.JBossResourceException: Could not create connection;
>
>
> and 'JDBCExceptionReporter' throws an error (the complete log is
> attached to this email):
>
> Caused by:
> org.jboss.resource.JBossResourceException: Apparently wrong driver class
> specified for URL: class: org.postgresql.Driver, url:
> jdbc:postgresql://localhost/omero3
> at
> org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:290)
> at
> org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:170)
>
> ... 217 more
>
>
> And that's why both, OMERO.insight and OMERO.importer
> do not see the OMERO.server (although the last lines of the startup log say
>
> 09:07:01,284 INFO [EJBContainer] STARTED EJB:
> ome.services.jboss.OmeroContextHook ejbName: OmeroContextHook
> 09:07:01,612 INFO [STDOUT]
> -------------------------------------------------
> 09:07:01,612 INFO [STDOUT] OMERO Version: 3.0-TRUNK (Rev: 1173) Ready.
> 09:07:01,612 INFO [STDOUT]
> -------------------------------------------------
> 09:07:01,619 INFO [EJB3Deployer] Deployed:
> file:/ome/omero-install/omero-3.0-Beta2.2/jboss-4.2.1.GA/server/default/tmp/deploy/tmp54463omero.ear-contents/server-3.0-TRUNK.jar
>
> 09:07:01,626 INFO [EARDeployer] Started J2EE application:
> file:/ome/omero-install/omero-3.0-Beta2.2/jboss-4.2.1.GA/server/default/deploy/omero.ear
>
> 09:07:01,716 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
> http-0.0.0.0-8080
> 09:07:01,735 INFO [AjpProtocol] Starting Coyote AJP/1.3 on
> ajp-0.0.0.0-8009
> 09:07:01,744 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build:
> SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 1m:211ms).
>
>
> Any suggestions? ;-)
>
> The OS is AIX 5.3, the DB is PostgreSQL 8.2.4.
>
> Regards,
> Oliver Mueller
>
> --
> Oliver M,b|(Bller
>
> Institut f,b|(Br Molekulare Zellbiologie
> Medizinische Fakult,bd(Bt
> Universit,bd(Bt des Saarlandes
> Geb,bd(Bude 61 - FR 2.1 - Anatomie & Zellbiologie
> D-66421 Homburg/Saar
> Tel.: + 49 (0) 6841 162 61 09
>
>
> ____________
> Virus checked by G DATA AntiVirus
> Version: AVKA 18.17 from 16.11.2007
> Virus news: www.antiviruslab.com
>
More information about the ome-users
mailing list