Re: 3-D display locking up under NT, jdk1.2.2, Java 3D 1.2

• To: visad-list@xxxxxxxxxxxxx
• Subject: Re: 3-D display locking up under NT, jdk1.2.2, Java 3D 1.2
• From: Curtis Rueden <curtis@xxxxxxxxxxxxx>
• Date: Thu, 08 Jun 2000 20:30:36 -0500

Steve,

Many VisAD operations in Java3D 1.2 cause that same ArrayOutOfBoundsException
to be thrown.  VisAD also currently uses mixed mode immediate rendering in
Java3D, which does not work properly in Java3D 1.2 (you will find that VisAD
displays generate an infinite sequence of DisplayEvent.FRAME_DONE events).
The Java3D team has fixed the latter problem for the next release, but I do
not know about the former problem.  I will file a bug report about it soon.

My advice to everyone is to steer clear of Java3D 1.2, and instead use
Java3D 1.1.3, which is still accessible from the Java3D web site.

-Curtis

At 16:29 08-06-00 -0600, you wrote:
>Hi,
>
>I'm having a problem with a VisAD 3-D display on a Windows NT system.
>At a variable point in the application, the 3-D VisAD display locks up
>(i.e. hangs) and the following error message is emitted:
>
>     java.lang.ArrayIndexOutOfBoundsException: 0
>     Warning: Domain values not strictly monotonic; adjusting...
>     java.lang.IndexOutOfBoundsException: Index: -1, Size: 16
>             at java.util.ArrayList.RangeCheck(ArrayList.java, Compiled Code)
>             at java.util.ArrayList.get(ArrayList.java, Compiled Code)
>             at 
> javax.media.j3d.RenderBin.removeOrderedHeadLightBin(RenderBin.java:3108)
>             at javax.media.j3d.RenderBin.removeLightBin(RenderBin.java:3590)
>             at 
> javax.media.j3d.LightBin.removeEnvironmentSet(LightBin.java:318)
>             at 
> javax.media.j3d.EnvironmentSet.removeAttributeBin(EnvironmentSet.java:360)
>             at 
> javax.media.j3d.AttributeBin.removeTextureBin(AttributeBin.java:247)
>             at 
> javax.media.j3d.TextureBin.removeRenderMolecule(TextureBin.java:297)
>             at 
> javax.media.j3d.RenderMolecule.updateRemoveRenderAtoms(RenderMolecule.java, 
> Compiled Code)
>             at javax.media.j3d.RenderBin.updateObject(RenderBin.java, 
> Compiled Code)
>
>             at 
> javax.media.j3d.MasterControl.updateMirrorObjects(MasterControl.java, 
> Compiled Code)
>             at javax.media.j3d.MasterControl.runMonitor(MasterControl.java, 
> Compiled Code)
>             at javax.media.j3d.MasterControl.doWork(MasterControl.java, 
> Compiled Code)
>             at 
> javax.media.j3d.MasterControlThread.run(MasterControlThread.java:28)
>
>The environment is Sun's jdk1.2.2 and Sun's Java 3D 1.2.
>
>Has anyone else encountered this?
>
>--Steve

• References:
  • 3-D display locking up under NT, jdk1.2.2, Java 3D 1.2
    • From: Steve Emmerson