Skip to main content

Update Tool Causes Death to Domain

26 replies [Last post]
javamonkey79
Offline
Joined: 2010-06-17
Points: 0

After running the update tool on a test domain I was not able to get it to start.

The version from the admin page shows: GlassFish v3 (build 74.2) but I'm not sure that is right, since the other prod domains have not been restarted.

After building the new domain, I ran the update tool. I then shut the domain down. When I attemped to start it - it times out.

A review of the server.log looks as though there is a dependency problem in one of the OSGi bundles:

[#|2010-08-17T15:41:20.538-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]

[#|2010-08-17T15:41:20.538-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
|#]

[#|2010-08-17T15:41:25.541-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/osgi-http.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]

[#|2010-08-17T15:41:25.542-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
|#]

[#|2010-08-17T15:41:25.542-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]

[#|2010-08-17T15:41:25.543-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
|#]

Does anyone out there know how to resolve this? We really like some elements of GFv3 - but this could be a game changer for us. If we have to rebuild the server (again) I don't think we'll use GFv3.

TIA

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
snjezana
Offline
Joined: 2005-02-15
Points: 0

Missing post #2

Date: Fri, 20 Aug 2010 15:51:34 -0700
From: Snjezana Sevo-Zenzerovic
Content-Type: text/plain; charset=UTF-8; format=flowed

I see, but note that you did not apply updates, you actually installed
additional packages which were not present in your initial installation
and that eventually caused the problem...

Since you cannot apply updates from Admin console update section, you
need to run 'pkg image-update' command and this will upgrade your
installation from v3 to 3.0.1 (which is stable release, so everything
should work without glitch).

You should stop your domains before applying the update and restart them
afterwards. You may also want to clean up osgi-cache directories for
each domain which was running before restarting so that all OSGi bundles
get cleanly reloaded.

glassfish@javadesktop.org wrote:
> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>
> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>
> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
> org.glassfish.deployment.common.DeploymentException
>
> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>
> I think this is one of the links:
> http://forums.java.net/jive/thread.jspa?messageID=397805
>
> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480712
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

The last instructions seem to have solved the update problem, however, I still can not deploy the ear to any of the domains.

I get this:
[#|2010-08-23T20:35:37.812-0700|SEVERE|oracle-glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=42;_ThreadName=Thread-1;|Module type not recognized|#]

[#|2010-08-23T20:35:37.812-0700|SEVERE|oracle-glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=42;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
org.glassfish.deployment.common.DeploymentException

Caused by: java.lang.NullPointerException
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:638)
at org.glassfish.javaee.full.deployment.EarDeployer.prepareBundle(EarDeployer.java:269)
at org.glassfish.javaee.full.deployment.EarDeployer.access$200(EarDeployer.java:79)
at org.glassfish.javaee.full.deployment.EarDeployer$1.doBundle(EarDeployer.java:131)
at org.glassfish.javaee.full.deployment.EarDeployer$1.doBundle(EarDeployer.java:129)
at org.glassfish.javaee.full.deployment.EarDeployer.doOnBundles(EarDeployer.java:197)
at org.glassfish.javaee.full.deployment.EarDeployer.doOnAllBundles(EarDeployer.java:248)
at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:129)
... 63 more
|#]

According to the application.xml xsd javaModule should be allowed - is this not the case?


server.base.dao-1.0.1-SNAPSHOT.jar

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

FWIW - all I am really trying to do is include a "utility jar" in my ear. This is a jar that includes some base classes, interfaces, etc that one of the EJB's needs. This worked fine in GF v2, so I am at a loss. Additionally, I have ensured that the classpath entry is in my manifest.

tjquinn
Offline
Joined: 2005-03-30
Points: 0

You are telling GlassFish that your module is an app client module. A entry identifies app clients, not library JARs.

The spec, although large, is clear about this, and about how you can put library JARs in the EAR's /lib directory (or you can specify another directory within the EAR using the
element in your application.xml.

Remove the entry if it is not an app client. If I recall correctly GlassFish 3.1 no longer throws the NPE, but I think incorrectly identifying the library as an app client is the source of your problem.

- Tim

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

I see. After playing with it for some time I finally manually put the lib jar in a folder 'lib' in the ear. This worked, thanks!

Also, for anyone out there using Maven, this was my problem:
What I had:

someGroupName
someArtifactName
true

What I have now that works:

someGroupName
someArtifactName
lib

Snjezana Sevo-Zenzerovic

I see, but note that you did not apply updates, you actually installed
additional packages which were not present in your initial installation
and that eventually caused the problem...

Since you cannot apply updates from Admin console update section, you
need to run 'pkg image-update' command and this will upgrade your
installation from v3 to 3.0.1 (which is stable release, so everything
should work without glitch).

You should stop your domains before applying the update and restart them
afterwards. You may also want to clean up osgi-cache directories for
each domain which was running before restarting so that all OSGi bundles
get cleanly reloaded.

glassfish@javadesktop.org wrote:
> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>
> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>
> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
> org.glassfish.deployment.common.DeploymentException
>
> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>
> I think this is one of the links:
> http://forums.java.net/jive/thread.jspa?messageID=397805
>
> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480712
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Alexis Moussine-Pouchkine

if the updatetool (or the 'pkg' CLI) say there are no updates then you can safely consider this admin console message as a false positive (Snjezana would have the details).
As for the initial reason for the deployment failure, it does sound like you've installed the Web Profile which is unable to deal with EAR files.
A clean install of the Full Platform bundle for GlassFish 3.0.1 is something to try out (if you haven't already).
-Alexis

On 21 août 2010, at 00:56, glassfish@javadesktop.org wrote:

> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>
> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>
> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
> org.glassfish.deployment.common.DeploymentException
>
> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>
> I think this is one of the links:
> http://forums.java.net/jive/thread.jspa?messageID=397805
>
> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480712
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Snjezana Sevo-Zenzerovic

FWIW, this is in fact already full platform installation of v3 and
updates are available since as far as I can tell 3.0.1 updates were
never installed - at least at the time package listing was provided
couple of days ago.

Running 'pkg image-update' should take care of everything IMHO :-)

Alexis Moussine-Pouchkine wrote:
> if the updatetool (or the 'pkg' CLI) say there are no updates then you can safely consider this admin console message as a false positive (Snjezana would have the details).
> As for the initial reason for the deployment failure, it does sound like you've installed the Web Profile which is unable to deal with EAR files.
> A clean install of the Full Platform bundle for GlassFish 3.0.1 is something to try out (if you haven't already).
> -Alexis
>
> On 21 août 2010, at 00:56, glassfish@javadesktop.org wrote:
>
>
>> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>>
>> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>>
>> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
>> org.glassfish.deployment.common.DeploymentException
>>
>> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>>
>> I think this is one of the links:
>> http://forums.java.net/jive/thread.jspa?messageID=397805
>>
>> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
>> [Message sent by forum member 'javamonkey79']
>>
>> http://forums.java.net/jive/thread.jspa?messageID=480712
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Snjezana Sevo-Zenzerovic

FWIW, you probably run into this issue and need to install couple of
extra packages to get pkg and updatetool to work:

https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=1874

Snjezana Sevo-Zenzerovic wrote:
> Did updatetool work before, or were you using update section of Admin
> console to install packages?
> Also, what platform are you using?
>
> glassfish@javadesktop.org wrote:
>> You've given me hope that we might have to fix without a rebuild -
>> however, when I try to run the updatetool or pkg I get this:
>> intuser@glassfish01 /opt/glassfishv3/bin # sudo ./pkg
>> Traceback (most recent call last):
>> File "/opt/glassfishv3/pkg/bin/client.py", line 62, in ?
>> import pkg.client.api as api
>> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/api.py", line
>> 40, in ?
>> import pkg.client.image as image
>> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/image.py",
>> line 48, in ?
>> import pkg.client.transport.transport as transport
>> File
>> "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/transport.py",
>> line 40, in ?
>> import pkg.client.transport.engine as engine
>> File
>> "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/engine.py",
>> line 31, in ?
>> import pycurl
>> ImportError: libidn.so.11: cannot open shared object file: No such
>> file or directory
>>
>> Am I running it wrong, or is there a bug here?
>> [Message sent by forum member 'javamonkey79']
>>
>> http://forums.java.net/jive/thread.jspa?messageID=480520
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

Ok, I got the pkg command installed by running yum and installing the libidn. I also ran both of these:
sudo ./pkg uninstall glassfish-osgi-admin-console
sudo ./pkg uninstall glassfish-osgi-http

It kinda looked like it worked and I'm not seeing any complaints in the log anymore regarding those two bundles, however, I am seeing this still:

[#|2010-08-18T17:07:43.536-0700|WARNING|glassfishv3.0|org.jvnet.hk2.osgimain|_ThreadID=11;_ThreadName=Thread-1;|Exception while starting bundle com.sun.enterprise.osgi-adapter [45]
org.osgi.framework.BundleException: Activator start error in bundle com.sun.enterprise.osgi-adapter [45].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1751)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1622)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.jvnet.hk2.osgimain.Main.start(Main.java:140)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:640)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1700)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1622)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:636)
Caused by: com.sun.enterprise.module.ResolveError: Failed to start Bundle Id [19] State [INSTALLED] [org.glassfish.ha.shoal-cache-bootstrap(GlassFish ha-shoal-cache-bootstrap):3.1.0.b15]
at org.jvnet.hk2.osgiadapter.OSGiModuleImpl.start(OSGiModuleImpl.java:174)
at org.jvnet.hk2.osgiadapter.OSGiModuleImpl$2$1$1.loadClass(OSGiModuleImpl.java:341)
at com.sun.hk2.component.LazyInhabitant.fetch(LazyInhabitant.java:91)
at com.sun.hk2.component.LazyInhabitant.type(LazyInhabitant.java:78)
at com.sun.enterprise.v3.server.AppServerStartup$2.compare(AppServerStartup.java:439)
at com.sun.enterprise.v3.server.AppServerStartup$2.compare(AppServerStartup.java:437)
at java.util.PriorityQueue.siftUpUsingComparator(PriorityQueue.java:611)
at java.util.PriorityQueue.siftUp(PriorityQueue.java:589)
at java.util.PriorityQueue.offer(PriorityQueue.java:291)
at java.util.PriorityQueue.add(PriorityQueue.java:268)
at java.util.AbstractQueue.addAll(AbstractQueue.java:189)
at com.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:224)
at com.sun.enterprise.v3.server.AppServerStartup.start(AppServerStartup.java:128)
at com.sun.enterprise.module.bootstrap.Main.launch(Main.java:457)
at com.sun.enterprise.module.bootstrap.Main.launch(Main.java:401)
at org.jvnet.hk2.osgiadapter.HK2Main.start(HK2Main.java:125)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:640)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1700)
... 9 more
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.ha.shoal-cache-bootstrap [19]: package; (&(package=org.glassfish.api)(version>=3.1.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at org.jvnet.hk2.osgiadapter.OSGiModuleImpl.start(OSGiModuleImpl.java:166)
... 26 more
|#]

I'm guessing I need to also uninstall: org.glassfish.ha.shoal-cache-bootstrap

But I am not 100% sure and would rather be safe than sorry...

Message was edited by: javamonkey79

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

I uninstalled those 2 packages and am still having problems. Please see the exception post above.

Message was edited by: javamonkey79

Snjezana Sevo-Zenzerovic

It seems that you installed something else belonging to 3.1 release -
could you please run 'pkg list -f' command and attach the output?

glassfish@javadesktop.org wrote:
> I uninstalled those 2 packages and am still having problems. Please see the exception post below.
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480589
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

intuser@glassfish01 /opt/glassfishv3/bin # sudo ./pkg list -f
NAME (PUBLISHER) VERSION STATE UFIX
ant (contrib.glassfish.org) 1.7.1-0.6 installed ----
felix 2.0.2-0 installed u---
glassfish-ant-tasks (dev.glassfish.org) 3.1-15 installed ----
glassfish-appclient 3.0-74.2 installed u---
glassfish-branding (release.glassfish.sun.com) 3.0-74.2 installed u---
glassfish-branding-gui (release.glassfish.sun.com) 3.0-74.2 installed u---
glassfish-cluster (dev.glassfish.org) 3.1-15 installed ----
glassfish-cluster-util (contrib.glassfish.org) 1.0-0.0 installed ----
glassfish-cmp 3.0-74.2 installed u---
glassfish-common 3.0-74.2 installed u---
glassfish-common-full 3.0-74.2 installed u---
glassfish-common-full-l10n 3.0.1-20.1 installed ----
glassfish-common-l10n 3.0.1-20.1 installed ----
glassfish-corba 3.0.0-41 installed u---
glassfish-corba-base 3.0.0-41 installed u---
glassfish-docs (release.glassfish.sun.com) 3.0.5-3 installed ----
glassfish-ejb 3.0-74.2 installed u---
glassfish-ejb-l10n 3.0.1-20.1 installed ----
glassfish-ejb-lite 3.0-74.2 installed u---
glassfish-ejb-lite-l10n 3.0.1-20.1 installed ----
glassfish-enterprise-full-profile (release.glassfish.sun.com) 3.0-74.2 installed u---
glassfish-enterprise-web-profile (release.glassfish.sun.com) 3.0-74.2 installed u---
glassfish-full-incorporation 3.0-74.2 installed u---
glassfish-full-profile 3.0-74.2 installed u---
glassfish-generic-ra (dev.glassfish.org) 2.0-0.0 installed ----
glassfish-grizzly 1.9.18-9 installed u---
glassfish-grizzly-full 1.9.18-9 installed u---
glassfish-gui 3.0-74.2 installed u---
glassfish-gui-l10n 3.0.1-20.1 installed ----
glassfish-ha (dev.glassfish.org) 3.1-15 installed ----
glassfish-hk2 3.0-74.2 installed u---
glassfish-javahelp 2.0.2-0 installed u---
glassfish-jca 3.0-74.2 installed u---
glassfish-jca-l10n 3.0.1-20.1 installed ----
glassfish-jcdi 3.0-74.2 installed u---
glassfish-jdbc 3.0-74.2 installed u---
glassfish-jdbc-l10n 3.0.1-20.1 installed ----
glassfish-jms 3.0-74.2 installed u---
glassfish-jms-l10n 3.0.1-20.1 installed ----
glassfish-jpa 3.0-74.2 installed u---
glassfish-jsf 2.0.2-10 installed u---
glassfish-jta 3.0-74.2 installed u---
glassfish-jts 3.0-74.2 installed u---
glassfish-jts-l10n 3.0.1-20.1 installed ----
glassfish-management 3.0-74.2 installed u---
glassfish-monitoring-scripting-client (release.glassfish.sun.com) 3.0-0 installed ----
glassfish-nucleus 3.0-74.2 installed u---
glassfish-nucleus-l10n 3.0.1-20.1 installed ----
glassfish-registration 3.0-74.2 installed u---
glassfish-scripting 3.0-74.2 installed u---
glassfish-scripting-l10n 3.0.1-20.1 installed ----
glassfish-upgrade 3.0-74.2 installed u---
glassfish-upgrade-l10n 3.0.1-20.1 installed ----
glassfish-verifier (dev.glassfish.org) 3.1-15 installed ----
glassfish-web 3.0-74.2 installed u---
glassfish-web-incorporation 3.0-74.2 installed u---
glassfish-web-l10n 3.0.1-20.1 installed ----
glassfish-web-profile 3.0-74.2 installed u---
grails (contrib.glassfish.org) 1.1.2-1.0 installed ----
hibernate (contrib.glassfish.org) 3.5.0-0.3 installed ----
javadb-client 10.5.3.0-1 installed ----
javadb-common 10.5.3.0-1 installed ----
javadb-core 10.5.3.0-1 installed ----
javadb-demo 10.5.3.0-1 installed ----
javadb-doc 10.5.3.0-1 installed ----
javadb-javadoc 10.5.3.0-1 installed ----
javaee-firstcup-tutorial (release.glassfish.sun.com) 2.0.1-6 installed ----
javaee-javadocs (release.glassfish.sun.com) 3.0-74.2 installed ----
javaee-samples-build (release.glassfish.sun.com) 0.9-16 installed ----
javaee-samples-full (release.glassfish.sun.com) 0.9-16 installed ----
javaee-samples-web (release.glassfish.sun.com) 0.9-16 installed ----
javaee-sdk-full-profile (release.glassfish.sun.com) 3.0-74.2 installed ----
javaee-sdk-web-profile (release.glassfish.sun.com) 3.0-74.2 installed ----
javaee-tutorial (release.glassfish.sun.com) 6.0.4-2 installed ----
jersey (dev.glassfish.org) 1.2-1.0 installed u---
jersey-docs-and-examples (dev.glassfish.org) 1.2-1.0 installed ----
jmaki (contrib.glassfish.org) 1.8.1-2.0 installed ----
jruby (contrib.glassfish.org) 1.4.0-1.0 installed ----
jruby-gems (contrib.glassfish.org) 2.3.5-1.0 installed ----
jython-container (contrib.glassfish.org) 0.5.6-1.1 installed ----
jython-runtime (contrib.glassfish.org) 2.5.1-1.0 installed ----
metro 2.0-29 installed u---
mq-bin-exe 4.4.1-7.2 installed u---
mq-bin-sh 4.4.1-7.2 installed u---
mq-branding (release.glassfish.sun.com) 4.4.1-7.2 installed u---
mq-capi (release.glassfish.sun.com) 4.4.2-5.1 installed ----
mq-config-gf 4.4.1-7.2 installed u---
mq-core (dev.glassfish.org) 4.5-12.2 installed ----
mq-docs (dev.glassfish.org) 4.5-12.2 installed ----
mq-locale (dev.glassfish.org) 4.5-12.2 installed ----
mq-server 4.4.1-7.2 installed u---
nss-libs (release.glassfish.sun.com) 3.12.6-1.0 installed ----
nss-utils (release.glassfish.sun.com) 3.12.6-1.0 installed ----
pkg 1.122.2-38.2791 installed ----
pkg-extra-tools 0.2.0-38.2791 installed ----
pkg-java 1.122-38.2493 installed u---
pkg-toolkit 2.3.2-38.2791 installed ----
pkg-toolkit-incorporation 2.3.2-38.2791 installed ----
python2.4-minimal 2.4.4.0-38.2791 installed ----
sdk-branding-full (release.glassfish.sun.com) 3.0-74.2 installed ----
sdk-branding-web (release.glassfish.sun.com) 3.0-74.2 installed ----
shoal (dev.glassfish.org) 1.5.6-0 installed ----
sun-javaee-engine (dev.glassfish.org) 3.1-15 installed ----
updatetool 2.3.2-38.2791 installed ----
wxpython2.8-minimal 2.8.10.1-38.2791 installed ----

Snjezana Sevo-Zenzerovic

You will need to uninstall most packages with version 3.1-15 which were
installed from dev.glassfish.org repository , i.e.

glassfish-cluster
glassfish-ha
glassfish-verifier
shoal
sun-javaee-engine

This should bring your runtime back to the original state. If you really
do require glassfish-verifier, you can explicitly install one
corresponding to your installation version using this command:

pkg install glassfish-verifier@3.0-74.2

Other packages from the list are newly introduced in 3.1 release and
have no function in the context of your v3 installation, so you can just
leave them off.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

I watched the logs and removed the offending bundles. All in all this is what was removed:
767 sudo ./pkg uninstall glassfish-osgi-admin-console
768 sudo ./pkg uninstall glassfish-osgi-http
818 sudo ./pkg uninstall glassfish-ant-tasks
819 sudo ./pkg uninstall glassfish-cluster
820 sudo ./pkg uninstall glassfish-verifier
821 sudo ./pkg uninstall glassfish-cluster
822 sudo ./pkg uninstall glassfish-ha
823 sudo ./pkg uninstall glassfish-cluster
826 sudo ./pkg uninstall shoal

Once removed the domain started, yea! It did complain a little about some bundle being in an unexpected state. I restarted the domain again and it did not complain and started pretty quick.

Thanks for your timely help!

Snjezana Sevo-Zenzerovic

You are welcome - I forgot to mention that you may need to clean up the
content of osgi cache directory in your domain configuration directory
so that bundles can be cleanly loaded but if you are seeing no issues in
the second restart you should be fine...

I'll restrict package dependencies in such a way that it won't be that
easy to get into this kind of trouble, but as a general rule, you should
not install extra packages on the production server without a good
reason :-)

glassfish@javadesktop.org wrote:
> I watched the logs and removed the offending bundles. All in all this is what was removed:
> 767 sudo ./pkg uninstall glassfish-osgi-admin-console
> 768 sudo ./pkg uninstall glassfish-osgi-http
> 818 sudo ./pkg uninstall glassfish-ant-tasks
> 819 sudo ./pkg uninstall glassfish-cluster
> 820 sudo ./pkg uninstall glassfish-verifier
> 821 sudo ./pkg uninstall glassfish-cluster
> 822 sudo ./pkg uninstall glassfish-ha
> 823 sudo ./pkg uninstall glassfish-cluster
> 826 sudo ./pkg uninstall shoal
>
> Once removed the domain started, yea! It did complain a little about some bundle being in an unexpected state. I restarted the domain again and it did not complain and started pretty quick.
>
> Thanks for your timely help!
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480609
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:

[#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]

[#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
org.glassfish.deployment.common.DeploymentException

Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.

I think this is one of the links:
http://forums.java.net/jive/thread.jspa?messageID=397805

I believe this to be the offending piece of the application.xml:


server.base.dao-1.0.1-SNAPSHOT.jar

What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?

Message was edited by: javamonkey79

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

Should I start a new post for this issue? I am not familiar with the particulars of this forum. TIA

snjezana
Offline
Joined: 2005-02-15
Points: 0

No, you don't necessarily need to start new post, IMO, it is still related to your original issue. That being said, I see that couple of follow-up posts by Alexis and myself which show up on users@glassfish.dev.java.net mailing list did not make it to the forum. I'll dig them up and post them manually.

snjezana
Offline
Joined: 2005-02-15
Points: 0

Missing post #1

From: Alexis Moussine-Pouchkine
Date: Sat, 21 Aug 2010 00:49:23 +0200
Subject: Update Tool Causes Death to Domain

if the updatetool (or the 'pkg' CLI) say there are no updates then you can safely consider this admin console message as a false positive (Snjezana would have the details).
As for the initial reason for the deployment failure, it does sound like you've installed the Web Profile which is unable to deal with EAR files.
A clean install of the Full Platform bundle for GlassFish 3.0.1 is something to try out (if you haven't already).
-Alexis

On 21 août 2010, at 00:56, glassfish@javadesktop.org wrote:

> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>
> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>
> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
> org.glassfish.deployment.common.DeploymentException
>
> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>
> I think this is one of the links:
> http://forums.java.net/jive/thread.jspa?messageID=397805
>
> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480712
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

snjezana
Offline
Joined: 2005-02-15
Points: 0

Missing post #3

Date: Fri, 20 Aug 2010 15:58:15 -0700
From: Snjezana Sevo-Zenzerovic
Subject: Update Tool Causes Death to Domain

FWIW, this is in fact already full platform installation of v3 and
updates are available since as far as I can tell 3.0.1 updates were
never installed - at least at the time package listing was provided
couple of days ago.

Running 'pkg image-update' should take care of everything IMHO :-)

Alexis Moussine-Pouchkine wrote:
> if the updatetool (or the 'pkg' CLI) say there are no updates then you can safely consider this admin console message as a false positive (Snjezana would have the details).
> As for the initial reason for the deployment failure, it does sound like you've installed the Web Profile which is unable to deal with EAR files.
> A clean install of the Full Platform bundle for GlassFish 3.0.1 is something to try out (if you haven't already).
> -Alexis
>
> On 21 août 2010, at 00:56, glassfish@javadesktop.org wrote:
>
>
>> The whole reason I was trying to apply the updates was I am getting this when trying to deploy an ear:
>>
>> [#|2010-08-20T15:26:44.519-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Module type not recognized|#]
>>
>> [#|2010-08-20T15:26:44.520-0700|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-1;|Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
>> org.glassfish.deployment.common.DeploymentException
>>
>> Most forum posts I read (and I think there is a bug for this) indicate updating to a later version of GF.
>>
>> I think this is one of the links:
>> http://forums.java.net/jive/thread.jspa?messageID=397805
>>
>> What strikes me as odd, is that I have restarted all domains yet I still see the attached screenshot in the admin console. Do the updates require a server reboot?
>> [Message sent by forum member 'javamonkey79']
>>
>> http://forums.java.net/jive/thread.jspa?messageID=480712
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

Snjezana Sevo-Zenzerovic

It seems that you installed Felix web console package on top of your
GlassFish installation and this package works only with recent GlassFish
3.1 builds and not with the original GlassFish v3 - unfortunately,
package version dependencies are not enforced strictly enough and this
will get fixed.

Things should get back to normal if you run updatetool and uninstall
glassfish-osgi-http and glassfish-osgi-admin-console packages.

glassfish@javadesktop.org wrote:
> After running the update tool on a test domain I was not able to get it to start.
>
> The version from the admin page shows: GlassFish v3 (build 74.2) but I'm not sure that is right, since the other prod domains have not been restarted.
>
> After building the new domain, I ran the update tool. I then shut the domain down. When I attemped to start it - it times out.
>
> A review of the server.log looks as though there is a dependency problem in one of the OSGi bundles:
>
> [#|2010-08-17T15:41:20.538-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]
>
> [#|2010-08-17T15:41:20.538-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
> |#]
>
> [#|2010-08-17T15:41:25.541-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/osgi-http.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]
>
> [#|2010-08-17T15:41:25.542-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
> |#]
>
> [#|2010-08-17T15:41:25.542-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|Error while starting bundle: file:/opt/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.jar: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))|#]
>
> [#|2010-08-17T15:41:25.543-0700|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=12;_ThreadName=Thread-1;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.osgi-http [279]: package; (&(package=com.sun.enterprise.config.serverbeans)(version>=3.1.0))
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1027)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1013)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1006)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:396)
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:206)
> |#]
>
>
> Does anyone out there know how to resolve this? We really like some elements of GFv3 - but this could be a game changer for us. If we have to rebuild the server (again) I don't think we'll use GFv3.
>
> TIA
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480513
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

You've given me hope that we might have to fix without a rebuild - however, when I try to run the updatetool or pkg I get this:
intuser@glassfish01 /opt/glassfishv3/bin # sudo ./pkg
Traceback (most recent call last):
File "/opt/glassfishv3/pkg/bin/client.py", line 62, in ?
import pkg.client.api as api
File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/api.py", line 40, in ?
import pkg.client.image as image
File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/image.py", line 48, in ?
import pkg.client.transport.transport as transport
File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/transport.py", line 40, in ?
import pkg.client.transport.engine as engine
File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/engine.py", line 31, in ?
import pycurl
ImportError: libidn.so.11: cannot open shared object file: No such file or directory

Am I running it wrong, or is there a bug here?

Snjezana Sevo-Zenzerovic

Did updatetool work before, or were you using update section of Admin
console to install packages?
Also, what platform are you using?

glassfish@javadesktop.org wrote:
> You've given me hope that we might have to fix without a rebuild - however, when I try to run the updatetool or pkg I get this:
> intuser@glassfish01 /opt/glassfishv3/bin # sudo ./pkg
> Traceback (most recent call last):
> File "/opt/glassfishv3/pkg/bin/client.py", line 62, in ?
> import pkg.client.api as api
> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/api.py", line 40, in ?
> import pkg.client.image as image
> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/image.py", line 48, in ?
> import pkg.client.transport.transport as transport
> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/transport.py", line 40, in ?
> import pkg.client.transport.engine as engine
> File "/opt/glassfishv3/pkg/vendor-packages/pkg/client/transport/engine.py", line 31, in ?
> import pycurl
> ImportError: libidn.so.11: cannot open shared object file: No such file or directory
>
> Am I running it wrong, or is there a bug here?
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480520
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

javamonkey79
Offline
Joined: 2010-06-17
Points: 0

I used the update tool in the command console.

We're using CentOS

Here is most of the uname -a dump:
Linux glassfish01.company.com 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:32:21 EST 2010 x86_64 x86_64 x86_64 GNU/Linux

Snjezana Sevo-Zenzerovic

CentOS is RPM based, right? See my previous message, I think you need to
install same 32-bit libidn support packages as those documented for
RedHat distributions...

glassfish@javadesktop.org wrote:
> I used the update tool in the command console.
>
> We're using CentOS
>
> Here is most of the uname -a dump:
> Linux glassfish01.company.com 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:32:21 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
> [Message sent by forum member 'javamonkey79']
>
> http://forums.java.net/jive/thread.jspa?messageID=480523
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

--
Oracle
Snjezana Sevo-Zenzerovic

Green Oracle Oracle is committed to
developing practices and products that help protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net