users@glassfish.java.net

Live Upgrade broke my SJS Application Server

From: <glassfish_at_javadesktop.org>
Date: Sat, 02 May 2009 15:41:31 PDT

I'm trying to live upgrade a server to the Solaris 10 10/08, from 11/06. During the live upgrade I got the following error:

WARNING: <16> packages failed to install properly on boot environment <sol10_1008_stage1>.
INFORMATION: </var/sadm/system/data/upgrade_failed_pkgadds> on boot
environment <sol10_1008_stage1> contains a list of packages that failed to
upgrade or install properly. Review the file before you reboot the system
to determine if any additional system maintenance is required.

File contents:

# cat /var/sadm/system/data/upgrade_failed_pkgadds
SUNWiqfs
SUNWiquc
SUNWiqum
SUNWjato
SUNWiqjx
SUNWiqr
SUNWiqu
SUNWascmn
SUNWasac
SUNWasu
SUNWasdem
SUNWasjdoc
SUNWasman
SUNWjatodoc
SUNWjatodmo
SUNWasut

So there are some AS packages in there. I wasn't sure if this was fatal or not (I was thinking, so what if they failed to upgrade? A Solaris upgrade wouldn't upgrade the AS packages anyway.) so I activated the new BE and restarted. Now when I try to start AS I get:

[#|2009-05-02T18:12:32.759-0400|INFO|sun-appserver-ee8.1_02|javax.enterprise.sysccessfully|#]

[#|2009-05-02T18:12:33.187-0400|INFO|sun-appserver-ee8.1_02|javax.enterprise.sys com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2009-05-02T18:12:33.402-0400|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.r]

[#|2009-05-02T18:12:33.408-0400|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.sderLifecycle_at_778 cannot be initialized! : com.sun.appserv.server.ServerLifecyImpl|#]

[#|2009-05-02T18:12:33.410-0400|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.salization
com.sun.appserv.server.ServerLifecycleException: com.sun.messaging.jmq.admin.jms
        at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProvi
        at com.sun.enterprise.server.ApplicationServer.onInitialization(Applicat
        at com.sun.enterprise.server.PEMain.run(PEMain.java:295)
        at com.sun.enterprise.server.PEMain.main(PEMain.java:218)
Caused by: java.lang.ClassNotFoundException: com.sun.messaging.jmq.admin.jmsspi.
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:164)
        at com.sun.enterprise.jms.IASJmsUtil.getJMSAdminFactory(IASJmsUtil.java:
        at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProvi
        ... 3 more
|#]

[#|2009-05-02T18:12:33.418-0400|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.s

[#|2009-05-02T18:12:33.419-0400|INFO|sun-appserver-ee8.1_02|javax.enterprise.sys

[#|2009-05-02T18:12:33.425-0400|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.silure.|#]


I'm going to flip back to the old BE, but I'd like to figure out why this has failed. It gives me cause for concern if I try to do an in place upgrade.

Any input would be appreciated.

Thanks,
Mark
[Message sent by forum member 'med1972' (med1972)]

http://forums.java.net/jive/thread.jspa?messageID=344747