[ clif-Bugs-300446 ] ClassNotFoundException at injector deployment (v0.2a4)

[<noreply@xxxxxxxxxxxxxxxxxxx>]

Bugs item #300446, was opened at 11/06/2004 16:15
You can respond by visiting: 
http://forge.objectweb.org/tracker/?func=detail&atid=100057&aid=300446&group_id=57

Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 8
Submitted By: Bruno Dillenseger (dillense)
Assigned to: Bruno Dillenseger (dillense)
Summary: ClassNotFoundException at injector deployment (v0.2a4)

Initial Comment:
When deploying injectors with a console running on a Linux box, exceptions are
thrown, and the console remains idle :

* CLIF server side :

[java] Server XXX is ready.
[java] WARNING: java.lang.ClassNotFoundException:
org.objectweb.clif.storage.api.StorageWriteService
[java] WARNING: java.lang.ClassNotFoundException:
org.objectweb.clif.storage.api.StorageProxyAdmin
[java] p0.3 Exception java.lang.ClassNotFoundException:
org.objectweb.clif.storage.api.StorageWriteService

* console side :

[java] Fractal registry is ready.
[java] {XXX=Injector and Probe deployment...}
[java] org.objectweb.fractal.rmi.RemoteException: server side exception:
java.lang.ClassNotFoundException:
org.objectweb.clif.storage.api.StorageWriteService
[java] at
org.objectweb.fractal.api.factory.GenericFactory_Stub.newFcInstance(Unknown 
Source)
[java] at
org.objectweb.clif.console.api.ClifServerReference.<init>(ClifServerReference.java:111)


----------------------------------------------------------------------

>Comment By: Bruno Dillenseger (dillense)
Date: 11/06/2004 16:42

Message:
connecté 
user_id=291

The faulty part is the embedded pseudo-web server
responsible for delivering CLIF classes and resources to the
RMI classloader of the CLIF servers. Depending on the
runtime environment, it sometimes delivers corrupted Jar or
classes, leading to a ClassNotFoundException in the CLIF
server and a deployment failure.
This comes from a character encoding problem when reading
the class or Jar files and sending them to the CLIF servers.
The pseudo-web server relies on the
InputStreamReader/OutputStreamWriter classes with the
default character encoding. According to Sun JDK1.3
documentation, "every instance of the Java virtual machine
has a default character encoding. The default encoding is
determined during virtual-machine startup and typically
depends upon the locale and encoding being used by the
underlying operating system." In some enviroments, this
default encoding is 7-bit ASCII, leading to corrupted bytes
(the most significant bit set to 0).

----------------------------------------------------------------------

You can respond by visiting: 
http://forge.objectweb.org/tracker/?func=detail&atid=100057&aid=300446&group_id=57