FULL PRODUCT VERSION :
JRE 1.6update18 and 1.5 update 22

java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)

java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Window XP SP3 (5.1.2600)
Internet Explorer 7

EXTRA RELEVANT SYSTEM CONFIGURATION :
Oracle AS10gr2 running oracle Forms
Network Load Balancer running arrow-point sticky cookies

A DESCRIPTION OF THE PROBLEM :
When utilizing a load balanced Oracle Forms environment, which uses JRE 1.5 update 22 to function and Arrow point cookies within the JSession cookie. The cookie is lost or not called when a broswer get is sent to the server from within the same browser session, while the client has the enable next generation java plugin check box selected in the 1.6 update 18 client. A network trace reveals that the get statement lack the jsession cookie, which is used to direct them to the correct server, where they are processing. All post statements contain the appropriate cookie.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Load JRE 1.5 update 22
Load JRE 1.6 update 18

Launch an application that requires the use of cookies to track the session and the server for continious connectivity and processing

Run a packet capture on the Session to see the cookie appear in both post and get statements.

Enable the Next Generation plugin on the JRE 1.6 Update 18

Rerun the application and the packet capture. The post will contain the cookie, the gets will not.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Java Next Generation Plugin should use all the session cookies from the originating session to keep track of user connection and process, when working with a load balancer
ACTUAL -
Java Next Generation plug-in does not call the cookie and include it in the network connection string when a get command is issued from a new java applet with in the same browser session.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
When Using JRE 1.5 update 22 and JRE 1.6 Update 18 ( No Next Gen)

oracle.uix=0^^GMT-5:00; ARPT=LKZYVJS10.107.25.32CKMOK; OHS-forms.aidomain.net-80=7B234B47CBFDCE0BAD2320703C818840F09986F09A5D44202A48F349DEBCD7A5FC41185D7EEB53E620E367B8D6943CAA9369ABC125A87B12EBBDB535012FF4C09CAC44AEBB8078719DB7EBF3F6C5F5CE60CA2CACACEFDA287002713EE6C44C538630F1675A7B734975490E868E5D37DB75D867DCD06354ED56100434BF5E5F8F5DB177A1B04C744207449AB9FD687FCF773E171D7557FF758466A37529661D6EA5D327CAD142F62A3C443B65C0077FFCB2919C751B655FD79434A08AFBC803EBF26BF35ABC287DF2C76DBF581BF6C968CF44C04C193ED79DB6EE772CB9BEBDFB; ShimmerBHO=BHOStatus:I

Wne Using JRE 1.5 update 22 and JRE 1.6 Update 18 (Next Gen plugin selected)

oracle.uix=0^^GMT-5:00; ShimmerBHO=BHOStatus:I

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Run JRE 1.5 update 22 and JRE 1.6 update 18 without the Next Generation java plugin enabled. This will allow all jre function to remain at the 1.5 update 22 level