Menu

#174 Firewall stops the startup of Dr. Java

closed
nobody
Other (88)
7
2008-01-18
2003-05-02
Anonymous
No

Dr. Java (Dr. Java stable 20030313.jar) hangs up when
trying to start up under Windows XP/home. The Dr.
Java Splash screen comes up but won't go
away....Need to end the Javaw Process to terminate.
This happens both when double clicking on the Dr.
Java .jar file, and when starting from a command line.

I've found that the problem was my McAfee Firewall,
when the firewall is off, this problem goes away. When
the firewall is on, it happens.

This does not happen with an older version of Dr. Java
(no version number, size 833kb, dated 7/30/2001)

hansb@theworld.com
Using SDK 1.4.1.02

Discussion

  • Tim Oberg

    Tim Oberg - 2003-05-21

    Logged In: YES
    user_id=691516

    This is indicative of another problem. Whenever any sort of
    rmi stuff fails, the only indication of an error is that a
    message is logged iff logging is turned on (it defaults to
    off). So the only indication of any error is when the
    program hangs. An UnexpectedExceptionError when this type
    of failure occurs may be more appropriate. And if it
    specifically happens when drjava tries to connect to address
    127.0.0.1 (as is probably happening here), a message to
    check firewall settings may be appropriate, at least as an
    interim solution.

     
  • Charles Reis

    Charles Reis - 2003-10-04

    Logged In: YES
    user_id=429731

    This issue appears to be occurring more frequently (eg.
    support request 817823), so it should really be addressed.

    For users with this problem:

    Try downloading the copy of DrJava linked below, which has
    extra debugging information enabled to help diagnose the
    problem. Please post any error messages that it reports to
    this bug report.
    http://drjava.org/downloads/drjava-debug-reset.jar

    For developers diagnosing the problem:

    I've also noticed a similar problem (or perhaps it's closer
    to the "Reset Failed!" problem, which might or might not be
    the same) on Linux if I shut down my network interface and
    try to run DrJava. This might be a fundamental problem with
    using RMI, since even very old copies of DrJava crash in
    this situation. It's worth thinking about a workaround,
    though. Here's the error I get from the debugging build
    linked above (this error is displayed from SlaveJVMRunner.java):

    An error occurred while starting the slave JVM:
    Couldn't instantiate and register the slave.
    Also failed to display error through master JVM, because:
    java.rmi.ConnectIOException: Exception creating connection
    to: 127.0.0.1; nested exception is:
    java.net.SocketException: Network is unreachable
    at
    sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:580)
    at
    sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at
    sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
    at
    edu.rice.cs.drjava.model.repl.newjvm.MainJVM_Stub.errorStartingSlave(Unknown
    Source)
    at
    edu.rice.cs.util.newjvm.SlaveJVMRunner.main(SlaveJVMRunner.java:136)
    Caused by: java.net.SocketException: Network is unreachable
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at
    java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at
    sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
    at
    sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
    at
    sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
    ... 5 more

    Original error:
    java.rmi.ConnectIOException: Exception creating connection
    to: 127.0.0.1; nested exception is:
    java.net.SocketException: Network is unreachable
    at
    sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:580)
    at
    sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
    at
    sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
    at
    edu.rice.cs.drjava.model.repl.newjvm.MainJVM_Stub.registerSlave(Unknown
    Source)
    at
    edu.rice.cs.util.newjvm.SlaveJVMRunner.main(SlaveJVMRunner.java:130)
    Caused by: java.net.SocketException: Network is unreachable
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at
    java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at
    sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
    at
    sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
    at
    sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
    ... 5 more

     
  • Charles Reis

    Charles Reis - 2003-10-04
    • milestone: 173642 --> 5: Makes DrJ unstable
    • priority: 5 --> 7
     
  • Mathias Ricken

    Mathias Ricken - 2008-01-18
    • status: open --> closed
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.