facebook

Servlet exception only using myeclipse?

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #202925 Reply

    harryajh
    Member

    Using eclipse 2.1.2, win 2000 (sp4), IE 5.5 (sp2), jdk 1.4, myeclipse 020700RC2, weblogic 6.1 (sp4 – I think!)

    I have a struts app (not using html tag library though!). The way actions are called are as follows using javascript –

    var oForm = top.document.fPerformance;

    oForm.action = “GotoWasteProducedAction.do”;

    oForm.submit();

    This works fine – the trouble is sometimes IE seems to issue multiple requests – when my WL 6.1 server is ran from outside eclipse (i.e via a dos window) it works fine but from within eclipse using myeclipse it throws this exception (not consistantly either!) –

    ///////////////////////////////////////////////////////////////////////////////////

    <Feb 5, 2004 12:54:16 PM GMT> <Error> <HTTP> <[WebAppServletContext(6921717,HWInt,/HWInt)] Servlet failed with IOException
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at weblogic.servlet.internal.ChunkUtils.writeChunkNoTransfer(ChunkUtils.java:237)
    at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:202)
    at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:272)
    at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:154)
    at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:126)
    at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:484)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:284)
    at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
    at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1480)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:506)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    ///////////////////////////////////////////////////////////////////////////////////

    Any ideas why this would happen? – I’ve wasted so much time on this it’s probably as usual something really stupid!

    thanks

    harry

    #202930 Reply

    Riyad Kalla
    Member

    harry can you try running the application server not in debug mode from MyEclipse and see if that helps?
    Windows>Preferences>MyEclipse>Application Servers>Web Logic 6>Launch

    set “‘Start Weblogic’ Launches in” to “Run mode”.

    #202935 Reply

    harryajh
    Member

    makes no difference!

    #202936 Reply

    Riyad Kalla
    Member

    Harry please drop to a command line and type “java -version” and paste the version in here. I know you did mention JDK 1.4, but there are quite a few service releases for 1.4.0 and I don’t know if you are being general (1.4.x) or if you literally mean 1.4.0 release.

    Scott has noted a few times in the forums that if you are using 1.4.0 it is highly suggested you upgrade your JDK. There were quite a few bugs in the 1.4.0 JDK release (even the services releases) that have given people problems when running/debugging with the application servers.

    While your problem does seem strange in that it only happens from MyEclipse, I would like to rule out all potential problems.

    Also, PLEASE check that MyEclipse is setup to use the proper JDK to run you application server. Go here: Windows>Prefs>Java>Installed JREs

    select the JRE you want to setup to be a JDK, click edit. Now change the name of this JRE to reflect that it is a JDK not a JRE, now hit the browse button next to the “JRE home directory” field, and browse to the JDK directory on your hard drive that you wish to run the application server with (preferably the same JDK that is being used to run Web Logic from the command line (if you have multiple JDKs/JREs installed)). Now hit OK/OK to commit the changes. Now open up: Windows>Prefs>MyEclipse>Application Servers>JDK, andin the drop down select the JDK you just setup. Now hit OK, and restart Eclipse.

    Try this and see if it helps.

    #202938 Reply

    harryajh
    Member

    from dos prompt –
    “java version “1.3.1”
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
    Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)”

    whereas from “installed jres” I’m using “j2sdk1.4.2_02” – could this be the problem? – have to have it set to 1.4.x to use debugging but target platform is 1.3.1 – does this mean eclipse is running 1.4.01 but weblogic is using 1.3.1? If so any ideas how to make WL use 1.4.02? – I have no JAVA_HOME set as advised sometime ago not to set it – should I? is it safe?

    thanks

    harry

    #202940 Reply

    Riyad Kalla
    Member

    harry,
    This *could* certainly be one of the problems. Under “installed jres” is the “JRE home directory” for the “j2sdk1.4.2_02” item pointing to a JDK installation? (e.g. C:\j2sdk1.4.2_02?) or is it pointing to a JRE installation? (e.g. C:\Program Files\Java\j2re1.4.2_02). Once you have verified that it is pointing to a JDK installation, do what I mentioned above and go check the JDK you selected to run weblogic here:
    Windows>Prefs>MyEclipse>Application Servers>JDK

    is that dropdown showing that you are using the “j2sdk1.4.2_02” JDK? If so, then Weblogic is correctly using the 1.4.2 JDK to run. To see what Eclipse is being run with, go to Help>About>Configuration Details, you will see some lines about the path and JRE being used to actually run Eclipse.

    It is usually a good idea to set a JAVA_HOME variable pointing to the JDK you want to use on your system and also add the path:

    
    %JAVA_HOME%\bin
    

    to your environment PATH settings and make sure no other hard coded paths to JAVA installations are in there (it sounds like you have an old one lying around whcih is why your system is finding JRE 1.3.1).

    #202947 Reply

    harryajh
    Member

    tried what you suggested & eclipse jre stuff was setup correctly. Uninstalled 1.3.1 & 1.3.1.06 & after a bit of messing around managed to get wl 6.1 running from dos prompt using jdk 1.4.1

    This exception –

    <05-Feb-2004 18:01:50 GMT> <Error> <HTTP> <[WebAppServletContext(2291032,HWInt,/
    HWInt)] Servlet failed with IOException
    java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at weblogic.servlet.internal.ChunkUtils.writeChunkNoTransfer(ChunkUtils.
    java:237)
    at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:202)

    at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:272)
    .
    .
    .

    seems to only happen when using 1.4 not in 1.3.x as reinstalled, tried it & works fine. So looks like nothing to do with myeclipse but I don’t suppose you have any ideas as to why it happens in 1.4?

    thanks very much for you help!

    harry

    #202948 Reply

    harryajh
    Member

    ps. why when returning to your website do I have to keep logging in despite clicking the “log in auto…” box everytime?

    #202962 Reply

    Riyad Kalla
    Member

    harry,
    I’m glad its working but do not know what is wrong with 1.4.1… can you try upgrading all the way to 1.4.2_03 possibly?

    as far as the website, if you want to stay logged in you have to do it from the home link, and use the login box on the far right where the checkbox is. If you use the quick login in the top left, it doesn’t keep you logged in. If you WERE doing this, then I have no idea. You might want to post to the portal forum and check with Jim.

Viewing 9 posts - 1 through 9 (of 9 total)
Reply To: Servlet exception only using myeclipse?

You must be logged in to post in the forum log in