lifecycle page not show
When I use RAM admin to view the life cycle tab, it always report java applet error, but I have already accept to load Applet. I changed 5 machines, but got the same error like this:
java.lang.ClassFormatError: Incompatible magic value 1008813135 in class file com/ibm/ram/applet/lifecycle/LifecycleApplet
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Errorjava.lang.ClassFormatError: Incompatible magic value 1008813135 in class file com/ibm/ram/applet/lifecycle/LifecycleApplet
java.lang.ClassFormatError: Incompatible magic value 1008813135 in class file com/ibm/ram/applet/lifecycle/LifecycleApplet
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Errorjava.lang.ClassFormatError: Incompatible magic value 1008813135 in class file com/ibm/ram/applet/lifecycle/LifecycleApplet
11 answers
Hi,
Your browser's applet cache has probably been corrupted.
Try:
Its the Java cache, so the solution go to Java Control Panel, "General"
tab, and under "Temporary Internet Files" click "Settings", then click
"Delete Files". Try using the applet again.
--
Rich Kulp
Rational Asset Manager developer
Your browser's applet cache has probably been corrupted.
Try:
Its the Java cache, so the solution go to Java Control Panel, "General"
tab, and under "Temporary Internet Files" click "Settings", then click
"Delete Files". Try using the applet again.
--
Rich Kulp
Rational Asset Manager developer
Rich,
I tried in my machine, but it still not work after delete temporary files under
C:\Documents and Settings\Administrator\Application Data\IBM\Java\Deployment\cache
I tried in my machine, but it still not work after delete temporary files under
C:\Documents and Settings\Administrator\Application Data\IBM\Java\Deployment\cache
Hi,
Your browser's applet cache has probably been corrupted.
Try:
Its the Java cache, so the solution go to Java Control Panel, "General"
tab, and under "Temporary Internet Files" click "Settings", then click
"Delete Files". Try using the applet again.
--
Rich Kulp
Rational Asset Manager developer
Hi,
Actually this link is even more interesting:
http://forums.sun.com/thread.jspa?threadID=640927
It could be you are getting a bad link. When you access a link on the
web side of RAM (instead of the web services) a 404 IS NOT SENT. Instead
a standard html error page is being created. This would then produce the
shown error.
Try doing this:
using your base ram link (such as "http://my.host.com/ram/") go to this
link in RAM: "applets/lifecycle.jar" (like
"http://my.host.com/ram/applets/lifecycle.jar") and see what you get. Do
you get a jar or a page not found.
One other thing, is your context path (e.g. "/ram/") more than one path
(e.g. "/something/ram/")? You didn't say what version of RAM you have.
We currently have problems with this kind of path in 7202 and below.
There is a 7202 testfix 7 that handles some of these. I don't know if
this is one of them.
--
Rich Kulp
Rational Asset Manager developer
Actually this link is even more interesting:
http://forums.sun.com/thread.jspa?threadID=640927
It could be you are getting a bad link. When you access a link on the
web side of RAM (instead of the web services) a 404 IS NOT SENT. Instead
a standard html error page is being created. This would then produce the
shown error.
Try doing this:
using your base ram link (such as "http://my.host.com/ram/") go to this
link in RAM: "applets/lifecycle.jar" (like
"http://my.host.com/ram/applets/lifecycle.jar") and see what you get. Do
you get a jar or a page not found.
One other thing, is your context path (e.g. "/ram/") more than one path
(e.g. "/something/ram/")? You didn't say what version of RAM you have.
We currently have problems with this kind of path in 7202 and below.
There is a 7202 testfix 7 that handles some of these. I don't know if
this is one of them.
--
Rich Kulp
Rational Asset Manager developer
Hi, Rich,
I tried the link as you mean "http://my.host.com/ram/applets/lifecycle.jar", and it will ask me to download this jar file. Our RAM is using the 7202 with the test fix 6 , our URL has some fixed context path between "http://my.host.com/" with "ram", do you think we should download the text fix 7? Thanks.
I tried the link as you mean "http://my.host.com/ram/applets/lifecycle.jar", and it will ask me to download this jar file. Our RAM is using the 7202 with the test fix 6 , our URL has some fixed context path between "http://my.host.com/" with "ram", do you think we should download the text fix 7? Thanks.
Hi,
Actually this link is even more interesting:
http://forums.sun.com/thread.jspa?threadID=640927
It could be you are getting a bad link. When you access a link on the
web side of RAM (instead of the web services) a 404 IS NOT SENT. Instead
a standard html error page is being created. This would then produce the
shown error.
Try doing this:
using your base ram link (such as "http://my.host.com/ram/") go to this
link in RAM: "applets/lifecycle.jar" (like
"http://my.host.com/ram/applets/lifecycle.jar") and see what you get. Do
you get a jar or a page not found.
One other thing, is your context path (e.g. "/ram/") more than one path
(e.g. "/something/ram/")? You didn't say what version of RAM you have.
We currently have problems with this kind of path in 7202 and below.
There is a 7202 testfix 7 that handles some of these. I don't know if
this is one of them.
--
Rich Kulp
Rational Asset Manager developer
Rich,
our path like this:
https://yourhost.com/cc/enterprise/ram/
Is the test fix 7 include any change? Thanks.
our path like this:
https://yourhost.com/cc/enterprise/ram/
Is the test fix 7 include any change? Thanks.
Hi,
I'm not quite sure what you were saying.
Testfix 7 will fix this:
http://yourhost.com/somethingElseBesidesJustRam/ram/...
If you path is just:
http://yourhost.com/ram/...
then test fix 7 will not help.
--
Rich Kulp
Rational Asset Manager developer
On 11/15/2010 2:53 AM, pantian wrote:
Like I said, testfix 7 will handle some problems like what you just
showed. It may completely fix your problem. I hope it does. Having a
multi-path context root is new to RAM. Nobody had done that until a
month ago. So we fixed the problems in testfix 7 that the customer had
in that particular case.
--
Rich Kulp
Rational Asset Manager developer
Rich,
our path like this:
https://yourhost.com/cc/enterprise/ram/
Like I said, testfix 7 will handle some problems like what you just
showed. It may completely fix your problem. I hope it does. Having a
multi-path context root is new to RAM. Nobody had done that until a
month ago. So we fixed the problems in testfix 7 that the customer had
in that particular case.
--
Rich Kulp
Rational Asset Manager developer
page 1of 1 pagesof 2 pages