[Bluej-discuss] Error message in BlueJ launch

[Davin McCall]

Hi Todd,

It's hard to say for sure, but I suspect that some firewall software is 
to blame for the "transport error" problem. Norton Internet Security or 
ZoneAlarm are the usual candidates for this sort of problem, but it may 
well be any other firewall software. Setting the "bluej.vm.transport" 
parameter to "dt_shmem" in the bluej.defs file will probably help; just 
remove the '#' from the beginning of the existing line (which reads: 
#bluej.vm.transport=dt_shmem).

As for the duplicate CheckStyle extension, is it possible that he/she 
has two different versions installed at the same time?

Davin.


Todd Whittaker wrote:
> Hello all,
>
> I have a student who is puzzled by an error message every time he launches BlueJ.  He says that this affects other things (but exactly what is unclear).  
>
> The error is "ERROR: transport error 202: recv error: Software caused connection abort ["transport.c", L41]".  This is under JDK 1.5.0_07b3.
>
> Below is the bluej-debuglog.txt file and here is a link to a screenshot of the message:
>
> http://einstein.franklin.edu/~whittakt/BlueJerror.png (36 Kb)
>
> He says that as soon as he launches BlueJ he can open the terminal window and see the above error message.  Any hints as to what may be the issue?  I don't get the error message about the duplicate CheckstyleExtension in my own installation...
>
> <------------ cut here: bluej-debuglog.txt *----------------->
> BlueJ run started: Tue Jan 09 13:51:44 EST 2007
> BlueJ version 2.1.3    Java version 1.5.0_07
> Virtual machine: Java HotSpot(TM) Client VM 1.5.0_07-b03 (Sun Microsystems Inc.)
> Running on: Windows XP 5.1 (x86)
> Java Home: c:\program files\java\jdk1.5.0_07\jre
> ----
> Extension is already loaded: com.puppycrawl.tools.checkstyle.plugins.bluej.CheckstyleExtension jarName=C:\Program Files\BlueJ\lib\extensions\checkstyle-extension-4.2.jar
> Connected to debug VM via dt_socket transport...
> Connected to debug VM via dt_shmem transport...
> Connected to debug VM via dt_shmem transport...
> Communication with debug VM fully established.
> <------------ cut here: bluej-debuglog.txt *----------------->
>
> Thanks,
>
>