So the jar in the original ear is a valid jar, but the one under the nodeagent directory is not. Can you also check the copy under DAS, $GF_INSTALL/domains/domain1/applications/j2ee-apps/bilo-ear-1.1/nrr-4.4.6.jar
During cluster deployment, the application bits first got expanded under DAS, then the node agent synchronize the bits over to instance. From your earlier posts, this does seem like the synchronization process did not happen properly.
Can you post the stack trace of that synchronization exception? Also can you post the steps that could reproduce this problem if you can reproduce it consistently on your box?
[Message sent by forum member 'hzhang_jn' (hzhang_jn)]
http://forums.java.net/jive/thread.jspa?messageID=249919