SUN JRE 1.3.1 Can not Find Properties File, 1.3.0 Can.

Aug 1, 2001

PROBLEM:

Upon manual installation of the Sun 1.3.1 JAVA Plug In on

a client, our applet will load but can no longer "find" the

properties file and throws a MissingResourceException. Other

class files from our single jar are found OK. No other changes

were made on this machine - only the JRE 1.3.1 install.

This was done by uninstalling the old 1.3.0 JRE, rebooting

the client, then manually (not via the auto HTML download)

installing the new 1.3.1 JRE. At this point our web page

launching our applet was accessed and the failure occurred.

We are assuming that old HTML files expecting version 1.3

plugins "should" function fine on previously installed

1.3.1 JRE plugins on client machines.

(BTW-converting our HTML to 1.3.1 made things even worse)

The unacceptable way to get 1.3.1 to function is to enter

IE->Internet OPtions->Connections->Lan Settings->Proxy server

and then UNCHECK the "Use a proxy server" checkbox.

The resource file will then be found on the next try.

QUESTIONS:

1. What are the differences between JRE 1.3.0 and 1.3.1

with regard to ResourceBundles?

2. What needs to be reconfigured on the client side to accomodate 1.3.1?

3. Does the "trustProxy" issue have something to do with the probelm?

ENVIRONMENT:

OS: WinNT4.0 SP6

Browser:IE 5.5 SP1 version 5.50.4522.1800

JRE:Sun 1.3.0 and 1.3.1

Compiler:IBMJDK 1.3

SOURCE CODE:

The line of code that throws the exception on 1.3.1 (only)

java.util.PropertyResourceBundle rb = (java.util.PropertyResourceBundle)java.util.PropertyResourceBundle.getBundle("properties.ClientProperties");

CONSOLE DUMPS:

Console start info:

Java(TM) Plug-in: Version 1.3.1

Using JRE version 1.3.1 Java HotSpot(TM) Client VM

User home directory = C:\WINNT\Profiles\admin

Proxy Configuration: Manual Configuration

Proxy: socks=socks.myCity.myCompany.com:1080

Proxy Overrides: ,localhost,49213,127.0.0.1,203.3.7.222,<local>

Console dump after startup:

Opening http://myserver/webapp/TestApp/properties/TestAppProperties.class

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties.class with no proxy

Opening http://myserver/webapp/TestApp/properties/TestAppProperties.properties

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties.properties with no proxy

Opening http://myserver/webapp/TestApp/properties/TestAppProperties_en.class

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties_en.class with no proxy

Opening http://myserver/webapp/TestApp/properties/TestAppProperties_en.properties

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties_en.properties with no proxy

Opening http://myserver/webapp/TestApp/properties/TestAppProperties_en_US.class

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties_en_US.class with no proxy

Opening http://myserver/webapp/TestApp/properties/TestAppProperties_en_US.properties

Connecting http://myserver/webapp/TestApp/properties/TestAppProperties_en_US.properties with no proxy

java.util.MissingResourceException:Can't find bundle for base name properties.TestAppProperties, locale en_US

[3449 byte] By [humesr] at [2007-9-26 2:37:44]
# 1

Do you know how to check the clients machine to see what version (Java Plugin/JRE) they currently have? And if so...I need to do this and tell them that if they have plugin 1.3.0 they need to download 1.3.1 or the applet will not work properly.

Any tips or ideas would help out a lot!

Terry

tapodaca at 2007-6-29 10:07:31 > top of Java-index,Desktop,Runtime Environment...
# 2
SUN JRE 1.3.0 works perfect.SUN JRE 1.3.1 is the problem. And as we continue to use 1.3.1 does many other unpleasant things like shutting down the browser randomly and all flavors of socket errors.
humesr at 2007-6-29 10:07:31 > top of Java-index,Desktop,Runtime Environment...
# 3

The final workaround is to setup each client machine

so that the java plugin will not use the browsers

proxy for applets.

This is unacceptable too.

SUN changed something in 1.3.1 that altered proxy use behavior. I suspect we will have problems when we go live and try to get thru the firewall. Hopefully the next release of the JRE will not be as buggy and the problem will go away into the cornfield.

humesr at 2007-6-29 10:07:31 > top of Java-index,Desktop,Runtime Environment...
# 4
Any solution about the JRE 1.3.1 and plugin? I have run into the browser shutdown too, also some other problems. If you have any tips, let me know.
tapodaca at 2007-6-29 10:07:31 > top of Java-index,Desktop,Runtime Environment...