Kbase P112504: Installation of Fathom Management breaks the functionality of OpenEdge Web Services
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/10/2010 |
|
Status: Verified
SYMPTOM(s):
Installation of Fathom Management breaks the functionality of OpenEdge Web Services
Unable to deploy new Web Service after enabling Fathom Management remote monitoring
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.IncompatibleClassChangeError
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:349)
Unable to update Web Service after installation of Fathom remote monitoring
Unable to query Web Service Adapter instance after installation of Fathom remote monitoring
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.NoClassDefFoundError: org/apache/soap/util/xml/XMLJavaMappingRegistry
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:349)
FACT(s) (Environment):
Windows
OpenEdge 10.0B
Fathom Management 3.0A
CAUSE:
Bug# OE00123584
CAUSE:
Bug# OE00123918
FIX:
Upgrade to 10.1A or later.
Workaround:
After Fathom Management has been installed and enabled:
Copy the classpath content of the [PluginPolicy.WSA] section in the %DLC%\properties\AdminServerPlugins.properties file and prepend it to the classpath of the [PluginPolicy.Progress.AdminServer] section.
If you start the AdminServer from the Windows services, then you would have to add -DSONICMQ_XBOOTPATH="-Xbootclasspath/p:." to the Chimera string in the registry. The exact location is: [HKLM]\SOFTWARE\PSC\AdminService\10.0B\StartupCmd. For example:
"c:\Progress\oe100b\bin\jvmstart" -a "c:\Progress\oe100b\properties\AdminServerPlugins.properties"::PluginPolicy.Progress.AdminServer -o eventmgr -w @{WorkPath} @{JAVA\JREHOME}\bin\java -DInstall.Dir=@{Startup\DLC} -DWork.Dir=@{WorkPath} -DSONICMQ_XBOOTPATH="-Xbootclasspath/p:." -Dadmsrv.jvm=@{JAVA\JREHOME}\bin\java -Djvmstart.debug=0 com.progress.chimera.adminserver.AdminServerType -start -service
If you are using the proadsv.bat script, then you need to include the -DSONICMQ_XBOOTPATH="-Xbootclasspath/p:." parameter, for example:
"%JVMSTRT%" -o stderr -s -m silent -a "%ADMSRVRPROP%"::%ADMSRVRGRP% "%JVM%" -Dadmsrv.jvm="%JVM%" -DInstall.Dir="%DLC%" -DWork.Dir="%WRK%" -DSONICMQ_XBOOTPATH="-Xbootclasspath/p:." -Djvmstart.debug=0 %ADMSRVRCLASS% %PARMS%