You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/06/27 07:59:29 UTC

[jira] Created: (HADOOP-325) ClassNotFoundException under jvm 1.6

ClassNotFoundException under jvm 1.6
------------------------------------

         Key: HADOOP-325
         URL: http://issues.apache.org/jira/browse/HADOOP-325
     Project: Hadoop
        Type: Bug

  Components: ipc  
    Versions: 0.3.2    
    Reporter: Owen O'Malley
 Assigned to: Owen O'Malley 
     Fix For: 0.4.0


We have been having problems with classes that are returned by RPC methods not being loaded/initialized correctly. The work around has been to put in the servers, code of the form:

static { new FooBar(); }  // to resolve the ClassNotFoundException for class FooBar.

When I tried running under java 1.6, that stopped working because one of the classes had to be instantiated from a package that didn't have visibility to create an instance. So I tracked the problem down to how the classes were being loaded via reflection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (HADOOP-325) ClassNotFoundException under jvm 1.6

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-325?page=all ]

Owen O'Malley updated HADOOP-325:
---------------------------------

    Attachment: class-load-init.patch

This patch uses the required classloader, but makes sure the class is initialized.

I found and removed the object creation blocks from the 4 servers, but if there are others hiding somewhere, please let me know.

> ClassNotFoundException under jvm 1.6
> ------------------------------------
>
>          Key: HADOOP-325
>          URL: http://issues.apache.org/jira/browse/HADOOP-325
>      Project: Hadoop
>         Type: Bug

>   Components: ipc
>     Versions: 0.3.2
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.4.0
>  Attachments: class-load-init.patch
>
> We have been having problems with classes that are returned by RPC methods not being loaded/initialized correctly. The work around has been to put in the servers, code of the form:
> static { new FooBar(); }  // to resolve the ClassNotFoundException for class FooBar.
> When I tried running under java 1.6, that stopped working because one of the classes had to be instantiated from a package that didn't have visibility to create an instance. So I tracked the problem down to how the classes were being loaded via reflection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Resolved: (HADOOP-325) ClassNotFoundException under jvm 1.6

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-325?page=all ]
     
Doug Cutting resolved HADOOP-325:
---------------------------------

    Resolution: Fixed

I just committed this.  Thanks, Owen!

> ClassNotFoundException under jvm 1.6
> ------------------------------------
>
>          Key: HADOOP-325
>          URL: http://issues.apache.org/jira/browse/HADOOP-325
>      Project: Hadoop
>         Type: Bug

>   Components: ipc
>     Versions: 0.3.2
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.4.0
>  Attachments: class-load-init.patch
>
> We have been having problems with classes that are returned by RPC methods not being loaded/initialized correctly. The work around has been to put in the servers, code of the form:
> static { new FooBar(); }  // to resolve the ClassNotFoundException for class FooBar.
> When I tried running under java 1.6, that stopped working because one of the classes had to be instantiated from a package that didn't have visibility to create an instance. So I tracked the problem down to how the classes were being loaded via reflection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira