You've got to be real careful about loading native classes, and, in
particular, not load them twice under two different loaders. (At
least that's my vague recollection.)
On Sep 23, 10:12 pm, ls02 agal...@audible.com wrote:
So what's the proper way to deal with such issue?
On Sep 23, 10:39 pm,
But we have one single shared library that is used by numerious
classes and instances. Note, the problem occurs very seldom. I never
personally saw it.
On Sep 24, 7:38 am, DanH danhi...@ieee.org wrote:
You've got to be real careful about loading native classes, and, in
particular, not load them
This is an area that is poorly described in the docs (if at all). The
real specification is in the JCK test cases, which is why I gained a
slight familiarity with it. You have to read the test cases and
figure out why your Java implementation is failing them to
understand the spec.
My vague
Ah, it kinda came back to me a little more. In your particular case
where you have multiple classes referencing the lib you see this:
Native class A is loaded under loader X and loads the lib under that
loader. Native class B is loaded under loader Y and attempts to load
the lib under that
On Sep 24, 10:11 am, DanH danhi...@ieee.org wrote:
Ah, it kinda came back to me a little more. In your particular case
where you have multiple classes referencing the lib you see this:
Native class A is loaded under loader X and loads the lib under that
loader. Native class B is loaded under
If you say so.
On Sep 24, 5:29 pm, fadden fad...@android.com wrote:
On Sep 24, 10:11 am, DanH danhi...@ieee.org wrote:
Ah, it kinda came back to me a little more. In your particular case
where you have multiple classes referencing the lib you see this:
Native class A is loaded under
On regular Java systems this can occur when the native class gets
loaded by the wrong class loader. And there are a couple of other
obscure causes with regard to class loading, IIRC.
On Sep 23, 7:34 pm, ls02 agal...@audible.com wrote:
From time to time we get from customers the following error
So what's the proper way to deal with such issue?
On Sep 23, 10:39 pm, DanH danhi...@ieee.org wrote:
On regular Java systems this can occur when the native class gets
loaded by the wrong class loader. And there are a couple of other
obscure causes with regard to class loading, IIRC.
On Sep
8 matches
Mail list logo
