Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

WebSpeed 2.x

FIX:

As a debugging tool, it might be necessary to turn on the Java Console, or Java Logging, for the browser you are using (for example, it may show the client is running out of memory or show a java error that has been fixed by a Microsoft patch).

To enable Java logging on Internet Explorer (IE) 3.x:

1) Select View > Options > Advanced.

2) Click on "Enable Java Logging".

This puts a java log on disk so you can read it later
(for example, C:\\WINNT\java\javalog.txt


To enable Java logging on Netscape Communicator:

Select Communicator > Java Console. This starts another
window that shows Java errors as they occur.

Typical problems are:

- When you run the Section Editor, a dialog box that says:

Cannot load section list for file

comes up.

- When you run the Report or Detail Wizards, a Java exception is
generated, that looks something like the following:


java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
at java/lang/String.substring
at qb/DbInfo.load
at qb/Wizard.run
at qb/Wizard.onInit
at qb/Wizard.init
at com/ms/applet/AppletPanel.securedCall0
at com/ms/applet/AppletPanel.securedCall
at com/ms/applet/AppletPanel.processSentEvent
at com/ms/applet/AppletPanel.processSentEvent
at com/ms/applet/AppletPanel.run
at java/lang/Thread.run

Background information:

WebSpeed Workshop runs in two environments; your browser and the
Java Virtual Machine (JVM) that is spawned to run the applets.
The Java applets make web requests to WebSpeed to get
information:

- For the Report and Detail wizards.

(Information on connected databases.)

- For the Section Editor.

(Information on the sections of the programs and the
contents of the sections.)

These web requests are done by the JVM, not by the web browser.
When the applets are initiated, the Common Gateway Interface
(CGI) information is passed to the JVM, so that it should be
populated with the same information that is available to the
browser (for example, the CGI variables).

The JVM needs this to make sure that it connects to the same
WebSpeed agent that is managing your project.

Typical causes of Java Workshop problems:

- Browser Incompatibility.

Old versions of web browsers can cause problems. The Java
implementation changed between the 3.x and 4.x versions of
both Internet Explorer and Netscape, causing errors,
functionality changes, and other problems in the Java
applets in the Workshop.

Solution: If you are using an old browser (for example,
pre-Version 3.x) for either IE or Netscape, try
upgrading to a newer browser.

NOTE: Some of the newer browsers (5.X) may or may not work
with Workshop 2.1 applets.

- Authentication.

If you have authentication enabled on the web server, it can
cause a problem with the Java applets (only if you are using
the wsnsa or wsisa messengers. The cgiip messenger does not
suffer from this problem).

There was a bug in WebSpeed Versions 2.0 and 2.1 where the
REMOTE_USER variable (set with authentication) was not
propagated to the JVM of the applet which caused the
applet's requests to fail.

Solution: If you have authentication enabled on the web
server (and require it), get the latest Workshop
Version 2.1 patch for your platform. If you do not
need to use authentication, removing it resolves
this problem.

- Cannot Resolve Host.

It has been observe.d that changes in the network
configuration can cause problems with the applets. In some
cases, the browser is able to resolve the IP Address of the
Web server host but the JVM is not able to.

Solution: If your network setup has changed recently, it
could be the problem. You must check such things
as the Domain Name Server (DNS), and the hosts on
the client. You could even try using the IP
Address of the host instead of the hostname.

If you do this, the workshop applets will work, because
there is no further resolution necessary..