JDMK + JMX 1.0 compatability

Hi,
I have to use JDMK lib with weblogic 8.1. But Weblogic uses JMX 1.0 So facing incompatibility issue. Could any body give a suggestion how to overcome this issue.
Thank you.

Thanks for your reply.
But my problem is weblogic is using JMX 1.0 But My uplication is using JDMK jar which needs JMX 1.1 or above. How do I achieve this. It tried to overide the JMX classes of weblogic from an external jar. But in that case weblogic doesn't start, it fails while launching.
Thanks
Deepak

Similar Messages

Unable to register system with sconadm

I'm trying to get smpatch working within my environment so I can get our patch management/automation under control. I've been able to successfully get this working on 1 system. When attempting to get this working on a second system, I have had nothing but issues. Any help with this would be greatly appreciated.
1. I have followed both ID 1288579.1 and ID 1311733.1 to a T.
2. I do have a valid MOS account, and to take it a step further, I have had my account set to Admin on the support contract I have.
3. I've verified that my account can download patches. I tested with PCA and it can retrieve patches without issue with me account.
4. my suc.sh output:
| Sun Update Collector V 1.0.10 |
Solaris release:
Solaris 10 10/08 s10x_u6wos_07b X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 27 October 2008
Solaris Kernel: Generic_137138-09
Machine Type: i86pc
Platform: i86pc
Software Cluster:
CLUSTER=SUNWCall
Environment:
HOME=/
HZ=
LOGNAME=root
MAIL=/var/mail/root
OLDPWD=/usr/jdk
PATH=/usr/sbin:/usr/bin
PWD=/export/home/bbranch
SHELL=/sbin/sh
SHLVL=1
TERM=vt100
TZ=US/Central
_=./suc.sh
Sun UC package status:
SUNWbreg not installed
SUNWdc not installed
Sun UC package information:
Sun UC package chk:
..done..
Sun UC patch revision:
120336-04
121082-06
121082-08
121119-13
121119-19
121454-02
123004-03
123004-04
123006-07
123006-09
123631-03
123896-05
123896-25
124187-07
137138-09
Patch install dates:
Note: The dates listed and patches listed may differ due to patches included with the OS release installed.
drwxr-xr-- 2 root root 512 2011-09-21 13:47:44.093500000 -0500 121082-08
drwxr-xr-- 2 root root 512 2011-09-21 11:04:00.643649000 -0500 121119-19
drwxr-xr-- 2 root root 512 2011-09-21 13:04:38.208182000 -0500 123004-04
drwxr-xr-- 2 root root 512 2011-09-21 11:04:23.198060000 -0500 123006-09
drwxr-xr-- 2 root root 512 2011-09-21 11:11:22.682756000 -0500 123896-25
Java versions:
System default:
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)
Java 5:
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)
Java 6:
Unable to locate JRE meeting specification "1.6*"
Java used by smpatch and updatemanager:
/usr/sbin/pprosvc:JAVACMD="/usr/jdk/latest/bin/java -version:1.5+"
/bin/updatemanager:JAVA_EXEC="/usr/jdk/latest/bin/java -version:1.5+"
Cacao Java version:
java-home=/usr/jdk/latest
Cacao Base Directories:
cacao.install.rt.base.dir=/
cacao.install.etc.base.dir=/
Cacao all settings:
snmp-adaptor-port=11161
snmp-adaptor-trap-port=11162
jmxmp-connector-port=11162
commandstream-adaptor-port=11163
rmi-registry-port=11164
secure-webserver-port=11165
java-flags= -Xmx128M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8 -Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed
micro-agent=false
java-home=/usr/jdk/latest
jdmk-home=/usr/share/lib/jdmk
nss-lib-home=/usr/lib/mps/secv1
nss-tools-home=/usr/sfw/bin
retries=4
log-file-limit=1000000
log-file-count=3
log-file-append=true
enable-instrumentation=false
user=root
group=sys
network-bind-address=127.0.0.1
watchdog-heartbeat-timeout=60
Cacao Modules:
List of modules registered:
com.sun.cacao.agent_logging 1.0
com.sun.cacao.cached_connector 2.2
com.sun.cacao.command_stream_adaptor 1.0
com.sun.cacao.dtrace 1.0
com.sun.cacao.efd 2.2
com.sun.cacao.instrum 1.0
com.sun.cacao.invoker 1.0
com.sun.cacao.mib2simple 1.0
com.sun.cacao.rbac 2.1
com.sun.cacao.rmi 1.0
com.sun.cacao.session 2.2
com.sun.cacao.snmpv3_adaptor 1.0
com.sun.cacao.watchdog.heartbeat 1.0
com.sun.cacao.watchdog.probe 1.0
com.sun.scn.SolarisAssetModule 1.0
com.sun.scn.base.SCNBase 1.0
com.sun.scn.offering.ProductRegistration 1.0
com.sun.scn.offering.SoftwareUpdate 1.0
com.sun.scn.sensor.Sensor_Module 1.0
ls Cacao directories:
/etc/cacao/instances/default:
total 6
drwxr-xr-x 2 root sys 512 Sep 21 13:04 modules
drwxr-xr-x 3 root sys 512 Sep 21 11:11 private
drwxr-xr-x 5 root sys 512 Sep 21 10:12 security
/etc/cacao/instances/default/modules:
total 24
-rw-r----- 1 root sys 2581 Mar 27 2006 com.sun.scn.base.SCNBase.xml
-rw-r----- 1 root sys 2921 Dec 3 2007 com.sun.scn.offering.ProductRegistration.xml
-rw-r--r-- 1 root sys 2789 Dec 3 2007 com.sun.scn.offering.SWUPRegistration.xml
-rw-r----- 1 root sys 1307 Mar 17 2010 com.sun.scn.sam.SolarisAssetModule.xml
-rw-r----- 1 root sys 1010 Mar 16 2006 com.sun.scn.sensor.Sensor_Module.xml
/etc/cacao/instances/default/private:
total 26
-rw-r--r-- 1 root sys 5386 Sep 22 09:57 cacao.properties
-rw-r--r-- 1 root sys 559 Sep 21 10:12 logger.properties
drwxr-xr-x 2 root sys 3072 Sep 21 11:11 modules
-rw-r--r-- 1 root sys 2196 Sep 21 11:11 svc_cacao.xml
/etc/cacao/instances/default/private/modules:
total 82
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.auth.session.2.2.2.properties
-rw-r--r-- 1 root sys 1435 Sep 21 11:11 com.sun.cacao.auth.session.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.cached_connector.2.2.2.properties
-rw-r--r-- 1 root sys 1033 Sep 21 11:11 com.sun.cacao.cached_connector.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.command_stream_adaptor.2.2.2.properties
-rw-r--r-- 1 root sys 1005 Sep 21 11:11 com.sun.cacao.command_stream_adaptor.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 10:12 com.sun.cacao.dtrace.properties
-rw-r--r-- 1 root sys 957 Sep 21 10:12 com.sun.cacao.dtrace.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.efd.2.2.2.properties
-rw-r--r-- 1 root sys 1115 Sep 21 11:11 com.sun.cacao.efd.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.instrum.2.2.2.properties
-rw-r--r-- 1 root sys 1025 Sep 21 11:11 com.sun.cacao.instrum.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.invoker.2.2.2.properties
-rw-r--r-- 1 root sys 1086 Sep 21 11:11 com.sun.cacao.invoker.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.logging_manager.2.2.2.properties
-rw-r--r-- 1 root sys 903 Sep 21 11:11 com.sun.cacao.logging_manager.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.mib2simple.2.2.2.properties
-rw-r--r-- 1 root sys 2816 Sep 21 11:11 com.sun.cacao.mib2simple.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.rbac.2.2.2.properties
-rw-r--r-- 1 root sys 1295 Sep 21 11:11 com.sun.cacao.rbac.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.rmi.2.2.2.properties
-rw-r--r-- 1 root sys 960 Sep 21 11:11 com.sun.cacao.rmi.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.snmpv3_adaptor.2.2.2.properties
-rw-r--r-- 1 root sys 2049 Sep 21 11:11 com.sun.cacao.snmpv3_adaptor.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.watchdog.heartbeat.2.2.2.properties
-rw-r--r-- 1 root sys 2559 Sep 21 11:11 com.sun.cacao.watchdog.heartbeat.2.2.2.xml
-rw-r--r-- 1 root sys 56 Sep 21 11:11 com.sun.cacao.watchdog.probe.2.2.2.properties
-rw-r--r-- 1 root sys 1757 Sep 21 11:11 com.sun.cacao.watchdog.probe.2.2.2.xml
/etc/cacao/instances/default/security:
total 8
drwxr-xr-x 2 root sys 512 Sep 21 10:12 jsse
drwxr-xr-x 5 root sys 512 Sep 21 10:12 nss
-rw------- 1 root sys 197 Sep 21 10:12 password
drwxr-xr-x 2 root sys 512 Sep 22 09:57 snmp
/etc/cacao/instances/default/security/jsse:
total 8
-rw-r--r-- 1 root sys 639 Sep 21 10:12 agent.cert
-rw-r--r-- 1 root sys 1630 Sep 21 10:12 keystore
-rw-r--r-- 1 root sys 486 Sep 21 10:12 truststore
/etc/cacao/instances/default/security/nss:
total 6
drwxr-xr-x 2 root sys 512 Sep 21 10:12 localca
drwxr-xr-x 2 root sys 512 Sep 21 10:12 unknown
drwxr-xr-x 2 root sys 512 Sep 21 10:12 wellknown
/etc/cacao/instances/default/security/nss/localca:
total 226
-rw-r--r-- 1 root sys 65536 Sep 21 10:12 cert8.db
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 key3.db
-rw-r--r-- 1 root sys 635 Sep 21 10:12 localca.cert
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 secmod.db
/etc/cacao/instances/default/security/nss/unknown:
total 208
-rw-r--r-- 1 root sys 65536 Sep 21 10:12 cert8.db
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 key3.db
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 secmod.db
/etc/cacao/instances/default/security/nss/wellknown:
total 226
-rw-r--r-- 1 root sys 65536 Sep 21 10:12 cert8.db
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 key3.db
-rw-r--r-- 1 root sys 32768 Sep 21 10:12 secmod.db
-rw-r--r-- 1 root sys 643 Sep 21 10:12 wellknown.cert
/etc/cacao/instances/default/security/snmp:
total 8
-rw------- 1 root sys 884 Sep 21 10:12 jdmk.acl
-rw------- 1 root sys 1110 Sep 22 09:57 jdmk.security
-rw------- 1 root sys 664 Sep 21 10:12 jdmk.uacl
/usr/lib/cacao/lib/tools/template:
total 8
drwxr-xr-x 5 root sys 512 Sep 21 09:49 config
drwxr-xr-x 2 root sys 1536 Sep 21 11:11 modules
drwxr-xr-x 2 root sys 512 Sep 21 11:11 startup
/usr/lib/cacao/lib/tools/template/config:
total 6
drwxr-xr-x 2 root sys 512 Sep 21 09:49 modules
drwxr-xr-x 3 root sys 512 Sep 21 11:11 private
drwxr-xr-x 3 root sys 512 Sep 21 09:49 security
/usr/lib/cacao/lib/tools/template/config/modules:
total 0
/usr/lib/cacao/lib/tools/template/config/private:
total 16
-rw-r--r-- 1 root sys 6045 Dec 7 2010 cacao.properties
-rw-r--r-- 1 root sys 565 Dec 7 2010 logger.properties
drwxr-xr-x 2 root sys 512 Sep 21 09:49 modules
/usr/lib/cacao/lib/tools/template/config/private/modules:
total 0
/usr/lib/cacao/lib/tools/template/config/security:
total 2
drwxr-xr-x 2 root sys 512 Sep 21 11:11 snmp
/usr/lib/cacao/lib/tools/template/config/security/snmp:
total 6
-rw-r--r-- 1 root sys 896 Dec 7 2010 jdmk.acl
-rw-r--r-- 1 root sys 1005 Dec 7 2010 jdmk.security
-rw-r--r-- 1 root sys 680 Dec 7 2010 jdmk.uacl
/usr/lib/cacao/lib/tools/template/modules:
total 54
-rw-r--r-- 1 root sys 1435 Dec 7 2010 com.sun.cacao.auth.session.2.2.2.xml
-rw-r--r-- 1 root sys 1033 Dec 7 2010 com.sun.cacao.cached_connector.2.2.2.xml
-rw-r--r-- 1 root sys 1005 Dec 7 2010 com.sun.cacao.command_stream_adaptor.2.2.2.xml
-rw-r--r-- 1 root sys 957 Feb 15 2007 com.sun.cacao.dtrace.xml
-rw-r--r-- 1 root sys 1115 Dec 7 2010 com.sun.cacao.efd.2.2.2.xml
-rw-r--r-- 1 root sys 1025 Dec 7 2010 com.sun.cacao.instrum.2.2.2.xml
-rw-r--r-- 1 root sys 1086 Dec 7 2010 com.sun.cacao.invoker.2.2.2.xml
-rw-r--r-- 1 root sys 903 Dec 7 2010 com.sun.cacao.logging_manager.2.2.2.xml
-rw-r--r-- 1 root sys 2816 Dec 7 2010 com.sun.cacao.mib2simple.2.2.2.xml
-rw-r--r-- 1 root sys 1295 Dec 7 2010 com.sun.cacao.rbac.2.2.2.xml
-rw-r--r-- 1 root sys 960 Dec 7 2010 com.sun.cacao.rmi.2.2.2.xml
-rw-r--r-- 1 root sys 2049 Dec 7 2010 com.sun.cacao.snmpv3_adaptor.2.2.2.xml
-rw-r--r-- 1 root sys 2559 Dec 7 2010 com.sun.cacao.watchdog.heartbeat.2.2.2.xml
-rw-r--r-- 1 root sys 1757 Dec 7 2010 com.sun.cacao.watchdog.probe.2.2.2.xml
/usr/lib/cacao/lib/tools/template/startup:
total 14
-rw-r--r-- 1 root sys 3770 Dec 7 2010 cacao
-rw-r--r-- 1 root sys 2164 Dec 7 2010 svc_cacao.xml
checking Cacao ports:
*.111 Idle
127.0.0.1.11161 Idle
*.111 *.* 0 0 49152 0 LISTEN
127.0.0.1.11164 *.* 0 0 49152 0 LISTEN
127.0.0.1.11163 *.* 0 0 49152 0 LISTEN
127.0.0.1.11162 *.* 0 0 49152 0 LISTEN
checking Cacao java process:
root 3225 0.3 4.011263241060 ? S 09:57:06 0:03 /usr/jdk/latest/bin/java -Xmx128M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8 -Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed -classpath /usr/share/lib/jdmk/jdmkrt.jar:/usr/share/lib/jdmk/jmxremote_optional.jar:/usr/lib/cacao/lib/cacao_cacao.jar:/usr/lib/cacao/lib/cacao_j5core.jar:/usr/lib/cacao/lib/bcprov-jdk14.jar -Djavax.management.builder.initial=com.sun.jdmk.JdmkMBeanServerBuilder -Dcacao.print.status=true -Dcacao.config.dir=/etc/cacao/instances/default -Dcacao.monitoring.mode=smf -Dcom.sun.cacao.ssl.keystore.password.file=/etc/cacao/instances/default/security/password com.sun.cacao.container.impl.ContainerPrivate
root 1325 0.2 1.68425216216 ? S 09:42:59 0:02 /usr/jdk/latest/bin/java -version:1.5+ -jar /usr/lib/patch/swupna.jar -wait
noaccess 710 0.1 11.6196796119900 ? S 09:08:02 0:13 /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 -classpath /usr/share/webconsole/private/container/bin/bootstrap.jar:/usr/share/webconsole/private/container/bin/commons-logging.jar:/usr/share/webconsole/private/container/bin/log4j.jar:/usr/java/lib/tools.jar:/usr/java/jre/lib/jsse.jar -Djava.security.manager -Djava.security.policy==/var/webconsole/domains/console/conf/console.policy -Djavax.net.ssl.trustStore=/var/webconsole/domains/console/conf/keystore.jks -Djava.security.auth.login.config=/var/webconsole/domains/console/conf/consolelogin.conf -Dcatalina.home=/usr/share/webconsole/private/container -Dcatalina.base=/var/webconsole/domains/console -Dcom.sun.web.console.home=/usr/share/webconsole -Dcom.sun.web.console.conf=/etc/webconsole/console -Dcom.sun.web.console.base=/var/webconsole/domains/console -Dcom.sun.web.console.logdir=/var/log/webconsole/console -Dcom.sun.web.console.native=/usr/lib/webconsole -Dcom.sun.web.console.appbase=/var/webconsole/domains/console/webapps -Dcom.sun.web.console.secureport=6789 -Dcom.sun.web.console.unsecureport=6788 -Dcom.sun.web.console.unsecurehost=127.0.0.1 -Dwebconsole.default.file=/etc/webconsole/console/default.properties -Dwebconsole.config.file=/etc/webconsole/console/service.properties -Dcom.sun.web.console.startfile=/var/webconsole/tmp/console_start.tmp -Djava.awt.headless=true -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog org.apache.catalina.startup.Bootstrap start
root 3224 0.0 0.2 1864 1184 ? S 09:57:06 0:00 /usr/lib/cacao/lib/tools/launch -w /var/cacao/instances/default -L 16384 -A /usr/lib/cacao/lib/tools/proc_analysis -W /var/cacao/instances/default -T 300 -P /var/run/cacao/instances/default/run/hb.pipe -f -U root -G sys -- /usr/jdk/latest/bin/java -Xmx128M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8 -Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed -classpath /usr/share/lib/jdmk/jdmkrt.jar:/usr/share/lib/jdmk/jmxremote_optional.jar:/usr/lib/cacao/lib/cacao_cacao.jar:/usr/lib/cacao/lib/cacao_j5core.jar:/usr/lib/cacao/lib/bcprov-jdk14.jar -Djavax.management.builder.initial=com.sun.jdmk.JdmkMBeanServerBuilder -Dcacao.print.status=true -Dcacao.config.dir=/etc/cacao/instances/default -Dcacao.monitoring.mode=smf -Dcom.sun.cacao.ssl.keystore.password.file=/etc/cacao/instances/default/security/password com.sun.cacao.container.impl.ContainerPrivate
copying cacao files to /tmp/suc-cacao...
done.
Solaris 10 cacao instances:
STATE NSTATE STIME CTID FMRI
online - 9:57:07 88 svc:/application/management/common-agent-container-1:default
9:57:06 3224 launch
9:57:06 3225 java
Full list of cacao SMF service(s):
fmri svc:/application/management/common-agent-container-1:default
name Cacao, a common Java container for JDMK/JMX based management solution
enabled true (temporary)
state online
next_state none
state_time Thu Sep 22 09:57:07 2011
logfile /var/svc/log/application-management-common-agent-container-1:default.log
restarter svc:/system/svc/restarter:default
contract_id 88
dependency require_all/none svc:/system/filesystem/local (online)
dependency require_all/none svc:/network/initial (online)
dependency require_all/none svc:/milestone/multi-user (online)
Services in maintenance/disabled state:
svc:/system/pkgserv:default (Flush package command database to disk (see pkgadm(1m)).)
State: offline since Thu Sep 22 09:07:25 2011
Reason: Dependency file://localhost/usr/sadm/install/bin/pkgserv is absent.
See: http://sun.com/msg/SMF-8000-E2
Impact: This service is not running.
All ccr properties:
18:
cns.assetid:
cns.br.SunUCenabled:
true
cns.ccr.keyGenPath:
/usr/lib/cc-ccr/bin/ccrKeyGen
cns.clientid:
cns.httpproxy.auth:
cns.httpproxy.ipaddr:
cns.httpproxy.port:
cns.regtoken:
cns.security.password:
dAw5y36sZJoC+XZR504J4YfvVN8gcxGUYp1bCb8i7x21
cns.security.privatekey:
cns.security.publickey:
cns.swup.UMautolaunch:
false
cns.swup.autoAnalysis.enabled:
true
cns.swup.checkinInterval:
2
cns.swup.lastCheckin:
0
cns.swup.patchbaseline:
current
cns.swup.regRequired:
true
cns.transport.serverurl:
patchsvr not installed.
Entitlement:
smpatch settings:
patchpro.backout.directory     -     ""
patchpro.baseline.directory     -     /var/sadm/spool
patchpro.download.directory     -     /var/sadm/spool
patchpro.install.types          -     rebootafter:reconfigafter:standard
patchpro.patch.source          -     https://getupdates.oracle.com/
patchpro.patchset          -     current3
patchpro.proxy.host          -     ""
patchpro.proxy.passwd          ****     ****
patchpro.proxy.port          -     8080
patchpro.proxy.user          -     ""
debug smpatch analyze:
Effective proxy host : ""
Effective proxy port : "8080"
Effective proxy user : ""
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates.oracle.com
... ... Filename of URL is /xml/motd.xml
... ... File path portion of URL is /xml/motd.xml
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 18:00:00 CST 1969
... Caught IO Exception.
((HttpURLConnection)connection).getResponseCode() : 401
((HttpURLConnection)connection).getResponseMessage() : Authorization Required
Error: Unable to download document : "xml/motd.xml"
Cannot connect to retrieve motd.xml: Authorization Required
Effective proxy host : ""
Effective proxy port : "8080"
Effective proxy user : ""
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates.oracle.com
... ... Filename of URL is /detector/detectors.jar
... ... File path portion of URL is /detector/detectors.jar
Effective proxy host : ""
Effective proxy port : "8080"
Effective proxy user : ""
... Submitting download request against a GUUS server
... ... Hostname of URL is getupdates.oracle.com
... ... Filename of URL is /database/current3.zip
... ... File path portion of URL is /database/current3.zip
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 18:00:00 CST 1969
Defining request header : IF_MODIFIED_SINCE... valueWed Dec 31 18:00:00 CST 1969
... Caught IO Exception.
((HttpURLConnection)connection).getResponseCode() : 401
((HttpURLConnection)connection).getResponseMessage() : Authorization Required
... Caught IO Exception.
((HttpURLConnection)connection).getResponseCode() : 401
((HttpURLConnection)connection).getResponseMessage() : Authorization Required
Failure: Cannot connect to retrieve current3.zip: Authorization Required
ls /var/sadm/spool:
/var/sadm/spool:
total 2
drwxr-xr-x 5 root sys 512 Sep 22 10:00 cache
/var/sadm/spool/cache:
total 6
drwxr-xr-x 2 root root 512 Sep 22 10:00 Database
drwxr-xr-x 3 root sys 512 Sep 21 09:54 updatemanager
drwxr-xr-x 2 root root 512 Sep 22 10:00 xml
/var/sadm/spool/cache/Database:
total 0
/var/sadm/spool/cache/updatemanager:
total 2
drwxr-xr-x 2 root sys 512 Sep 21 09:54 analysis.results
/var/sadm/spool/cache/updatemanager/analysis.results:
total 0
/var/sadm/spool/cache/xml:
total 0
copying sconadm log files to /tmp/suc-sconadm...
done.
checking certificate...
Enter keystore password:
***************** WARNING WARNING WARNING *****************
* The integrity of the information stored in your keystore *
* has NOT been verified! In order to verify its integrity, *
* you must provide your keystore password. *
***************** WARNING WARNING WARNING *****************
Keystore type: jks
Keystore provider: SUN
Your keystore contains 11 entries
Alias name: smirootcacert
Creation date: Jun 18, 2002
Entry type: trustedCertEntry
Owner: CN=Sun Microsystems Inc Root CA, O=Sun Microsystems Inc, C=US
Issuer: CN=GTE CyberTrust Root, O=GTE Corporation, C=US
Serial number: 200014a
Valid from: Tue Nov 07 16:39:00 CST 2000 until: Thu Nov 07 17:59:00 CST 2002
Certificate fingerprints:
     MD5: D8:B6:68:D4:6B:04:B9:5A:EB:34:23:54:B8:F3:97:8C
     SHA1: BD:D9:0B:DA:AE:91:5F:33:C4:3D:10:E3:77:F0:45:09:4A:E8:A2:98
Alias name: updateserver.sun.com
Creation date: Apr 20, 2004
Entry type: trustedCertEntry
Owner: CN=updateserver.sun.com, OU=Solaris Patch Server, O="Sun Microsystems, Inc.", L=Santa Clara, ST=California, C=US
Issuer: CN=updateserver.sun.com, OU=Solaris Patch Server, O="Sun Microsystems, Inc.", L=Santa Clara, ST=California, C=US
Serial number: 4085ad7d
Valid from: Tue Apr 20 18:08:45 CDT 2004 until: Fri Apr 18 18:08:45 CDT 2014
Certificate fingerprints:
     MD5: C7:0D:9B:84:B2:E0:57:FA:F4:D1:0C:2E:F3:0E:68:DF
     SHA1: 48:B3:6B:35:AB:15:FE:BF:C5:B9:FF:39:F9:7E:FF:BB:C2:07:9B:7A
Alias name: gtecybertrustglobalca
Creation date: Feb 6, 2006
Entry type: trustedCertEntry
Owner: CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US
Issuer: CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US
Serial number: 1a5
Valid from: Wed Aug 12 19:29:00 CDT 1998 until: Mon Aug 13 18:59:00 CDT 2018
Certificate fingerprints:
     MD5: CA:3D:D3:68:F1:03:5C:D0:32:FA:B8:2B:59:E8:5A:DB
     SHA1: 97:81:79:50:D8:1C:96:70:CC:34:D8:09:CF:79:44:31:36:7E:F4:74
Alias name: verisignclass3g2ca
Creation date: Feb 6, 2006
Entry type: trustedCertEntry
Owner: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 3 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 3 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
Serial number: 7dd9fe07cfa81eb7107967fba78934c6
Valid from: Sun May 17 19:00:00 CDT 1998 until: Tue Aug 01 18:59:59 CDT 2028
Certificate fingerprints:
     MD5: A2:33:9B:4C:74:78:73:D4:6C:E7:C1:F3:8D:CB:5C:E9
     SHA1: 85:37:1C:A6:E5:50:14:3D:CE:28:03:47:1B:DE:3A:09:E8:F8:77:0F
Alias name: smicacert
Creation date: Jun 18, 2002
Entry type: trustedCertEntry
Owner: O=Sun Microsystems Inc, CN=Sun Microsystems Inc CA (Class B)
Issuer: CN=Sun Microsystems Inc Root CA, O=Sun Microsystems Inc, C=US
Serial number: 1000006
Valid from: Mon Nov 13 13:23:10 CST 2000 until: Fri Nov 13 13:23:10 CST 2009
Certificate fingerprints:
     MD5: B4:1F:E1:0D:80:7D:B1:AB:15:5C:78:CB:C8:8F:CE:37
     SHA1: 1E:38:11:02:F0:5D:A3:27:5C:F9:6E:B1:1F:C4:79:95:E9:6E:D6:DF
Alias name: patchsigning3
Creation date: Dec 9, 2008
Entry type: trustedCertEntry
Owner: CN=patchsign 20081125, OU=Class B, OU=Corporate Object Signing, O=Sun Microsystems Inc
Issuer: CN=Object Signing CA, OU=Class 2 OnSite Subscriber CA, OU=VeriSign Trust Network, O=Sun Microsystems Inc
Serial number: c6c945f7361c6aa3c520502b3db45a7
Valid from: Mon Nov 24 18:00:00 CST 2008 until: Fri Nov 25 17:59:59 CST 2011
Certificate fingerprints:
     MD5: 37:FD:5B:76:06:29:65:DB:47:D8:A5:AB:E7:D7:2C:08
     SHA1: 30:C7:C3:AF:85:00:8F:3B:41:DC:55:A3:99:53:E4:00:D8:97:D7:01
Alias name: patchsigning2
Creation date: Feb 8, 2006
Entry type: trustedCertEntry
Owner: CN=Patch (No version), OU=Class B, OU=Corporate Object Signing, O=Sun Microsystems Inc
Issuer: CN=Object Signing CA, OU=Class 2 OnSite Subscriber CA, OU=VeriSign Trust Network, O=Sun Microsystems Inc
Serial number: 3ed0ec9de0eed991b93f09d331d05e93
Valid from: Tue Jan 24 18:00:00 CST 2006 until: Sat Jan 24 17:59:59 CST 2009
Certificate fingerprints:
     MD5: 07:5C:E4:4F:4C:DC:4D:D5:D0:A8:A8:16:C8:DB:37:5F
     SHA1: A2:A8:17:32:2C:C4:7E:DE:8E:67:70:5E:08:2B:91:E9:8A:48:8C:05
Alias name: patchsigning
Creation date: Jun 18, 2002
Entry type: trustedCertEntry
Owner: CN=Enterprise Services Patch Management, O=Sun Microsystems Inc
Issuer: O=Sun Microsystems Inc, CN=Sun Microsystems Inc CA (Class B)
Serial number: 1400007b
Valid from: Mon Sep 24 15:38:53 CDT 2001 until: Sun Sep 24 15:38:53 CDT 2006
Certificate fingerprints:
     MD5: 6F:63:51:C4:3D:92:C5:B9:A7:90:2F:FB:C0:68:66:16
     SHA1: D0:8D:7B:2D:06:AF:1F:37:5C:0D:1B:A0:B3:CB:A0:2E:90:D6:45:0C
Alias name: smirootcacert2
Creation date: Oct 21, 2002
Entry type: trustedCertEntry
Owner: CN=Sun Microsystems Inc Root CA, O=Sun Microsystems Inc, C=US
Issuer: CN=GTE CyberTrust Root, O=GTE Corporation, C=US
Serial number: 40002ae
Valid from: Wed Oct 16 10:45:00 CDT 2002 until: Sat Oct 16 18:59:00 CDT 2004
Certificate fingerprints:
     MD5: 54:E3:D1:E4:79:B4:17:23:65:B4:F9:14:AD:C6:4A:FE
     SHA1: 90:F1:AB:87:AE:A0:4C:1F:AF:43:60:DE:5D:A8:0E:D8:CE:E7:06:AE
Alias name: getupdates.oracle.com
Creation date: Apr 25, 2011
Entry type: trustedCertEntry
Owner: CN=*.oracle.com, OU=Terms of use at www.verisign.com/rpa (c)10, OU=Global IT, O=Oracle Corporation, L=Redwood Shores, ST=California, C=US
Issuer: OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign, OU=VeriSign International Server CA - Class 3, OU="VeriSign, Inc.", O=VeriSign Trust Network
Serial number: 7854c9713b40a03d934e4b1b7f266170
Valid from: Mon Apr 12 19:00:00 CDT 2010 until: Thu May 05 18:59:59 CDT 2011
Certificate fingerprints:
     MD5: 03:CB:5F:B8:58:40:23:03:7E:89:A7:49:AF:06:7C:23
     SHA1: 63:95:E0:5C:87:42:8E:38:95:73:EE:03:1C:50:48:FE:43:8F:DC:8C
Alias name: oracle.com
Creation date: Apr 25, 2011
Entry type: trustedCertEntry
Owner: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Serial number: 641be820ce020813f32d4d2d95d67e67
Valid from: Sun Feb 07 18:00:00 CST 2010 until: Fri Feb 07 17:59:59 CST 2020
Certificate fingerprints:
     MD5: BA:B0:65:B4:3B:9C:E8:40:30:21:7D:C5:C6:CD:3F:EB
     SHA1: B1:8D:9D:19:56:69:BA:0F:78:29:51:75:66:C2:5F:42:2A:27:71:04
checking network settings...
141.146.44.51     updates.oraclegha.com getupdates.oracle.com updates.oracle.com
164.58.129.138     a248.e.akamai.net
164.58.129.143     a248.e.akamai.net
141.146.44.51     updates.oraclegha.com cns-services.oracle.com updates.oracle.com

Sampath,
You can use one of the following workarounds :
1. Install redhat-release package from AS
or
2. Edit /etc/redhat-release
change (for example):
Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
to:
Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
The next version of "up2date" will correctly handle "ES" or "WS" systems.
Regards,
Björn

Cacao service in maintenance after vda-config

Hello all,
I installed Sun VDI 3.1 on a x4150 Solaris 10 10/09 box, but when I run vda-config, choosing option 3: Single Sun VDI Host, I get this:
System Configuration
+ Restarting Common Agent Container service...
Error when trying to start SMF service: [svc:/application/management/common-agent-container-1:default].
Please check the SMF log file for more information: [var/svc/log/application-management-common-agent-container-1:default.log].
The configuration of Sun VDI 3.1 has completed.
This server is configured as a Single Sun VDI Host.
A log file is available at '/var/adm/log/vda-config.2010_01_18_07:38:26.log'.
bash-3.00$ svcs -l common-agent-container-1
fmri svc:/application/management/common-agent-container-1:default
name Cacao, a common Java container for JDMK/JMX based management solution
enabled true
state maintenance
next_state none
state_time Mon Jan 18 07:40:49 2010
logfile /var/svc/log/application-management-common-agent-container-1:default.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/system/filesystem/local (online)
dependency require_all/none svc:/network/initial (online)
dependency require_all/none svc:/milestone/multi-user (online)
In /var/svc/log/application-management-common-agent-container-1:default.log:
[ Jan 18 07:40:49 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Error: Fail to start cacao agent. default
[ Jan 18 07:40:49 Method "start" exited with status 1 ]
The cacao service runs just fine prior to vda-config.
How can I get this to work?
Thanks.

I figured out why cacao won't start after the config. vda-config does this:
cacaoadm set-param java-flags=-Xms4M -Xmx256M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8
This is what prevents cacao from starting again. But why? What should it be? Any ideas?
Thanks.

Cacaoadm start fail ( Can't load library)

Hi,
Do you have any idea regarding following error while starting cacao:
root #
root # cacaoadm start
Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /var/run/.patchSafeMode/root/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
at java.lang.Runtime.load0(Runtime.java:769)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
root #
root#
root#
root@#
root@#
root@# cacaoadm -V
2.1.1
root@#
root@ #
root@# uname -a
SunOS cluster2 5.10 Generic_138888-01 sun4v sparc SUNW,SPARC-Enterprise-T5220
root@#
root@#
root@ #
root@ #
root@ # svcs -l svc:/application/management/common-agent-container-2:default
fmri svc:/application/management/common-agent-container-2:default
name Cacao, a common Java container for JDMK/JMX based management solution
enabled true
state maintenance
next_state none
state_time Mon Feb 09 19:34:07 2009
logfile /var/svc/log/application-management-common-agent-container-2:default.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/system/filesystem/local (online)
dependency require_all/none svc:/network/initial (online)
dependency require_all/none svc:/milestone/multi-user (online)
root@#
root@ # tail -30 /var/svc/log/application-management-common-agent-container-2:default.log
[ Feb 9 19:33:50 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /var/run/.patchSafeMode/root/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
at java.lang.Runtime.load0(Runtime.java:769)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
Error: Fail to start cacao agent. default
[ Feb 9 19:33:56 Method "start" exited with status 1 ]
[ Feb 9 19:33:56 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /var/run/.patchSafeMode/root/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
at java.lang.Runtime.load0(Runtime.java:769)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
Error: Fail to start cacao agent. default
[ Feb 9 19:34:02 Method "start" exited with status 1 ]
[ Feb 9 19:34:02 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /var/run/.patchSafeMode/root/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
at java.lang.Runtime.load0(Runtime.java:769)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
Error: Fail to start cacao agent. default
[ Feb 9 19:34:07 Method "start" exited with status 1 ]
root@ #
I will be great if you guys can give me some tips about this.
Thanks.

Hi Tim,
I havw change it to the same with no luck still not able to start cacaoadm?? smcwebserver version 3.0.2 and cacaoadm -V 2.2.0.1? any more suggestion? error i'm getting is
Error: Fail to start cacao agent. default
[ May 13 17:43:16 Method "start" exited with status 1 ]
[ May 13 17:44:34 Leaving maintenance because clear requested. ]
[ May 13 17:44:34 Enabled. ]
[ May 13 17:44:34 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Error: Fail to start cacao agent. default
[ May 13 17:44:36 Method "start" exited with status 1 ]

Cacao love *sigh*

Trying to register a new machine (with sconadm), it just sits there..
# svcs -xv
svc:/application/management/common-agent-container-1:default (Cacao, a common Java container for JDMK/JMX based management solution)
State: maintenance since Wed Aug 06 09:41:26 2008
Reason: Start method failed repeatedly, last exited with status 1.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M cacaoadm
See: man -M /usr/share/man -s 5 cacao
See: /var/svc/log/application-management-common-agent-container-1:default.log
Impact: This service is not running.
# cacaoadm start
Exception in thread "main" java.lang.UnsatisfiedLinkError: Expecting an absolute path of the library: #CACAO_RT_INSTALL_BASEDIR#/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.Runtime.load0(Runtime.java:766)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
# cat /etc/release
Solaris 10 5/08 s10s_u5wos_10 SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008
# uname -a
SunOS xxxxxx 5.10 Generic_137111-04 sun4v sparc SUNW,SPARC-Enterprise-T5220
Any ideas?

# cat /var/svc/log/application-management-common-agent-container-1\:default.log
[ Aug 6 09:41:20 Executing start method ("/usr/lib/cacao/lib/tools/scripts/cacao_smf start default") ]
Exception in thread "main" java.lang.UnsatisfiedLinkError: Expecting an absolute path of the library: #CACAO_RT_INSTALL_BASEDIR#
/usr/lib/cacao/lib/libcacao_cacao.so
at java.lang.Runtime.load0(Runtime.java:766)
at java.lang.Runtime.load(Runtime.java:757)
at com.sun.cacao.container.impl.ContainerPrivate.internalStart(ContainerPrivate.java:511)
at com.sun.cacao.container.impl.ContainerPrivate.start(ContainerPrivate.java:451)
at com.sun.cacao.container.impl.ContainerPrivate.main(ContainerPrivate.java:766)
Error: Fail to start cacao agent. default
[ Aug 6 09:41:26 Method "start" exited with status 1 ]
# pkgchk SUNWcacaort SUNWcacaowsvr SUNWcacaocrews SUNWcacaodtrace SUNWcacaome
WARNING: no pathnames were associated with <SUNWcacaowsvr>
WARNING: no pathnames were associated with <SUNWcacaocrews>
WARNING: no pathnames were associated with <SUNWcacaome>
# ldd /usr/lib/cacao/lib/libcacao_cacao.so
libsecdb.so.1 => /lib/libsecdb.so.1
libpam.so.1 => /lib/libpam.so.1
libdl.so.1 => /lib/libdl.so.1
libc.so.1 => /lib/libc.so.1
libnsl.so.1 => /lib/libnsl.so.1
libcmd.so.1 => /lib/libcmd.so.1
libmp.so.2 => /lib/libmp.so.2
libmd.so.1 => /lib/libmd.so.1
libscf.so.1 => /lib/libscf.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
libm.so.2 => /lib/libm.so.2
/platform/SUNW,SPARC-Enterprise-T5220/lib/libc_psr.so.1
/platform/SUNW,SPARC-Enterprise-T5220/lib/libmd_psr.so.1
# showrev -p | egrep '127141-07|123893-04'
Patch: 123893-04 Obsoletes: 124463-02 Requires: Incompatibles: Packages: SUNWcacaort

Anyone familiar w. SNMP, JMX, JDMK or Solstice

I am interested in reporting the number of java "objects" that are sent over a network.
Ideally, I would see reports in the Sun MC, Management Console.
Can anyone provide any clues as to whether this is possible using SNMP, JMX, JDMK, Solstice, or something else.
I am not interested in a proxy service. I do not want to intrude on the network.

Are you asking about the way to report or query the information such that can implement the monitor and communicate to SMC?
Or, are you wondering if the JVM (?) tracks that information in a way that is accessible by any or all of the thos protocols? If so, the answer is no.

JMX version compatibility

Can code written with JMX API in JDK5 running on JRE1.4 environment? Of course, I assume our written code JMX do not have some JDK 5 specific features, e.g. generics .
How about the same query for JMX API in JDK6?

Andy,
The JMX API in JDK 5 is identical to the API defined by JSRs 3 and 160, the JMX API and JMX Remote API respectively. You can download implementations of those JSRs from <http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/download.jsp>. You can connect to your JMX instrumentation using the JConsole from JDK 5 or JDK 6. The only things that are not available are (1) the ability to start a connector automatically using system properties like -Dcom.sun.management.jmxremote, and (2) the "platform MBeans" defined in java.lang.management that show things like memory and thread statistics.
The JMX API in JDK 6 is backward compatible. If you avoid any classes or methods that are marked "Since 1.6" in the Javadoc specification, then your JDK 6 code should also work on JDK 5 and 1.4.
Regards,
�amonn McManus -- JMX Spec Lead -- http://weblogs.java.net/blog/emcmanus

Possible to connect between JMX 1.0 and JMX 1.2

Hi,
We have a module that needs to send notifications. This java module is running in a J2EE Weblogic 8.1 webapp server. Weblogic support JMX 1.0.
Outside the J2EE server in another JVM we have the JMXAgent and the MBeans running as a regular server ( in J2SE). This server uses JMX 1.2 with the remote API ( not in JMX 1.0).
Both use the jdk1.4.x version of java.
The problem we have is to send the notification ( from weblogic) to the MBean since they support different JMX versions.
Any hints?
cheers,
//mike

Hi,
You will need to use a proprietary connector to exchange notifications between a JMX 1.0 application and a JMX 1.2 application, because JMX Remote API connector servers will
not work on top of JMX 1.0.
If weblogic 8 implements such a proprietary connector, you might be able to use its server part in your weblogic application, and its client part from within a client JVM that contains JMX 1.2.
http://e-docs.bea.com/wls/docs81/index.html
You might also try to use other proprietary connectors, such as those offered by the
Java DMK - for instance you could start a Java DMK 4.2 connector server (JDMK 4.2 is
based on JMX 1.0) in your weblogic application, and uses Java DMK 5.1/OpenDMK
in your JMX 1.2 client (Java DMK 4.2 and Java DMK 5.1/OpenDMK are inter-operable).
http://java.sun.com/products/jdmk/release.html#42
http://java.sun.com/products/jdmk
https://opendmk.dev.java.net/
Hope this helps,
-- daniel
http://blogs.sun.com/jmxetc

ColdFusion compatibility with Sun Java System Application Server

Background: A vendor that is doing a project for our
department told us that ColdFusion MX 6.1 is not compatible with
Sun Java System Application Server Enterprise Edition 8.1 and
beyond. Since we are migrating our server environment to this
release of Sun Java System Application Server Enterprise Edition,
we face a difficult situation in that our ColdFusion applications
will no longer run. Thus, we would like Adobe to answer a couple
questions which will help us determine what course of action we
ought to take.
Q: Will applications we developed using ColdFusion MX 6.1 run
on Sun Java System Application Server Enterprise Edition 8.1? Below
is a detailed description of the Sun Java System Application Server
Enterprise Edition we intend to migrate to.
Q: Is Adobe aware of any compatibility issues with this
configuration?
Q: What is Adobe's support commitment regarding future
releases of ColdFusion MX and Sun Java System Application Server
Enterprise Edition? Does Adobe intend to continue support this
environment?
Configuration: Sun Java System Application Server Enterprise
Edition 8.1_02 (build b24-p11)
Below is the specification levels for the 8.1 server
(J2EE1.4), note it can use J2SE 1.4.2_06 or 5.0 as the JAVA
runtime.
J2EE 1.4 compatible
Components: J2SE 1.4.2_06 or J2SE 5.0
Application and Application Client
Enterprise JavaBeans (EJB) 2.1
Java Servlet 2.4
JavaServer Pages(JSP) 2.0
J2EE Connector Architecture 1.5
JMX 1.2
JMS 1.1
Java Naming and Directory Interface (JNDI) 1.2
and Java Transaction API (JTA) 1.0
Web Services:Java Web Services Developer Pack 1.5
Java APIs for XML Registries (JAXR) 1.0
Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.1
SOAP With Attachments API for Java (SAAJ) 1.2
WS-I Basic Profile 1.0
Other:J2EE Deployment 1.1
J2EE Management 1.0
Java API for XML Processing (JAXP) 1.2
JavaMail 1.3
Java Authentication and Authorization Service (JAAS) 1.0
Java Authorization Contract for Containers (JACC) 1.0

First of all, is there a reason why you are using jRockit?
Since the issue appeared after upgrading the windows, the issue would potentially be in the interaction between JVM and OS.
Also, there were some issues related to memory leak that were fixed in AS 8.2.
May be you should try with a Sun JVM and AS 8.2.

(?) Java Management Extensions(JMX) Change

program works with previous versions of java,
with the java update 13, what could possibly be the compatibility issues that
i could look into and consider?
does JMX always works internally with any java application?
confused.
thanks
Edited by: twinks on Oct 7, 2009 6:23 AM

hi thanks for the reply.
im not really sure if the program uses jmx application.
i could not find the
javax.management in the imports of the sourcefiles though.
so i was wondering if jmx works internally in java or that one has yet to implement it and use the interfaces?
because if yes, then i think i dont have a compatibility problem with
6u13, but if it does, i dont know what aspects or what part of the application should i look into for possible compatibility issues.
:(

SNMP-to-JMX bridge

Does anyone know if there is a free SNMP-to-JMX bridge which makes it easy for tools like http://cacti.net/ to poll statistics about particular MBeans which expose int/long-type attributes.
I know JBoss offers such a solution but I would like to use something that doesn't require an application server.
Thanks.

Hi,
I don't have a ready-to-use solution to offer, but you could have a look at
the JMX-MBEAN-SERVER-MIB (examples/Snmp/MBeanVirtualTable) that comes
with the Java DMK.
http://java.sun.com/products/jdmk/index.jsp
The evaluation of the Java DMK is free and you could experiment with that table.
As far as I remember the example MIB only exposes MBean attributes as Strings
(using toString()), but if you have a little knowledge of JMX, SNMP & SMIv2 you should
be able to extend the MIB in order to handle ints as ints and longs as longs.
You could also write your own MIB dedicated to your own MBeans, like we did for
the JVM-MANAGEMENT-MIB which exposes the Monitoring & Management of the JVM
through SNMP. This would however require more coding & more SNMP expertise.
If you're interested in learning more about JMX, SNMP, and the JVM-MANAGEMENT-MIB,
I have written a series of articles on that subject - a good starting point is here:
http://blogs.sun.com/jmxetc/entry/simple_is_not_easy
Hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/jmxetc
Message was edited by:
dfuchs

Wierd problems of JDMK in Weblogic8.1

Hi, all,
I use JDMK5.1 to connect two Applications with JMX RmiConnector. The Applications run in WebLogic8.1.4. App1 is a normal application monitored by App2. App1 creates RMIConnectorServer and App2 creates RMIConnectorClient, an HtmlAdaptor listening 8082 is also created in App1. App2 manages App1 by monitoring and controlling the mbeans of App1.
I got two weird problems making me crazy:
1. App2 can get the MBean's property of App1, but if the property is primitive type (such as long, int or boolean) and the MBean is not a StandardMBean, the property is null in App2, and "UNAVAILABLE: javax.management.MBeanException wraps [java.lang.ClassNotFoundException: long]" is shown in the html page of HttpAdaptor.
2. App2 can get some mbeans but not all mbeans. App2 can get objectname of all mbeans, but with some mbeans, App2 get the MBeanInfo will encounter the exception below:
java.lang.NullPointerException
     at javax.management.MBeanFeatureInfo.readObject(MBeanFeatureInfo.java:80)
     at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1603)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1271)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
     at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:297)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:146)
     at com.sun.jdmk.comm.RmiConnectorServerObjectImplV2_Stub.getMBeanInfo(Unknown Source)
     at com.sun.jdmk.comm.comm.RmiConnectorClient.getMBeanInfo(Unknown Source)
All the problems above never happen in WebSphere5.1.
Any help will be high appreciated!

Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!
Try a Coke-a-Cola ther good!

JMX vs Reflexion

Hello,
I am trying to establish a comparison of Java Management Extensions and Java Reflexion. What does JMX brings that "standard" reflexion cannot do? What is the difference between those two APIs and what would be a practical use case for them?
Thanks in advance,
Balteo.

Well, firstly by defining an MBean you are restricting what classes and methods can be accessed - using reflection you could access any class and any method.
Secondly, you register in a central repository all your managed objects, so you don't have to keep track of all your objects yourself. This repository has namespaces so you can organise your objects.
Thirdly, JMX allows notification of events, rather than having to write your own custome event handling/routing etc.
Fourthly, JMX provides gauges, so that user defined limits can be put onto objects, and special events triggered when these limits are breached.
Using products such as Suns JDMK you can transparently remotely manage things, without having to write all that custom code yourself.
There may be more that I haven't thought of.
Don't really know of all of the uses of reflection, but JMX is very good for managing objects and managing and monitoring your system. If you look at JBoss they have a JMX micro kernal which loads all of the other parts of the app server, making it extremely flexible and easy to manage.

How to use JMX

Hi, all,
I am newbie in JMX. I want to know what software,such as API and so on, i must need to use JMX .and I want some tutorials of JMX.
thanks.
Kaven

Check out the JMX listserv archives at
http://archives.java.sun.com
and look for JMX-FORUM.
Theres information in there, and coincidentally over that last two days people have been asking the exact same question - look for the replies to topic "help ... get me started" - lots of links there.
There is also the sun JMX home page.
There are a few commercial implementations of JMX and at least 2 open source ones - search the JMX-FORUM for "open" if you're interested in that. Plus Sun supplies a reference implementation ( although I haven't used that.)
Personally I use JDMK, Sun's implementation, and I've found it meets my needs ( but then I'm not paying for the licence, my company is.) and it is available as an evaluation copy before you buy. It comes with tutorials, but I wouldn't be surprised if the others do as well.
Try and search the sun site and google for JMX, there'll be stuff there.
Finally, go to Amazon.com and look for "java and jmx" - there is at least one book out there.

Jmx-1_2_1-ri.zip & maven

I downloaded jmx-1_2_1-ri.zip and ran this command:
mvn install:install-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=./jmx-1_2_1-ri.zip
so it is now in my local maven repo (C:\Documents and Settings\<user>\.m2\repository
(before you point me to the error messsages in maven that show me where to go to download jars, please note that I have already gone to the URL and there is nothing to download except documentation (pdf files). You can go to the URL's and see there is no reference implementation, just docs.
It would be great if Sun ran their own maven repo where we could get jars (and actually kept it up to date).
URL's (nothing here except docs - no jars no ri
http://java.sun.com/products/JavaManagement/download.html
http://java.sun.com/products/jms/docs.html
(there is an ri here and I downloaded it and it is in my rep (see below) but I still get maven compile errors)
Details when I do:
$mvn install
I get
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
1) javax.jms:jms:jar:1.1
Try downloading the file manually from:
http://java.sun.com/products/jms/docs.html
Then, install it using the command:
mvn install:install-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=url -DrepositoryId=[id]
Path to dependency:
1) shift:sample:jar:1.0-SNAPSHOT
2) log4j:log4j:jar:1.2.15
3) javax.jms:jms:jar:1.1
2) com.sun.jdmk:jmxtools:jar:1.2.1
Try downloading the file manually from:
http://java.sun.com/products/JavaManagement/download.html
Then, install it using the command:
mvn install:install-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) shift:sample:jar:1.0-SNAPSHOT
2) com.sun.jdmk:jmxtools:jar:1.2.1
3) javax.management:jmxri:jar:1.2.1
Try downloading the file manually from:
http://java.sun.com/products/JavaManagement/download.html
Then, install it using the command:
mvn install:install-file -DgroupId=javax.management -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=javax.management -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) shift:sample:jar:1.0-SNAPSHOT
2) javax.management:jmxri:jar:1.2.1
3 required artifacts are missing.
for artifact:
shift:sample:jar:1.0-SNAPSHOT
from the specified remote repositories:
maven2-repository.dev.java.net (http://download.java.net/maven/2/),
central (http://repo1.maven.org/maven2)
-- this is what is in my maven repo
$ ls -alR jmx
jmx:
total 0
drwx------+ 3 roger None 0 Feb 20 01:20 .
drwx------+ 4 roger None 0 Feb 20 01:20 ..
drwx------+ 3 roger None 0 Feb 28 22:25 jmxri
jmx/jmxri:
total 1
drwx------+ 3 roger None 0 Feb 28 22:25 .
drwx------+ 3 roger None 0 Feb 20 01:20 ..
drwx------+ 2 roger None 0 Feb 28 22:25 1.2.1
-rwx------+ 1 roger None 292 Feb 28 22:25 maven-metadata-local.xml
jmx/jmxri/1.2.1:
total 18
drwx------+ 2 roger None 0 Feb 28 22:25 .
drwx------+ 3 roger None 0 Feb 28 22:25 ..
-rwx------+ 1 roger None 13236 Feb 28 22:25 jmxri-1.2.1.jar
-rwx------+ 1 roger None 155 Feb 20 01:20 jmxri-1.2.1.pom
-rwx------+ 1 roger None 40 Feb 20 01:20 jmxri-1.2.1.pom.sha1

I am very puzzled at what you write. If I go to http://java.sun.com/products/JavaManagement/download.html I see a section titled SPECIFICATIONS and a later section titled BINARY DOWNLOAD. In this second section I can download the implementations of the JMX and JMX Remote APIs.
What you write might be true of the JMS API, but the JMS and JMX APIs are completely unrelated (despite their similar names).
Éamonn McManus -- JMX Spec Lead -- http://weblogs.java.net/blog/emcmanus

JDMK + JMX 1.0 compatability

Similar Messages

Maybe you are looking for