Issue Details (XML | Word | Printable)

Key: GLASSFISH-15427
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: naman_mehta
Reporter: varunrupela
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

[STRESS] ClassFormatError observed from the logging module on a RichAccess run with JRockit

Created: 04/Jan/11 02:51 AM   Updated: 10/Jan/11 05:41 PM   Resolved: 10/Jan/11 05:41 PM
Component/s: logging
Affects Version/s: 3.1_b35
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File server.log (922 kB) 04/Jan/11 02:51 AM - varunrupela

Issue Links:
Dependency
 

Tags:
Participants: naman_mehta, Nazrul and varunrupela


 Description  « Hide

Please see parent issue http://java.net/jira/browse/GLASSFISH-15425 for details of the scenario.

The following message has been observed in the instance logs during the run:
*********
[#|2011-01-02T20:33:36.584+0530|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=22;_ThreadName=Thread-3;|Exception in thread "RMI TCP Connection(idle)" |#]

[#|2011-01-02T20:33:36.585+0530|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=22;_ThreadName=Thread-3;|java.lang.ClassFormatError: sun/reflect/GeneratedSerializationConstructorAccessor9016 : illegal JVM_CONSTANT_Methodref name: <init>
at sun.misc.Unsafe.defineClass(Native Method)
at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45)
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
at sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95)
at sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313)
at java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327)
at java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:413)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:409)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:409)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:409)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:409)
at java.io.ObjectStreamClass.lookup0(ObjectStreamClass.java:310)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1114)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:403)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

#]

Attached one of ther server logs that shows this issue.



varunrupela added a comment - 05/Jan/11 04:24 AM

We have started a re-run of this scenario with the latest build to collect more information on issue http://java.net/jira/browse/GLASSFISH-15426. Will also check if this issue still exists.


Nazrul added a comment - 10/Jan/11 05:41 PM

Not enough information available.