Closed Bug 121826 Opened 23 years ago Closed 22 years ago

Problem with HTTPConnection to a servlet

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: vasile.hanzu, Assigned: joe.chou)

References

Details

I have a problem using the Http URLConnection and DataOutputStream classes in 
an applet running in the Java Plugin built into Mozilla 0.9.7

The applet is supposed to communicate with a servlet over HTTP. I send a POST 
request to the server with a query and read the response. The code is :

      URL servletURL = new URL(serv);
      con = servletURL.openConnection();
      con.setDoOutput(true);
      con.setDoInput(true);
      con.setUseCaches(false);
      con.setRequestProperty("REQUEST_METHOD", "POST");
...
      pst = new PrintStream(con.getOutputStream());
// write the query
      pst.print( querry );
      pst.flush();
      pst.close();

InputStream in = con.getInputStream();
....

The problem occurs when I write the query (a String). The follow messages 
occur:


OJIPlugin acq Spontaneous pipe=10
Trying to enter spont monitor: 0
 OJIPlugin release 
for:Thread[Thread-15,1,http://vasi.sec.co.ro:8080/voh-ui/-threadGroup]
OJIPlugin releasePipe - exiting spont monitor
Current thread:Thread[Finalizer,8,system]
OJIPlugin: No AThread

OJIPlugin acq Spontaneous pipe=10

This message appears several times and Mozilla blocks all the interface.
It should connect to servlet and a message should apper on Tomcat's console.
Reporter: Please always specify which "Build ID" you are using,
as found in the title bar of the Mozilla window.
I am having this same problem see my but 113957 it has build and examples
Blocks: 113957
Please  specify java version you're using and attach java console verbose output
(level 5) to the bug
wfm, as nobody can reproduce it. reopen if you can.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
QA Contact: pmac → petersen
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.