URLConnection getInputStream()

Question

Hi guys.
I am writing an applet that is getting information from a .php file. I am opening a connection to the .php and posting to it, then I am opening an input stream from the connection and reading from it.
From the input stream, I can easily open a stream reader and read the data from it, but when I try to pass the input stream to another function, the program stalls indefinitely.
Here is an example:
               //works fine
                                URLConnection conCon = conURL.openConnection();
                    conCon.setDoOutput(true);
                    conCon.setUseCaches(false);
                    OutputStreamWriter conOut = new OutputStreamWriter(conCon.getOutputStream());
                    conOut.write(conPost);
                    conOut.flush();
                    conOut.close();
                    InputStream conIS = conCon.getInputStream();
                    BufferedReader buff = new BufferedReader(new InputStreamReader(conIS));
                    System.out.println(buff.readLine());
                //but if instead I do
                    InputStream conIS = conCon.getInputStream();
                    conSeq = FastaParser.getSequence(conIS);
//elsewhere
     public static String getSequence(InputStream is) throws IOException{
          String seq = "";
          InputStreamReader ir = new InputStreamReader(is);
          BufferedReader br = new BufferedReader(ir);
          String line = br.readLine();
                return line;
//it times outThis is just an example. I am doing other things with the input stream. Is there any way to stop it from stalling here?
Edited by: shiroganeookami on Oct 19, 2007 9:21 AM

Answer 1

shiroganeookami wrote:
well, here's the actual code:
...I don't see anything in that which would behave badly, other than possibly not checking your initially read string for null or checking string lengths before trying to use charAt(0) on it. I do see that you're conditionally building a "seq" string and then tossing it, returning only the last line (or null) you read, so that doesn't look right. But it doesn't look like it could possibly be the problem leading to this topic.
Looks like you better do some (more) debugging, by running in a debugger if possible, or at a minimum logging clues along the way, such as putting a
System.out.println("Here's the line I just read from the stream:" + line + ":");
in the do-while loop to see if it's getting in there and what you're reading from the stream.
And log other clues as well, such as at the end of the method to let yourself know whether the method returned or not, and before and after each br.readLine to let yourself know whether the readLine is hanging.