Reminder: Migrate Your JInitiator Clients to Sun JRE Now!

[June 29, 2009 Update: The July 2009 desupport date for JInitiator 1.3 applies to E-Business Suite customers only. Generic Oracle Forms customers should see Note 761159.1 for generic JInitiator desupport dates.]

The significance of many problems lessens over time, so procrastination has its place as a stress management technique.  Unfortunately, putting off your EBS end-user migration from Oracle JInitiator to the native Sun Java plug-in doesn't fall into that category.  We are down to the last grains of sand in this particular hourglass.

Oracle E-Business Suite Release 11i end-users access Forms-based content either with the native Sun Java Runtime Engine (JRE) client or Oracle JInitiator.  Oracle JInitiator comes in two flavors: 1.8 and 1.3.  The sun is setting for both JInitiator versions.

Error Correction Support (ECS) for JInitiator 1.1.8 will end on December 31, 2008.  In other words, the Oracle Forms group will no longer issue bug fixes for the JInitiator 1.1.8 codeline as of tomorrow.

Error Correction Support for JInitiator 1.3 for E-Business Suite Release 11i customers will end on July 31, 2009.

Diagram showing Forms JRE JInitiator desktop client architecture layers

Why Did We Once Need JInitiator At All?

Some additional background might be useful here:  Oracle JInitiator was originally released as a licenced version of Sun's Java client back when specific features were required to support Oracle Forms. This was particularly necessary for E-Business Suite Forms-based functionality, since the E-Business Suite pushed the envelope of what Forms and Java could do collectively from a user interface perspective.

Sun has since incorporated all of the enhancements needed to support Oracle Forms into their native Sun Java plug-in. This eliminates the need for Oracle to package its own Java client just for running Oracle Forms-based applications.

What Are the Support Implications for JInitiator Users?

Here's what you can expect if you log an Oracle E-Business Suite Release 11i service request against JInitiator after the respective dates shown above:

  1. Oracle Support will help you diagnose and isolate the root cause of any compatibility issues between JInitiator and the E-Business Suite.

  2. If there's a workaround or an existing Forms or JInitiator patch, Oracle Support will help you obtain the fix.

  3. If the issue requires a new Forms patch and can be reproduced using the native Sun JRE plug-in, a new bug will be logged against Oracle Forms.

  4. If the issue cannot be reproduced with the native Sun JRE client, no new Forms or JInitiator bugs will be logged.

What Do You Do Now?

If you haven't already started migrating your end-users to the native Sun JRE plug-in, I'd strongly recommend that you begin this process immediately.

Apps 11i is certified with the native Sun Java (JRE) plug-in. You can use any JRE release from 1.5.0_13 and higher, or 1.6.0_03 and higher.  Your end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either codelines -- without waiting for Oracle to certify these new JRE plug-ins with EBS 11i.

Why Choose the native Sun JRE over JInitiator 1.3?

Upgrading your Apps 11i end-users to the native Sun JRE directly will be less time-consuming and disruptive than upgrading them first from JInitiator 1.1.8 to 1.3 and then upgrading them again to the native Sun Java client before the July 2009 deadline.

The elimination of Oracle JInitiator simplifies your desktop administration environment.  Apps DBAs who have migrated their users to the native Sun JRE no longer have to struggle with compatibility and coexistence problems between JInitiator and other Java runtime clients on the same desktop.

Which JRE Versions Are Certified With Which Browsers?

This depends on your Windows operating version and the browser that your firm has deployed. Various combinations of Windows XP, Windows Vista, Microsoft Internet Explorer (IE) 6 and 7, and Firefox are now certified with JRE 1.5 and 1.6. To review the new minimum certification levels, see:

Related Articles

Comments:

We recently migrated to JRE from jinitiator 1.3.
Here are our experiences:

Installing the JRE plugin requires user to be at least "Power User". Many of our users are not power users.
So, this requires some kind of automated pushing the jre software to users.
This is the same requirement for jinitiator too.
The issue gets complex due to the need to maintain the JRE up to date and keep the user's desktop secure. This requires uninstalling the old versions and installing new versions.
Unfortunately, we don't have any automated tools to do this at this time. Going forward, we are trying to use MS' System Management Server to automate that.

What are your thoughts on this and could you suggest any tools that could help with that?

Thanks for your wonderful blog,
Rama Nalam

Posted by Rama Nalam on December 31, 2008 at 02:49 AM PST #

Hi, Rama,

Congratulations on your migration, and thanks for sharing your experiences with our readers.

Keeping JRE up-to-date is like any other update to software on your end-users' desktops. I would presume that you have to periodically update your end-users' antivirus scanners, malware protection, browsers, Windows security patches, and so on.

I'd infer from your email address that your organization is part of a larger statewide organization that has standardized tools for deploying desktop updates. It might be worthwhile contacting your peers in your sister organizations at the state level to see whether they have negotiated site licences for desktop administration tools like MS SMS (which is one of the most commonly-used tools for Windows desktops, in my experience).

There are many other desktop administration tools, of course. Unfortunately, I have limited visibility into this space and lack sufficient hands-on experience to recommend one tool over another. Other readers might chime in with their experiences, if we're lucky.

Regards,
Steven

Posted by Steven Chan on December 31, 2008 at 08:04 AM PST #

It might be worth noting that JRE6u11 (and possibly u10 as well) don't push out properly via an .msi, it should be fixed in u12 though.

Posted by Ian Neal on January 01, 2009 at 08:26 AM PST #

Hi, Ian,

Thanks for that tip. I wasn't aware of that issue. I hope Sun resolves this soon.

Regards,
Steven

Posted by Steven Chan on January 02, 2009 at 04:17 AM PST #

Steven or any of you smart gentlemen,

We recently migrated to Oracle version 12 and have many of our users experiencing loss of focus on the forms (ie, cannot click on fields or tab to fields). Can you tell what version of Java we should have installed on workstations and/or how could we resolve this issue.

Thanks,
Trevin Montgomery
678-455-8953

Posted by Trevin Montgomery on January 07, 2009 at 11:09 PM PST #

Trying to gather some info.

We have an out of date version of Sun JRE that is installed on the WebForms server. I need to know if there will be any issues if we upgrade to the latest version of Sun JRE on the server?

Posted by RENE on January 08, 2009 at 03:42 AM PST #

Hi, Rene,

There shouldn't be any problems in upgrading your application-tier Java components to the latest certified versions. See this article for JDK 1.6 certification information for EBS Release 11i:

Java SE 6 Certified With Release 11i - http://blogs.oracle.com/stevenChan/2007/09/java_se_6_certified_with_relea.html

Regards,
Steven

Posted by Steven Chan on January 09, 2009 at 02:22 AM PST #

Hi, Trevin,

You should ensure that you have JRE 1.6.0_03 -- at minimum -- installed on your desktops. If possible, I'd recommend installing the latest 1.6.x version available from Sun. Instructions are linked from this article:

Sun Java Plug-in 1.6.0_10 Certified with the E-Business Suite - http://blogs.oracle.com/stevenChan/2008/10/sun_java_plugin_160_10_certified_with_the_ebusines.html

It's also possible that your R12 environment might not have all of the Forms prereqs that resolve common focus-related issues. Check the same documentation linked above for those prereqs.

If you still encounter focus-related issues, log a formal Service Request via Metalink and one of our Support engineers will help you work through this.

Regards,
Steven

Posted by Steven Chan on January 09, 2009 at 02:41 AM PST #

Hi there,

We are in the process of migrating our E-Business Suite 11.5.10.2 installations from using Jinitiator 1.3.1.26 to SUN JRE 1.6.0_11.

One question that we are trying to get an answer from Oracle from is this:

Using Jinitiator with SSL we need to have a file called certdb.txt on the user's PC to allow them to make a secure connection. What is the equivalent file when using SUN JRE ?

Many thanks,

Dave Shipway,
Oxford University

Posted by David Shipway on January 13, 2009 at 11:10 PM PST #

Hi, Dave,

I'll look into this and post an update here. I'm not sure why this isn't already covered in Note 290807.1, but I'll ensure that that gets added to our official documentation, too.

Regards,
Steven

Posted by Steven Chan on January 14, 2009 at 05:45 AM PST #

Hi Steven,

Great blog!! - keep up the good work.

Configuration
==============
- 11.5.10.2 on Linux.
- Using forms servlet
- J2sdk 1.4.2_04 on the server.
- JRE version 1.6.0_11 Java HotSpot(TM) Client VM
on the client.

We're seeing persistent although intermittent and seemingly random crashes of the client forms sessions. The forms process is still there on the server after the crash (for about 10-15mins when it get's cleaned up), but the java and IE session seemingly crashes. No focus in the form, console stops logging and no buttons click etc. No error messages reported on the client. Users have to restart their browsers to log back in (IE6 and IE7)

Nothing to indicate what the issue might be in the java console and I've not been able to find anything in any of the server side logs that I've looked at.

I'll most likely raise an SR in the morning, but wondered if you'd come across this before, and whether there are any compatibility issues with having J2sdk 1.4.2 on the server and using jre 1.6.0 plugin on the client?

Thanks and regards,

Connell.

Posted by Connell on January 15, 2009 at 06:10 AM PST #

Hi, Connell,

Thanks for the problem report as well as your feedback on our blog.

I'm sorry to hear that you're encountering this issue. There should be no issues with having J2SE 1.4.2 on the application tier and JRE 1.6.0 on the client. The JRE clients should be backwards-compatible with earlier JDK/J2SE releases.

However, you may be encountering a variant of the more-common mouse focus issues that a few others have reported. This may be due to the Forms 6i patchset level on your EBS 11i application tier.

Support has just published an excellent diagnostic note with tips on troubleshooting these types of issues. See:

Troubleshooting Mouse Focus Issues Using JRE Clients with EBS 11i - http://blogs.oracle.com/stevenChan/2009/01/troubleshooting_mouse_focus_issues_using_jre_client_ebs11i.html

Please drop me an email or post your SR number; we're trying to track these issues closely.

Regards,
Steven

Posted by Steven Chan on January 15, 2009 at 06:55 AM PST #

Hi Steven,

Thanks for the update. SR No is SR:7377866.992. In the meantime I'm looking into the diagnostic notes and also whether I can reproduce the hang with jinitiator.

Thanks again, Connell.

Posted by Connell McMenamin on January 19, 2009 at 05:56 PM PST #

Hi, Connell,

Thanks for the SR number. We'll be working with your Support engineer on this one.

Regards,
Steven

Posted by Steven Chan on January 20, 2009 at 06:49 AM PST #

Hello Dave,

I hope the latest update on your SR has resolved your question, but please update the SR if you need to discuss further.

The certdb.txt file in Jinitiator stores the CA Certificates, so the equivilent in JRE is the "cacerts" file (which stores the seeded certificates) Any user accepted certificates are stored in seperate files in the users home directory (for example "trusted.cacerts")

Unless you need to work with unrecognized Certificate Authorities (or Client Certificates) you would not normally need to worry about these files as such

You can read more about JRE Plugin security at http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/security.html You may also find the information about "keytool" useful, which is the java tool provided to manage certificate stores. This is documented at http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html

regards

Mike

Posted by Mike Shaw on January 20, 2009 at 05:40 PM PST #

Just wondering if anyone has encountered the problem we are not experiencing.

We have multiple versions of Sun Java installed on our PC's and the server set to tell the client to use at leaset use 1.4.2_06. For some reason the system is connecting to Discoverer exceptionally slow (several minutes) and opens a dialog box that says 'The application requires an earlier version of Java. Do you want to continue? The required version of Java, 1.4.2_13, is not the latest and may not contain the latest security updates.' When we click 'Run' to the above message it launches version 1.6.0_11 and Discoverer opens.

Has anyone else experienced this issue? Any solutions?

Posted by David Eddy on January 25, 2009 at 02:00 AM PST #

Hi, David,

I've heard of situations like this. The solution depends on both your circumstances and your requirements. This all hinges upon how your environment handles "static versioning."

In the EBS world, the expected behavior changes depending upon the specific combination of your JRE release, browser, and EBS JRE setting. We've described a number of different EBS scenarios for handling static versioning in Microsoft IE in Metalink Note 290807.1 (for Apps 11i).

Although this Note is written specifically for EBS, I would suspect that the same principles apply to Discoverer, as well. In fact, I'd be very surprised if they *didn't* apply to Discoverer.

If that Note doesn't help, I'd recommend logging a formal Service Request with details about the JRE versions installed on your desktops, the browser used (i.e. Internet Explorer or Firefox), and the JRE specifications on your applications tier.

Regards,
Steven

Posted by Steven Chan on January 27, 2009 at 08:17 AM PST #

Just wanna share our experience regarding this matter.

Recently, we did 3 different upgrade:
- upgrade to developer 6i patchset 19
- migrated jinitiator to Sun JRE ( j2se1.5.0.17)
- upgrade java to jdk 1.6.0.12

We encountered below issues:

- Cannot view/print pdf and postscipt report.
resolved with patch 5232832

- Simplified chinese and japanese character set issue
Both languages displayed as square instead of actual character. Resolved by installing Albany WT J Font.. note: 240862.1.

Steven,

There is some issue whereby Sun JRE is not get loaded/installed after click on any form responsibility. The page seems to be hanging. This issue happened when user PC's already have highest version of Sun JRE compared to the apps server. For ex: we installed sun jre 1.5.0.17 on apps server. If user PC had higher than that, it may facing that issue. What we did is uninstall the java on user PC. Is there any other way to overcome this issue?

Thanks

Posted by Anuar on February 15, 2009 at 01:09 PM PST #

Hi, Anuar,

Thanks for sharing your experiences with the Sun JRE. It's possible that your environment isn't configured correctly. For example, there may be a conflict between the installed JRE on the desktop and the JRE that your EBS environment is requesting.

Rather than debug that here, I'd recommend logging a formal Service Request via Metalink to get one of our ATG Support specialists engaged. If your SR gets bogged down for some reason, please feel free to email it to me.

Regards,
Steven

Posted by Steven Chan on February 17, 2009 at 03:40 AM PST #

hi can someone help me out!!!! i am trying to access oracle rapid webbased application and when i logon i am getting a runtime error because i have java and jinitiator installed on my pc ,if i uninstall java it works fine , but i need java installed for some other applications please can someone help me out with this ?? Do i have to change any settings???

Posted by sunil on February 26, 2009 at 12:11 PM PST #

Hi, Sunil,

I'm not familiar with the "Oracle Rapid Webbased Application." This doesn't sound like an E-Business Suite product module.

I'd recommend logging a formal Service Request via Metalink against that product to more assistance with this one.

Regards,
Steven

Posted by Steven Chan on February 27, 2009 at 07:57 AM PST #

hi steven ,thanks for your reply will explain you my issue ,

A User is accessing a java application via IExplorer 6 on XP SP1 using Sun JRE
1.4.2_04. No problems when only accessing this application. However, when
user opens another IExplorer window at the same time to access an Oracle 11i
application which uses a JInitiator 1.3.1.18 browser add-on, the user will
get:

“Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\ProgramFiles\
InternetExplorer\iexplore.exe Abnormal program termination”.

Once user clicks OK on error, both IExplorer windows crash, i.e., they
disappear. Client needs to have both applications open simultaneously. The
Oracle 11i application does not have a specific JRE requirement. A native JRE
1.3.1.18 version was installed but we have removed, rebooted and installed 1.
4.2_04 JRE. The Oracle 11i application does use a Jinitiator 1.3.1.18 which
is a self-contained separate plug-in. Using either application using
IExplorer one at a time is no problem but as soon as they are both open at
same time in 2 different browser windows, that is when runtime error occurs.
]

could you please help me in fixing this as the user needs both java and jinitiator to be working for his applications

Posted by sunil on March 03, 2009 at 03:57 PM PST #

Sunil,

This sounds remarkably similar to a query I just handled about an Australian organization. If you haven't already done so, I'd recommend logging a formal Service Request via Metalink to get one of our Support Engineers engaged.

Until then, here's are my notes that I shared with the Australian consultant:

IE can only use a single JVM at a time (this is an Internet Explorer limitation and will apply also to JRE, too). Attempts to use a different JVM will cause IE crashes.

It is theoretically possible to start a new IE session with a different JVM, even while another IE session is still running. The catch lies in how this new session is started.

If you hit Ctrl+N while in IE, that's just opening a new window, not a new IE session. The only way to start a new IE session is to click the IE icon on your Start Menu. This behaviour is true for IE 7. I don't know if this is true for IE 6, though -- and I see you're using IE 6.

If this doesn't work, I'd recommend trying to reproduce the behaviour with IE 7. If multiple IE 7 sessions still cause crashes, then... well, you may wish to consider moving to the Sun JRE. Switching from JInitiator to the native Sun JRE should simplify your life, since the absence of JInitiator means just one less JVM to deal with. If I were in your shoes, I'd make sure that all of my Java-based applications all run on the same JRE release.

This includes E-Business Suite, of course. That's why we've tried to give you as many certified JRE options for EBS as possible: 1.5.0_13 and higher or 1.6.0_03 and higher. We don't want the E-Business Suite to be the one application holding you back.

Once you've got your Java applications on the same JRE level, desktop management issues like the one's you're experiencing now pretty much go away.

Regards,
Steven

Posted by Steven Chan on March 04, 2009 at 06:56 AM PST #

Hi Steven,

We migrated to JRE on one of our instances. For some people draging forms around the screen is very slow. It can take 10 seconds for a form to move from one locaiton to another. Is there a fix for this?

We are running:
- 11.5.10.2 on Linux.
- JRE version 1.6.0_12

Posted by Ryan Morehouse on March 04, 2009 at 10:06 PM PST #

Hi, Ryan,

I'm sorry to hear that you've been bitten by this. It appears to be a hardware-specific issue with the Sun JRE.

I've heard reports of this with all JRE releases up to and including JRE 1.6.0_12. This appears to be a Sun JRE issue with certain graphics cards and drivers (including nVidia Feforce, nVidia Quadro, and ATI Radeon cards).

This has been reported to Sun, and we're waiting for a fix from them. In the interim, a possible workaround is described in Note 757618.1 (cross-referenced from Notes 290807.1 and 393931.1).

For a permanent fix, we're waiting for Sun to resolve their bug #6635462:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6635462

If you're encountering different behaviour on different hardware than described in the above Notes and Sun bug, please log a formal Service Request via Metalink and send me the details.

Regards,
Steven

Posted by Steven Chan on March 05, 2009 at 03:07 AM PST #

Hello,

I am having an issue with Oracle Forms 10g. If I use the Sun Java JRE 1.6.0_02 I am unable to use the mouse to select a record in the data block, the form appears to be frozen on the first record. If I use jinitiator the form works fine, whichever record I select becomes highlighted.

Is there a specific version of JRE that I should be using with Forms 10g?

Regards

Cameron

Posted by Cameron Abbott on March 10, 2009 at 11:20 PM PDT #

Hello, Cameron,

I'm assuming that you're using some version of Oracle E-Business Suite 12. You can use JRE 1.6.0_03 and higher with EBS 12. I'd recommend using the latest 1.6.0_12 update.

If this is for a custom Forms 10g application and not the E-Business Suite Release 12, I'd recommend logging a Service Request against the Forms product for guidance on their certified JRE levels.

Good luck with this one.

Regards,
Steven

Posted by Steven Chan on March 12, 2009 at 02:45 AM PDT #

Hi Steven,
I've decided to change from JInitiator(1.3.1) to JRE (6u13) in our CRP instance and followed the instructions on ML Note 290807.1. Everything went well, but now if I try using any browser, I click on System Administrator responsibility and get a blank page with the following:
"Please make sure that JDK 1.6.0_13 is installed on your client. To download JDK 1.6.0_13 plugin you can visit http://finappstest01kt.seattlepacificindustries.com:8002/OA_HTML/oaj2se.exe. Please contact your System Administrator to know the correct version of the plugin."
If I click on the link it downloads plugin and next time it asks for the same thing, I openned an SR with Oracle support (21054158.6 ). They verified that JRE install went fine and now they want me to patch my Developer 6i. It is a lot of work to install 8+ patches and deal with unpredictable results (if you ask me). I don't see the benefit of going through all that if can ride JInitiator for some time and then, maybe upgrade to 12.

Any suggestions?
Thanks,
Eugene

Posted by Eugene on April 10, 2009 at 02:52 AM PDT #

Hi, Eugene,

The unfortunate reality of this business is that keeping up with the latest technologies (e.g. Vista and JRE clients) requires ongoing updates to things like Forms and the EBS techstack.

I reviewed your SR. Support's recommendations are correct: to use the latest Sun JRE client, you need to be at a certain Forms and ATG RUP prerequisite level on your EBS mid-tier.

Best of luck with your upgrade. Please feel free to let me know if you log SRs for any issues that you might run into.

Regards,
Steven

Posted by Steven Chan on April 13, 2009 at 07:04 AM PDT #

We just migrated from Jinitiator 1.3.1 to JRE 1.5.0_19-b02 and having issues with mouse navigation with our custom forms 10g applications. Has anyone encountered this issue? Please let me know what I need to do to fix this.

Thanks,
Srini

Posted by Srini on July 13, 2009 at 05:08 AM PDT #

Hello Srini,

I am not clear if you are using eBusiness Suite or standalone Forms Server, but in either case it would probably be best to raise a Service Request with Oracle Support (with either the eBiz team or Forms team respectively) in order we can investigate the exact circumstances of your issue.

For eBusiness Suite 11i customers having this kind of issue, there is Note 760250.1 "Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i" which may be useful to help diagnosing the root cause

Hope this helps

Mike Shaw

Posted by Mike Shaw on July 13, 2009 at 04:03 PM PDT #

Hi Steven,

I have been following your blog with interest, and wonder if you can clarify a situation please - or direct me to a contact in Oracle to obtain clarification.

We have recenlty upgraded our desktops to Sun JRE 1.5.0_16 for use with eBusiness 11.5.10 - as per your postings to move off JInitiator.

I need some clarification around the supported levels of JRE clients. Reading around there are references to the minimum supported JRE's. However with Sun's End of Life date for 1.5 does this not impact the support?
Also, is there a date planned where Oracle would no longer support eBusiness on JRE 1.5 clients, prompting a move to 1.6

Thanks for you help
Regards
Adam

Posted by Adam Fidler on July 13, 2009 at 09:22 PM PDT #

Hello, Adam,

Thanks for the feedback on our blog. Glad to hear that you've found it useful.

You might find the following article useful:

Understanding J2SE 1.5 End-of-Life Implications for Oracle E-Business Suite -
http://blogs.oracle.com/stevenChan/2009/06/understanding_j2se_15_endoflife_implications_for_apps.html

Feel free to let me know if you have any additional questions.

Regards,
Steven

Posted by Steven Chan on July 14, 2009 at 03:51 AM PDT #

We are in the process of converting from Jinit 1.3.1.29 to Sun's JVM 1.5.0_18-b02. The version of the JVM we run is controlled by another COTS package.

We are running into some issues with Sun’s JVM

1.Sometimes when launching a custom Oracle Forms (10.1.2.3) application the system will core dump and generate a log file. The header of the log file is below.

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d1f8111, pid=2548, tid=1788
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_18-b02 mixed mode, sharing)
# Problematic frame:
# C 0x6d1f8111
#

2.After you receive the core dump the next time you try to launch the application you may receive the following error in the forms console window, in the message area.
error:java.lang.ExceptionInitializerError

If you do not close the start page (HTML start page to launch the application) you
Will receive the following message.
error:java.lang.NoClassDefFoundError

If you close the start page and reopen it forms will launch properly.

3.The last issue we have found is forms sometimes seems to freeze and not repaint the screen when selecting menu options.

Let me know if you can help with any of these issues.

Thanks,

John

Posted by John on July 14, 2009 at 11:31 PM PDT #

Hello, John,

I'm afraid that I don't have any insight into the root cause of this. Since this problem is occurring with a generic Forms-based application and not the Oracle E-Business Suite, your best bet might be to log a formal Service Request with the Oracle Forms team directly.

Good luck with this one.

Regards,
Steven

Posted by Steven Chan on July 15, 2009 at 02:23 AM PDT #

Hi Steve,

Thanks for the wonderful blog and your kind quick response. Currently we are in Jinit 1.3.1.29.

I am planning to upgrade J2SE 1.5 but I noticed that (j2se1.5) the end of life is October 2009. What is your suggestion to me? Shall I go with 1.6? We are in 11.5.10.2(EBS).
Thanks
Prince

Posted by Prince Suthakar on October 08, 2009 at 12:10 AM PDT #

Hi, Prince,

If I were an IT manager facing the choice between J2SE 1.5 and 1.6, I'd go with 1.6 without hesitation. There's no real reason to upgrade to a Java release that will be desupported by Sun in a matter of weeks.

Regards,
Steven

Posted by Steven Chan on October 08, 2009 at 02:39 AM PDT #

Hi Steven,

Your blog has proved invaluable whilst migrating from Jinitiator 1.3.1.28 ---> JRE 1.6.0_13. Just want to thank you for your effort.

Currently we have two sets of clients trying to access Ebusiness Suite via JRE. One set who uses JRE controlled via individual desktop level, and another set who access it via some Citrix infrastructure.

The first set at individual desktop level, has been 99% successful bar some slow loading at times (sometimes up to about 4mins). It always seems to be the first time which is slow?

The second set is having serious issues in that it can sometimes take up to 30mins to load the EBS Forms session. Its also sometimes refusing to load at all. This has been very serious and we've had to revert the clients back to Jinit at user profile option level in EBS, which you'll appreciate is not ideal.

In my mind, the odd 4mins loading period (window just appears to be inactive and suddenly pops the core forms session up), is highly unacceptable.

Just really looking for some feedback/advice if you have any.

Massively appreciated.

Many thanks,
Gary

Posted by Gary Lythgoe on October 13, 2009 at 12:18 AM PDT #

Hi, Gary,

Thanks for the feedback on our blog. Glad to hear that you've found it useful.

The slowness of the first load is likely due to the fact that the JRE is downloading from your application tier server to your end-user's desktop. This is a one-time process, since subsequent Forms invocations should notice that the JRE is already installed, and thereby will skip the download.

The second issue you note is not what I'd expect to see. I'd like to ensure that you get some help from us in investigating this. Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on October 19, 2009 at 03:45 AM PDT #

Hi Steven,

We have upgraded to JRE 1.5.0_10 on our R12 instances with Forms 10.1.2.3. Our users are occasionally getting the following:

Exception in thread "AWT-EventQueue-3" java.lang.NoClassDefFoundError: oracle/bali/share/util/BooleanUtils
at oracle.ewt.scrolling.MouseWheelUtils.dispatchMouseWheelEvent(Unknown Source)
at oracle.ewt.event.tracking.GlassMouseGrabProvider$Proxy.processEventImpl(Unknown Source)
at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
at oracle.ewt.lwAWT.LWComponent.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: oracle.bali.share.util.BooleanUtils
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 20 more
Caused by: java.io.IOException: open HTTP connection failed:http://elbert.p2es.com:8001/OA_JAVA/oracle/bali/share/util/BooleanUtils.class
at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
... 24 more

and they are affectively locked out of the application. I haven't been able to find anything similar in MetaLink to help resolve the issue. Any ideas?

Regards,
Pete

Posted by Pete Waller on October 23, 2009 at 05:56 AM PDT #

Hi, Pete,

I'm afraid that I don't have any insight into what might be going on here. I'd like to have one of our JRE experts look into this for you. If this is still an issue, please log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on October 27, 2009 at 02:40 AM PDT #

Hi Steven\Peter,

For what it is worth we have the exact same issue as Peter.

Exception in thread "AWT-EventQueue-3" java.lang.NoClassDefFoundError: oracle/bali/share/util/BooleanUtils
at oracle.ewt.scrolling.MouseWheelUtils.dispatchMouseWheelEvent(Unknown Source)
...

We are running on 11.5.10 ATG6. Dev suite 6i patchset 19 on AIX 5.3\6.1. Using JRE 6u16. I have raised an SR but thought i would mention it here also given Peter's post.

Regards,
Lindsey

Posted by Lindsey McGregor on November 02, 2009 at 12:33 PM PST #

The users get the same error.

Exception in thread "AWT-EventQueue-2" java.lang.NoClassDefFoundError: oracle/bali/share/util/BooleanUtils
at oracle.ewt.scrolling.MouseWheelUtils.dispatchMouseWheelEvent(Unknown Source)

Did any one on the thread get this resolved.

Posted by Rajeev on November 03, 2009 at 12:00 AM PST #

Hi, Lindsey,

I'm sorry to hear that you're hitting the same issue. Thanks for the heads-up on your SR. I would definitely like to monitor this closely. Would you mind emailing your SR number to me?

Regards,
Steven

Posted by Steven Chan on November 03, 2009 at 02:13 AM PST #

Hello. We have migrated from Jinitiator 1.3.1.28 to JRE 1.6.0_16-b01 and are experiencing freezing and crashing issues with Oracle EBS (11.5.10.2). The issue happens sporatically and we are unable to recreate it at will. I've read that having Jinitiator and JRE on the system creates a conflict. Our machines currently have both installed as some of our other applications use Jinitiator. We are not sure what the impact would be on these other applications if we remove Jinitiator (I would think the applications should automatically point to JRE???). Do you have any insight on this? If both JVM's must remain on the machines, any idea on how to resolve the issue? We have been communicating to our users to open separate IE sessions when opening other applications however, we are still having the issue. Some of the users only have Oracle and Outlook open and still freeze and crash. I've found this blog to be very informational but not sure how to go about resolving our issue. One more thing to note, when a user crashes, a log file is created on their desktop. Please see below. The one thing I did notice consistent in all of the log files we've viewed is the problematic frame references mshtml.dll. The only thing I've been able to find on this is to install a new version of IE (we are currently on IE7).

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x3dba2a2a, pid=4356, tid=2296
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [mshtml.dll+0x182a2a]
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

--------------- T H R E A D ---------------

Current thread (0x05f1d400): JavaThread "Thread-0" [_thread_in_native, id=2296, stack(0x08310000,0x08410000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000138

Registers:
EAX=0x00000000, EBX=0x00000000, ECX=0x0000002b, EDX=0x05f1dcbc
ESP=0x0840fa24, EBP=0x0840fa3c, ESI=0x030888a0, EDI=0x7c8097e0
EIP=0x3dba2a2a, EFLAGS=0x00010246

Top of Stack: (sp=0x0840fa24)
0x0840fa24: 00000000 030888a0 26ac9e88 3dadcbe5
0x0840fa34: 030888a0 00000000 0840fa50 3dad5964
0x0840fa44: 030888a0 05f1d400 00205918 0840fa60
0x0840fa54: 3dbd7a08 030888a0 26ac9e88 0840faac
0x0840fa64: 6d4130be 00205918 06219e27 05f1d510
0x0840fa74: 0840fab4 00205918 00000000 05f1dcd4
0x0840fa84: 05f1dcd4 fffffffe 0840fa8c 26ac9e88
0x0840fa94: 0840fac0 26ad1438 00000000 26ac9e88

Instructions: (pc=0x3dba2a2a)
0x3dba2a1a: d4 9c d2 3d 8b 3d 10 13 a2 3d 8b f1 ff d7 33 db
0x3dba2a2a: 39 98 38 01 00 00 74 1f ff 35 d4 9c d2 3d ff d7

Stack: [0x08310000,0x08410000], sp=0x0840fa24, free space=1022k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [mshtml.dll+0x182a2a]
C [mshtml.dll+0xb5964]
C [mshtml.dll+0x1b7a08]
C [jp2iexp.dll+0x30be]
j sun.plugin2.main.server.IExplorerPlugin.javaScriptReleaseObject(Lsun/plugin2/liveconnect/BrowserSideObject;)V+4
j sun.plugin2.main.server.LiveConnectSupport$PerPluginInfo.releaseAllObjects()V+34
j sun.plugin2.main.server.LiveConnectSupport.shutdown(I)V+42
j sun.plugin2.main.server.JVMInstance.unregisterApplet(I)V+63
j sun.plugin2.main.server.JVMInstance.dispose()V+67
j sun.plugin2.main.server.JVMInstance.access$2600(Lsun/plugin2/main/server/JVMInstance;)V+1
j sun.plugin2.main.server.JVMInstance$Listener.jvmExited(Lsun/plugin2/jvm/JVMLauncher;)V+86
j sun.plugin2.jvm.JVMLauncher.fireJVMExited()V+31
j sun.plugin2.jvm.JVMLauncher.access$300(Lsun/plugin2/jvm/JVMLauncher;)V+1
j sun.plugin2.jvm.JVMLauncher$JVMWatcher.run()V+50
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
V [jvm.dll+0xecf9c]
V [jvm.dll+0x1741e1]
V [jvm.dll+0xed167]
V [jvm.dll+0xed1dd]
V [jvm.dll+0x116290]
V [jvm.dll+0x1d0424]
V [jvm.dll+0x173e5c]
C [MSVCR71.dll+0x9565]
C [kernel32.dll+0xb729]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j sun.plugin2.main.server.IExplorerPlugin.iUnknownRelease(J)V+0
j sun.plugin2.main.server.IExplorerPlugin.javaScriptReleaseObject(Lsun/plugin2/liveconnect/BrowserSideObject;)V+4
j sun.plugin2.main.server.LiveConnectSupport$PerPluginInfo.releaseAllObjects()V+34
j sun.plugin2.main.server.LiveConnectSupport.shutdown(I)V+42
j sun.plugin2.main.server.JVMInstance.unregisterApplet(I)V+63
j sun.plugin2.main.server.JVMInstance.dispose()V+67
j sun.plugin2.main.server.JVMInstance.access$2600(Lsun/plugin2/main/server/JVMInstance;)V+1
j sun.plugin2.main.server.JVMInstance$Listener.jvmExited(Lsun/plugin2/jvm/JVMLauncher;)V+86
j sun.plugin2.jvm.JVMLauncher.fireJVMExited()V+31
j sun.plugin2.jvm.JVMLauncher.access$300(Lsun/plugin2/jvm/JVMLauncher;)V+1
j sun.plugin2.jvm.JVMLauncher$JVMWatcher.run()V+50
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub

--------------- P R O C E S S ---------------

Java Threads: ( => current thread )
0x04644400 JavaThread "Thread-2" [_thread_in_native, id=2772, stack(0x08d40000,0x08e40000)]
=>0x05f1d400 JavaThread "Thread-0" [_thread_in_native, id=2296, stack(0x08310000,0x08410000)]
0x04629800 JavaThread "traceMsgQueueThread" daemon [_thread_blocked, id=4744, stack(0x05df0000,0x05ef0000)]
0x045eac00 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=5344, stack(0x05bf0000,0x05cf0000)]
0x045e4800 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2464, stack(0x05af0000,0x05bf0000)]
0x045e3000 JavaThread "Attach Listener" daemon [_thread_blocked, id=4684, stack(0x059f0000,0x05af0000)]
0x045e1c00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=2572, stack(0x058f0000,0x059f0000)]
0x045a3000 JavaThread "Finalizer" daemon [_thread_blocked, id=5564, stack(0x057f0000,0x058f0000)]
0x0459e800 JavaThread "Reference Handler" daemon [_thread_blocked, id=3120, stack(0x04780000,0x04880000)]
0x021f8800 JavaThread "main" [_thread_in_native, id=4720, stack(0x01a60000,0x01b60000)]

Other Threads:
0x0459d000 VMThread [stack: 0x04680000,0x04780000] [id=3560]
0x045f4c00 WatcherThread [stack: 0x05cf0000,0x05df0000] [id=976]

VM state:not at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread: None

Heap
def new generation total 960K, used 154K [0x24ac0000, 0x24bc0000, 0x24d30000)
eden space 896K, 14% used [0x24ac0000, 0x24ae0170, 0x24ba0000)
from space 64K, 40% used [0x24bb0000, 0x24bb68e0, 0x24bc0000)
to space 64K, 0% used [0x24ba0000, 0x24ba0000, 0x24bb0000)
tenured generation total 4096K, used 644K [0x24d30000, 0x25130000, 0x26ac0000)
the space 4096K, 15% used [0x24d30000, 0x24dd12e0, 0x24dd1400, 0x25130000)
compacting perm gen total 12288K, used 1540K [0x26ac0000, 0x276c0000, 0x2aac0000)
the space 12288K, 12% used [0x26ac0000, 0x26c41328, 0x26c41400, 0x276c0000)
ro space 8192K, 63% used [0x2aac0000, 0x2afd9920, 0x2afd9a00, 0x2b2c0000)
rw space 12288K, 53% used [0x2b2c0000, 0x2b934dd0, 0x2b934e00, 0x2bec0000)

Dynamic libraries:
0x00400000 - 0x0049c000 C:\Program Files\Internet Explorer\iexplore.exe
0x7c900000 - 0x7c9b2000 C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f6000 C:\WINDOWS\system32\kernel32.dll
0x6f000000 - 0x6f056000 C:\WINDOWS\SYSTEM32\SYSFER.DLL
0x77dd0000 - 0x77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f02000 C:\WINDOWS\system32\RPCRT4.dll
0x77fe0000 - 0x77ff1000 C:\WINDOWS\system32\Secur32.dll
0x77f10000 - 0x77f59000 C:\WINDOWS\system32\GDI32.dll
0x7e410000 - 0x7e4a1000 C:\WINDOWS\system32\USER32.dll
0x77c10000 - 0x77c68000 C:\WINDOWS\system32\msvcrt.dll
0x77f60000 - 0x77fd6000 C:\WINDOWS\system32\SHLWAPI.dll
0x7c9c0000 - 0x7d1d7000 C:\WINDOWS\system32\SHELL32.dll
0x774e0000 - 0x7761d000 C:\WINDOWS\system32\ole32.dll
0x78130000 - 0x78257000 C:\WINDOWS\system32\urlmon.dll
0x77120000 - 0x771ab000 C:\WINDOWS\system32\OLEAUT32.dll
0x3dfd0000 - 0x3e015000 C:\WINDOWS\system32\iertutil.dll
0x77c00000 - 0x77c08000 C:\WINDOWS\system32\VERSION.dll
0x76390000 - 0x763ad000 C:\WINDOWS\system32\IMM32.DLL
0x773d0000 - 0x774d3000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
0x5d090000 - 0x5d12a000 C:\WINDOWS\system32\comctl32.dll
0x3e1c0000 - 0x3e78d000 C:\WINDOWS\system32\IEFRAME.dll
0x76bf0000 - 0x76bfb000 C:\WINDOWS\system32\PSAPI.DLL
0x5ad70000 - 0x5ada8000 C:\WINDOWS\system32\UxTheme.dll
0x74720000 - 0x7476c000 C:\WINDOWS\system32\MSCTF.dll
0x00d40000 - 0x01005000 C:\WINDOWS\system32\xpsp2res.dll
0x755c0000 - 0x755ee000 C:\WINDOWS\system32\msctfime.ime
0x5dff0000 - 0x5e01f000 C:\WINDOWS\system32\IEUI.dll
0x76380000 - 0x76385000 C:\WINDOWS\system32\MSIMG32.dll
0x4ec50000 - 0x4edf6000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5581_x-ww_dfbc4fc4\gdiplus.dll
0x47060000 - 0x47081000 C:\WINDOWS\system32\xmllite.dll
0x77b40000 - 0x77b62000 C:\WINDOWS\system32\apphelp.dll
0x76fd0000 - 0x7704f000 C:\WINDOWS\system32\CLBCATQ.DLL
0x77050000 - 0x77115000 C:\WINDOWS\system32\COMRes.dll
0x746f0000 - 0x7471a000 C:\WINDOWS\System32\msimtf.dll
0x77a20000 - 0x77a74000 C:\WINDOWS\System32\cscui.dll
0x76600000 - 0x7661d000 C:\WINDOWS\System32\CSCDLL.dll
0x77920000 - 0x77a13000 C:\WINDOWS\system32\SETUPAPI.dll
0x325c0000 - 0x325d2000 C:\Program Files\Microsoft Office\OFFICE11\msohev.dll
0x61930000 - 0x6197a000 C:\Program Files\Internet Explorer\ieproxy.dll
0x061f0000 - 0x06205000 C:\WINDOWS\system32\SSSensor.dll
0x7d1e0000 - 0x7d49c000 C:\WINDOWS\system32\msi.dll
0x7e720000 - 0x7e7d0000 C:\WINDOWS\system32\SXS.DLL
0x3d930000 - 0x3da00000 C:\WINDOWS\system32\WININET.dll
0x01840000 - 0x01849000 C:\WINDOWS\system32\Normaliz.dll
0x75cf0000 - 0x75d81000 C:\WINDOWS\system32\MLANG.dll
0x71ab0000 - 0x71ac7000 C:\WINDOWS\system32\ws2_32.dll
0x71aa0000 - 0x71aa8000 C:\WINDOWS\system32\WS2HELP.dll
0x10000000 - 0x10011000 C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEHelperShim.dll
0x02250000 - 0x022eb000 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCR80.dll
0x7c420000 - 0x7c4a7000 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCP80.dll
0x021d0000 - 0x021e0000 C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEHelper.dll
0x6d440000 - 0x6d44c000 C:\Program Files\Java\jre6\bin\jp2ssv.dll
0x7c340000 - 0x7c396000 C:\Program Files\Java\jre6\bin\MSVCR71.dll
0x6dae0000 - 0x6daf2000 C:\Program Files\Java\jre6\lib\deploy\jqs\ie\jqs_plugin.dll
0x71a50000 - 0x71a8f000 C:\WINDOWS\system32\mswsock.dll
0x662b0000 - 0x66308000 C:\WINDOWS\system32\hnetcfg.dll
0x71a90000 - 0x71a98000 C:\WINDOWS\System32\wshtcpip.dll
0x76ee0000 - 0x76f1c000 C:\WINDOWS\system32\RASAPI32.dll
0x76e90000 - 0x76ea2000 C:\WINDOWS\system32\rasman.dll
0x5b860000 - 0x5b8b5000 C:\WINDOWS\system32\NETAPI32.dll
0x76eb0000 - 0x76edf000 C:\WINDOWS\system32\TAPI32.dll
0x76e80000 - 0x76e8e000 C:\WINDOWS\system32\rtutils.dll
0x76b40000 - 0x76b6d000 C:\WINDOWS\system32\WINMM.dll
0x769c0000 - 0x76a74000 C:\WINDOWS\system32\USERENV.dll
0x71d40000 - 0x71d5b000 C:\WINDOWS\system32\actxprxy.dll
0x77c70000 - 0x77c94000 C:\WINDOWS\system32\msv1_0.dll
0x76d60000 - 0x76d79000 C:\WINDOWS\system32\iphlpapi.dll
0x722b0000 - 0x722b5000 C:\WINDOWS\system32\sensapi.dll
0x76fc0000 - 0x76fc6000 C:\WINDOWS\system32\rasadhlp.dll
0x76f20000 - 0x76f47000 C:\WINDOWS\system32\DNSAPI.dll
0x42b80000 - 0x42b8a000 C:\WINDOWS\system32\jsproxy.dll
0x75c50000 - 0x75ccd000 C:\WINDOWS\system32\jscript.dll
0x76fb0000 - 0x76fb8000 C:\WINDOWS\System32\winrnr.dll
0x76f60000 - 0x76f8c000 C:\WINDOWS\system32\WLDAP32.dll
0x71f80000 - 0x71f84000 C:\WINDOWS\system32\security.dll
0x3da20000 - 0x3dd95000 C:\WINDOWS\system32\mshtml.dll
0x746c0000 - 0x746e9000 C:\WINDOWS\system32\msls31.dll
0x76c30000 - 0x76c5e000 C:\WINDOWS\system32\WINTRUST.dll
0x77a80000 - 0x77b15000 C:\WINDOWS\system32\CRYPT32.dll
0x77b20000 - 0x77b32000 C:\WINDOWS\system32\MSASN1.dll
0x76c90000 - 0x76cb8000 C:\WINDOWS\system32\IMAGEHLP.dll
0x72d20000 - 0x72d29000 C:\WINDOWS\system32\wdmaud.drv
0x72d10000 - 0x72d18000 C:\WINDOWS\system32\msacm32.drv
0x77be0000 - 0x77bf5000 C:\WINDOWS\system32\MSACM32.dll
0x77bd0000 - 0x77bd7000 C:\WINDOWS\system32\midimap.dll
0x72cf0000 - 0x72cf7000 C:\WINDOWS\system32\msadp32.acm
0x74980000 - 0x74a94000 C:\WINDOWS\system32\msxml3.dll
0x1b000000 - 0x1b00c000 C:\WINDOWS\system32\ImgUtil.dll
0x41e30000 - 0x41e3e000 C:\WINDOWS\system32\pngfilt.dll
0x420c0000 - 0x420f9000 C:\WINDOWS\system32\Dxtrans.dll
0x76b20000 - 0x76b31000 C:\WINDOWS\system32\ATL.DLL
0x6d430000 - 0x6d43a000 C:\WINDOWS\System32\ddrawex.dll
0x73760000 - 0x737ab000 C:\WINDOWS\System32\DDRAW.dll
0x73bc0000 - 0x73bc6000 C:\WINDOWS\System32\DCIMAN32.dll
0x42010000 - 0x42067000 C:\WINDOWS\system32\Dxtmsft.dll
0x68000000 - 0x68036000 C:\WINDOWS\system32\rsaenh.dll
0x42b90000 - 0x42c07000 C:\WINDOWS\system32\mshtmled.dll
0x767f0000 - 0x76817000 C:\WINDOWS\system32\schannel.dll
0x68100000 - 0x68126000 C:\WINDOWS\system32\dssenh.dll
0x58760000 - 0x58792000 C:\WINDOWS\system32\iepeers.dll
0x73000000 - 0x73026000 C:\WINDOWS\system32\WINSPOOL.DRV
0x6d410000 - 0x6d42c000 C:\Program Files\Java\jre6\bin\jp2iexp.dll
0x71ad0000 - 0x71ad9000 C:\WINDOWS\system32\wsock32.dll
0x6d800000 - 0x6da8b000 C:\PROGRA~1\Java\jre6\bin\client\jvm.dll
0x6d7b0000 - 0x6d7bc000 C:\PROGRA~1\Java\jre6\bin\verify.dll
0x6d330000 - 0x6d34f000 C:\PROGRA~1\Java\jre6\bin\java.dll
0x6d290000 - 0x6d298000 C:\PROGRA~1\Java\jre6\bin\hpi.dll
0x6d7f0000 - 0x6d7ff000 C:\PROGRA~1\Java\jre6\bin\zip.dll
0x02770000 - 0x02776000 C:\Program Files\Java\jre6\bin\jp2native.dll
0x6d1d0000 - 0x6d1e3000 C:\Program Files\Java\jre6\bin\deploy.dll
0x6d610000 - 0x6d623000 C:\Program Files\Java\jre6\bin\net.dll
0x6d630000 - 0x6d639000 C:\Program Files\Java\jre6\bin\nio.dll
0x6d6b0000 - 0x6d6f3000 C:\Program Files\Java\jre6\bin\regutils.dll
0x6d000000 - 0x6d14a000 C:\Program Files\Java\jre6\bin\awt.dll

VM Arguments:
jvm_args: -Xbootclasspath/a:C:\PROGRA~1\Java\jre6\lib\deploy.jar;C:\PROGRA~1\Java\jre6\lib\javaws.jar;C:\PROGRA~1\Java\jre6\lib\plugin.jar -Xmx32m -Djava.awt.headless=true -Dkernel.background.download=false -Dkernel.download.dialog=false -XX:MaxDirectMemorySize=64m
java_command:
Launcher Type: generic

Environment Variables:
PATH=C:\Program Files\Internet Explorer;;C:\orant\bin;c:\oracle\ora90\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\informix\bin;C:\Program Files\Credant\Shield v5.4.2\;"C:\Program Files\Common Files\EMC";C:\Program Files\Windows Imaging\
USERNAME=wmcdowel
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel

--------------- S Y S T E M ---------------

OS: Windows XP Build 2600 Service Pack 3

CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht

Memory: 4k page, physical 1039808k(23272k free), swap 2503148k(877736k free)

vm_info: Java HotSpot(TM) Client VM (14.2-b01) for windows-x86 JRE (1.6.0_16-b01), built on Jul 31 2009 11:26:58 by "java_re" with MS VC++ 7.1

time: Wed Nov 04 08:54:53 2009
elapsed time: 1865 seconds

Posted by Michelle DiGaetano on November 13, 2009 at 12:21 AM PST #

Hello, Michelle,

I'm glad to hear that you've migrated your EBS users over to the JRE client. I'm sorry that you're encountering problems, though. I'd like to help you get to the bottom of these issues quickly.

First, have you checked out the troubleshooting guide linked in this article?

Updated Tips for Debugging Sun JRE + Forms Focus Issues for EBS 11i and 12 - http://blogs.oracle.com/stevenChan/2009/07/tips_debugging_sun_jre_forms_focus.html

If you've gone through those troubleshooting steps and are still having problems, your next step would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on November 13, 2009 at 06:22 AM PST #

Hi Rajeev,

We are currently testing with the lastest JRE 6.17 version in an attempt to resolve the BooleanUtils.class not found issue. So far so good.

Regards,
Lindsey

Posted by Lindsey on November 18, 2009 at 04:37 PM PST #

I guess I am in the right place. I share the same pain with everyone else is experiencing. We have migrated from Jinitiator 1.3.1.18 to JRE 1.6.0_17 and experiencing forms losing focus with Oracle EBS (11.5.10.2). The issue happens sporatically and we are unable to recreate it at will. We have reapplied the following patch 8717874. We have also regen the forms with the parameter force 'Y'. I am no further along in finding a solution and I am afraid my users are getting little vulgar with their language towards me. I have opened a Service Request with Oracle Support but it is just going back and forth. Does anyone have any ideas I can sure use some help in resolving this issue.

Posted by Richard on December 07, 2009 at 12:54 PM PST #

Hi, Richard,

I'm sorry to hear that you're having trouble following your JRE migration from JInitiator. Have you checked out the latest troubleshooting guide for mouse focus issues? It's referenced here:

Troubleshooting Mouse Focus Issues Using JRE Clients with EBS 11i
http://blogs.oracle.com/stevenChan/2009/01/troubleshooting_mouse_focus_issues_using_jre_client_ebs11i.html

We've found that the vast majority of focus issues are resolved by following the steps in that Note. If you've applied all of the patches listed there and still have issues, please send me your SR number so that I can have someone in Development work with the Support engineer assigned to your SR.

Regards,
Steven

Posted by Steven Chan on December 08, 2009 at 01:59 AM PST #

Hi Steven

I'm having problems accessing, Note 761159.1 (for generic JInitiator desupport date) - is this a URL you can send me or a PDF or do I need to have access?

I just needed the note.

Cheers
StevenOoi

Posted by S.Ooi on December 10, 2009 at 02:02 PM PST #

We are using jinitiator 1.3.1.29. We are noticing, some client PCs [around 5 %], gets IE browser errors, IE crashings. Is it due to IE or firefox or windows problems?

Posted by Sandip Bose on December 11, 2009 at 03:23 AM PST #

Hi, StevenOoi,

I just checked Note 761159.1 -- it seems to be accessible via My Oracle Support (formerly Metalink). Are you having issues because you don't have an account for My Oracle Support?

If so, I'm afraid that Notes are available only to My Oracle Support subscribers. I'm not permitted to distribute those to non-subscribers.

It's a pretty short Note, though. It simply states that Error Correction Support (ECS) for generic JInitiator users on Windows will end as of 31-JAN-2010, and Extended Support (ES) will end as of 31-JAN-2013.

Regards,
Steven

Posted by Steven Chan on December 11, 2009 at 05:42 AM PST #

Hi, Sandip,

Sorry to hear that you're having trouble with the JRE migration. Have you gone through the latest JRE mouse focus troubleshooting guide linked from this article?

Updated Tips for Debugging Sun JRE + Forms Focus Issues for EBS 11i and 12
http://blogs.oracle.com/stevenChan/2009/07/tips_debugging_sun_jre_forms_focus.html

If you've gone through that and are still having problems with focus issues, your next step would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on December 11, 2009 at 05:59 AM PST #

Hi Gurus,
We have custom Oracle forms application and after upgrading to SUN JRE 1.6.0_16 we started getting Row lis locked by another user issue in forms.When we switch back to Jinitiator this problem doesn't exist(code remains same).

Thanks,
Suresh

Posted by Suresh on February 25, 2010 at 01:46 AM PST #

Hi, Suresh,

Given that you're encountering an issue with a custom Forms application, I suspect that there might be some coding standards at the root cause of this. Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get an Oracle Forms specialist engaged.

Regards,
Steven

Posted by Steven Chan on February 25, 2010 at 02:15 AM PST #

Hi Steven,

Recently, we migrated to Sun JRE 1.6.0.17, Since then often having issues with IE 6.0 crashes suddenly . Referring "mshtml.dll" in the log generated. Some times users are panic when it happens. Please suggest whether this issue is addressed in the later version of JRE.

Thanks
Srini

Posted by Srini on June 18, 2010 at 12:59 AM PDT #

Hi, Srini,

Without knowing the root causes of the crashes that you're experiencing, I can't comment on whether that will recur with later releases. I would recommend upgrading to the latest JRE on a testbed desktop to see whether you can replicate your issue there. See this recent article:

JRE 1.6.0_20 Build 5 Fixes E-Business Suite Compatibility Issues
http://blogs.oracle.com/stevenChan/2010/05/jre_16020b5_fixes_ebs_issues.html

Regards,
Steven

Posted by Steven Chan on June 18, 2010 at 02:56 AM PDT #

What are the problems will be occured while migrating application from jdk 1.4 to jdk 1.6?
What are the steps needs to follow to avoid those errors?
What info should be kept in mind while migrating jdk 1.4 to jdk 1.6?

Posted by abhishek on July 26, 2010 at 07:50 PM PDT #

Abhishek,

You've referred explicitly to the JDK -- not the JRE, although you're commenting on a JRE-related article. Remember, these are two different things. The JDK resides on your EBS application tier server, and the JRE resides on your Windows desktop clients that access your E-Business Suite environment.

Assuming that you know what you're doing here, you can find complete JDK upgrade instructions for your EBS application tier linked off this article:

Java SE 6 Certified With Release 11i
http://blogs.oracle.com/stevenChan/2007/09/java_se_6_certified_with_relea.html

If you've inadvertently confused the JRE with the JDK, you can find instructions for upgrading your JRE clients in the Note linked from the article above.

Regards,
Steven

Posted by Steven Chan on July 27, 2010 at 04:22 AM PDT #

Hi Steven,
Just wanted to get this out to you. We've migrated most of our users to the latest Sun JRE 1.6.0_20 update 5 (we waited because we also run Discoverer and wanted to use a common version for both).
One thing that we have noticed is frequent forms crashes and slowness in the forms, even though the load on the server has remained the same. We also have some thin client users accessing 11i forms over RDP and they experienced slowness as well.
The solution to the forms crashes and performance problem was to add this runtime parameter on the client side in the Java control panel applet:
-Dsun.java2d.noddraw=true
We also had done this on our older Jinitiator clients, but I didn't think we would need to do it with the newer JRE. Once we put that in it stops the intermittent forms crashes and the forms perform much better.
As always, test it out, but I just wanted to get this out there to others who may be experiencing some problems with the newer JRE.

Thanks,
Mark

Posted by Mark Coleman on September 03, 2010 at 05:04 AM PDT #

Hi, Mark,

Thanks for sharing this tip. Can you provide me with your Service Request number where this was investigated and replicated by Oracle Support? I'd like to review their analysis and see whether this has been formally reported as a bug to the Sun JRE team (or the Forms team).

Regards,
Steven

Posted by Steven Chan on September 03, 2010 at 05:21 AM PDT #

Hi Steven,
Unfortunately I didn't raise an SR for this. We've been using that parameter since JInitiator 1.3.1.18 to increase the performance of the forms interface through RDP (Remote Desktop Protocol) sessions. At that time we experienced issues with poor performance (forms slow to drag, slow data population) on thin clients connecting to a terminal server via RDP. I found the -D setting in a discussion on increasing java applet graphics performance. I thought I would give it a shot in Jinitiator and it made all the slow dragging and slow data population errors disappear.
When we began moving to the JRE 1.6 I thought we could leave that parameter behind, but right after deployment my users began complaining of forms crashes and poor forms performance, particularly in order entry when tabbing into the unit price field. Adding the -D parameter fixed the crashing and jacked up the forms performance again. This time though we weren't using RDP sessions, they were native sessions on desktop client machines, not thin clients.
I'll be glad to provide you any test data or test cases I can if necessary.
Thanks,
Mark

Posted by Mark Coleman on September 10, 2010 at 11:18 AM PDT #

Hi, Mark,

In rereading this thread, I realized that this is a workaround that you've come up with for your thin clients accessing EBS over RDP. It all comes clear now.

As you probably know, our official position is that we certify and support only Windows and Mac desktops accessing the E-Business Suite, so we don't have the infrastructure to validate this and update our official documentation accordingly.

I'm glad that you've been able to find a workaround for your thin clients. Thanks for sharing this tip with our readers. These kinds of insights are priceless for customers operating in slightly nonstandard environments, and it's great that we have a forum to share your experiences here.

Regards,
Steven

Posted by Steven Chan on September 14, 2010 at 03:35 AM PDT #

Hi Steven,
We found the parameter originally to help our thin client display performance, but we have been using it on both thin clients and Windows desktops since Jinitiator 1.3.1.18 to improve display performance and avoid forms crashing issues. When we moved to the JRE 1.6 I thought we could leave it behind, but the parameter solves several forms crash issues on the Windows desktops, so we put it back in on both.
You're correct in that originally it was for thin clients, which you guys don't officially support, but we are now using it on thin clients and Windows desktops with good results.
Just wanted to clarify, not trying to beat a dead horse! Thanks to you and all the good people at Oracle who put out this info!

Thanks,
Mark

Posted by Mark Coleman on September 15, 2010 at 11:05 AM PDT #

Hi Steven,
We are a little bit late, but now we want to change from JInitiator to JRE.
Current config: Oracle EBS 11.5.10.2 and JInitiator 1.3.1.25.

Our clients are spread all over the world and only partially controlled by us.
Currently we believe that we have not the ability to migrate all users/clients of an EBS instance at a big bang without problems. Introducing a new JRE will impact older Java applications.

Our idea is to configure our EBS to support JRE and JInit in parallel for a limited time. The intention is to support a fallback to JInitiator for clients with JRE problems to have some time to solve those issues without a fallback for all users.
We are running such a config in a test environment but Oracle does not recommend this for production.

It seems that all other customers switched all users of one EBS instance to JRE at a single blow or?
Is a step wise recommended migration strategy known by you?
Any customer experience?

Regards,
Gustav

Posted by Gustav Classen on September 16, 2010 at 11:28 PM PDT #

Hi, Gustav,

I haven't spoken to many customers about this directly. I would be very surprised if very large organizations (e.g. those with tens of thousands of EBS users) could switch over in a big bang conversion, though. I suspect that those organizations took a staged approach that allowed both JInitiator and JRE to run side-by-side.

For details about that approach, see Note 290807.1, Appendix B, "Multiple Client Java Plug-In Versions."

Good luck with your migration.

Regards,
Steven

Posted by Steven Chan on September 17, 2010 at 12:39 AM PDT #

Hi Steven,
We are planing to upgrade JDK of our EBS 11.5.10.2 configured with SSl, i would like to know if there are any precautions need to be taken before upgrading the JDK which will not impact SSL configuration.

Posted by guest on August 03, 2011 at 06:32 PM PDT #

Hi, Guest,

Upgrading your server-side JDK shouldn't affect your SSL configuration. You can refer to Note 300482.1 for pointers to EBS server-side JDK upgrade guides.

Regards,
Steven

Posted by Steven Chan on August 04, 2011 at 02:40 AM PDT #

We have migrated from oracle application server to Weblogic (10.3.2), forms (11g).

Some of the users are not able to access some part front end screen, no error message just hourglass. They have same jre like other users who are able to access application successfully.

Please advise how we can fix this issue.

Posted by vks on July 14, 2012 at 11:57 PM PDT #

Hello, VKS,

I'm sorry to hear that you've encountered an issue with this. It sounds like you're reporting an issue with a custom application and not Oracle E-Business Suite. This blog is for Oracle E-Business Suite topics, so we don't have much advice for generic issues like the one you're reporting.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our Forms specialists engaged.

Regards,
Steven

Posted by Steven Chan on July 16, 2012 at 08:08 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
25
26
27
28
29
30
   
       
Today