Closed Bug 188718 Opened 22 years ago Closed 21 years ago

Error loading server-side Java applet

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ericv, Assigned: joshua.xia)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1

I administer a site run on Sun IPlanet 6.0.  While attempting to set permissions
on directories (requiring use of a server-side Java applet), the applet
apparently loads but nothing is displayed in the frame generated.  This problem
does not happen using Netscape 4.77.  Please find below the contents of the Java
Console with trace level set to 5.  I have redacted the URL for security concerns.

JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
JavaScript: calling Java system code
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: calling Java system code
JavaScript: default security policy = http:[redacted]
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: JavaScript: default security policy = http:[redacted]
setWindow: call before applet exists:39865174
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: setWindow: call before applet exists:39865174
Referencing classloader: sun.plugin.ClassLoaderInfo@1684706, refcount=1
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: Referencing classloader: sun.plugin.ClassLoaderInfo@1684706, refcount=1
Loading applet ...
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: Loading applet ...
Initializing applet ...
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: Initializing applet ...
Starting applet ...
Jan 11, 2003 2:33:45 PM sun.plugin.usability.PluginLogger log
INFO: Starting applet ...
Parser Warning: user, group, ip, dns, program expected


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
-> Oji

Which JRE do you use ?
Assignee: asa → joshua.xia
Component: Browser-General → OJI
QA Contact: asa → petersen
I downloaded and installed Java 1.4.1 from Sun.  Here's the output from "java
-version":

java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
Oh yeah, just in case you were also interested, here's the contents of my
/usr/lib/mozilla/plugins:

lrwxrwxrwx    1 root     root           52 Jan 11 13:48 libjavaplugin_oji.so ->
/usr/java/jre/plugin/i386/ns610/libjavaplugin_oji.so
-rw-r--r--    1 root     root        18628 Jun 23  2002 libnullplugin.so

Eric, could you clarify this? You refer to a server-side applet, but clearly
you're talking about something that would display in mozilla. Mozilla is
downloading a java applet and executing it on your client, correct?  Or is
mozilla accessing a URL which causes some java thing to execute on the server?

These lines from the console trace look significant:

    INFO: Starting applet ...
    Parser Warning: user, group, ip, dns, program expected

The last line is presumably the applet complaining about something. But without
access to this applet, knowing how it works, or seeing the html that loads the
applet, I think it's impossible for an outsider to assign any further meaning to
the message.

Thanks for getting back to me.  What I'm doing is administering a Sun IPlanet web server.  I'd prefer to go with Apache, but that's out of my hands at the moment...  Anyway, in the IPlanet administration pages is an area where you can specify restricted access to parts of the document tree.  There is an applet which runs that allows you to specify granular permissions for specific users (basically a GUI for administering an ACL).  In Netscape it shows up fine, but in Mozilla I just get a blank screen, with those errors in the log.Unfortunately, allowing outside access to this administration page is extremely unlikely to happen for reasons I'm sure you can appreciate.  What else can I do short of that to help this process?
I was wondering if anyone had any other ideas on how I can fix this, or other
steps I can take to help diagnose the issue...?

I am still experiencing this problem.
I just downloaded and installed 1.4b and my issue has resolved itself.  

Prior to this I was using the Debian package ("apt-get install mozilla").  The
Debian package uses 1.0.0.  Almost all other java applets I encountered worked
fine on that package.  I experienced other issues with that package (freezing on
a laptop system) and so downloaded the latest build in an attempt to resolve that.

Looks like there may be something hosed about the package available on Debian
(stable).

Thanks to all who humored me on this issue.  
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
great !

(but fixed would be only correct with an attached patch)
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
-> wfm
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.