Bug 6760 - GlassFish Package (glassfishv2) is Missing JDMK Dependency
: GlassFish Package (glassfishv2) is Missing JDMK Dependency
Status: ACCEPTED
Product: opensolaris
packaging
: 200811
: ANY/Generic OpenSolaris
: P2 major (vote)
: ---
Assigned To: osol/packaging watcher
: osol/packaging watcher
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-02-19 06:44 UTC by Brian Leonard
Modified: 2009-03-23 15:11 UTC (History)
2 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Brian Leonard 2009-02-19 06:44:18 UTC
If you install GlassFish (glassfishv2) and create a domain using the cluster
profile (the most common profile for production use), e.g.:

$ pfexec asadmin create-domain --user admin --adminport 4848 --profile cluster
domain1

The domain will fail to start with the exception:

java.lang.ClassNotFoundException:
com.sun.jdmk.remote.cascading.proxy.ProxyCascadingAgent

Which is a class found in the SUNWjdmk-base package. However, installing this
package doesn't immediately solve the problem. GlassFish expects to find the
jar files in 

/opt/SUNWjdmk/5.1/lib

but the SUNWjdmk-base package installs them in

/usr/share/lib/jdmk

However, editing the AS_JDMK_HOME variable in 

/usr/appserver/config/asenv.conf 

to point to /usr/share/lib/jdmk doesn't solve the problem either, because
GlassFish appends the 'lib' directory to the AS_JDMK_HOME variable in 

/usr/appserver/lib/processLauncher.xml

So you then need to create a link for lib in /usr/share/lib/jdmk/.

Not a pretty picture.

In summary, the work around steps are to:

1) pfexec pkg install SUWjdmk-base
2) Set AS_JDMK_HOME in /usr/appserver/config/asenv.conf to /usr/share/lib/jdmk 
3) cd /usr/share/lib/jdmk
4) ln -s . lib

I guess alternatively, you could create a link in /opt/SUNWjdmk/5.1/lib
pointing to /usr/share/lib/jdmk, which would save you from editing the
asenv.conf file.
Comment 1 Rich Burridge 2009-03-23 10:23:19 UTC
Triaging. Moving to "packaging" for further evaluation.
Comment 2 Rich Burridge 2009-03-23 14:28:58 UTC
Hi Brian,

We can probably work around this by adding a symbolic link in the IPS
package definition file for the SUNWjdmk-base package, but we'd also
like to get it fixed "at the source". I.e. in the SVR4 package(s) that
the OpenSolaris release uses.

Where should I file a GlassFish bug to make this happen?

Thanks.
Comment 3 Brian Leonard 2009-03-23 14:48:23 UTC
Hi Rich,

You can submit the GlassFish bug at: 

https://glassfish.dev.java.net/servlets/ProjectIssues

Regards,
Brian
Comment 4 Rich Burridge 2009-03-23 15:11:53 UTC
Thanks Brian. I've opened:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=7423

Leaving this one open as I expect we'll try to work around the problem(s)
with changes to the IPS definition files for the glassfish-v2 and 
SUNWjdmk-base packages.