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 "Hairong Kuang (JIRA)" <ji...@apache.org> on 2006/05/13 02:58:10 UTC
[jira] Created: (HADOOP-217) IllegalAcessException when creating a
Block object via WritableFactories
IllegalAcessException when creating a Block object via WritableFactories
------------------------------------------------------------------------
Key: HADOOP-217
URL: http://issues.apache.org/jira/browse/HADOOP-217
Project: Hadoop
Type: Bug
Components: dfs
Versions: 0.3
Reporter: Hairong Kuang
Assigned to: Hairong Kuang
Fix For: 0.3
Attachments: access.patch
When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
at java.lang.Class.newInstance0(Class.java:344)
at java.lang.Class.newInstance(Class.java:303)
at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
... 5 more
--
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-217) IllegalAcessException when creating a
Block object via WritableFactories
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=all ]
Hairong Kuang updated HADOOP-217:
---------------------------------
Attachment: access.patch
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.3
> Attachments: access.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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-217) IllegalAcessException when creating a
Block object via WritableFactories
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=all ]
Doug Cutting resolved HADOOP-217:
---------------------------------
Fix Version: 0.3
(was: 0.4)
Resolution: Fixed
I just committed this. Thanks!
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.3
> Attachments: access.patch, block.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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] Commented: (HADOOP-217) IllegalAcessException when creating
a Block object via WritableFactories
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=comments#action_12413905 ]
Doug Cutting commented on HADOOP-217:
-------------------------------------
I think this has been fixed, no?
The problem is that, when we modified Hadoop to use a classloader the writable factory stuff partially broke. In particular, one can now obtain a reference to a Class instance when the static initializers of that class have not yet been run. In particular, the RPC code calls something like 'WritableFactories.newInstance(ClassLoader.findClass("foo.bar.Baz")), and foo.bar.Baz's static initializer, which registers the writable factory, has not yet run, and the call to newInstance fails as above. The work-around we've been using thus far is to, in the RPC client code, add a 'static { new Baz(); }' to force the static initializers of Baz to run. Long-term we should find a better solution.
We'd like to be able to pass objects in RPCs that are not public classes. This means that the RPC code needs to be able to construct an instance. The WritableFactory mechanism was created to solve this, but, as described above, it mysteriously broke when we stopped using the bootstrap classloader.
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.4
> Attachments: access.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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] Closed: (HADOOP-217) IllegalAcessException when creating a
Block object via WritableFactories
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=all ]
Doug Cutting closed HADOOP-217:
-------------------------------
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.3.0
> Attachments: access.patch, block.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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] Commented: (HADOOP-217) IllegalAcessException when creating
a Block object via WritableFactories
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=comments#action_12413899 ]
Sameer Paranjpye commented on HADOOP-217:
-----------------------------------------
This does not appear to hamper normal DFS operation in any way. Looks like the Block constructor is registered as a writable factory but is not public. Does it need to be? Should Block objects ever be constructed this way?
This needs further investigation, making the constructor public just addresses the symptom, not the problem IMO. Need to figure out what part of the code is trying to create blocks through a writable factory, and should it be doing that or something different?
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.4
> Attachments: access.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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-217) IllegalAcessException when creating a
Block object via WritableFactories
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=all ]
Hairong Kuang updated HADOOP-217:
---------------------------------
Attachment: block.patch
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.4
> Attachments: access.patch, block.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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] Commented: (HADOOP-217) IllegalAcessException when creating
a Block object via WritableFactories
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=comments#action_12414274 ]
Hairong Kuang commented on HADOOP-217:
--------------------------------------
The exception occurs when we restart dfs after the namenode is reformated. The namenode starts as an empty file system so the Block class is loaded. When the name node receives block reports containing blocks from the previous file system, it throws the exception.
To avoid this, we can either make the Block class public or explicitly load the class in NameNode.
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.4
> Attachments: access.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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-217) IllegalAcessException when creating a
Block object via WritableFactories
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-217?page=all ]
Sameer Paranjpye updated HADOOP-217:
------------------------------------
Fix Version: 0.4
(was: 0.3)
> IllegalAcessException when creating a Block object via WritableFactories
> ------------------------------------------------------------------------
>
> Key: HADOOP-217
> URL: http://issues.apache.org/jira/browse/HADOOP-217
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.4
> Attachments: access.patch
>
> When I ran the dfs namenode, I received an error message listed below. Changing Block class to be public will be able to fix the problem.
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:49)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:226)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:163)
> at org.apache.hadoop.io.ObjectWritable.readObject(ObjectWritable.java:211)
> at org.apache.hadoop.ipc.RPC$Invocation.readFields(RPC.java:88)
> at org.apache.hadoop.ipc.Server$Connection.run(Server.java:154)
> Caused by: java.lang.IllegalAccessException: Class org.apache.hadoop.io.WritableFactories can not access a member of class org.apache.hadoop.dfs.Block with modifiers "public"
> at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
> at java.lang.Class.newInstance0(Class.java:344)
> at java.lang.Class.newInstance(Class.java:303)
> at org.apache.hadoop.io.WritableFactories.newInstance(WritableFactories.java:45)
> ... 5 more
--
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