Article View: borland.public.jbuilder.debugger
Article #301Re: -- Cannot start Java debug process VM --
From: Woojin Oh
Date: Thu, 18 Dec 2003 03:50
Date: Thu, 18 Dec 2003 03:50
71 lines
3204 bytes
3204 bytes
Hi Hin, Thnak you for your answering. I tested "ping". For the localhost, OK, but for the <my computer name>, the ping test is failed. The ping show me a strange ip address. Maybe it cause disturbing the debug project. So, I changed <my computer name> to another one in english. I guess the base reason is that <my computer name> is set in korean(two-bytes character). Three of six test pc were using korean computer name, but one of three can debug project. I don't know why it happens. Anyway, thank you very much. "Hin Boen" <hboen@borland.com> wrote in message news:3fdfd2f8$1@newsgroups.borland.com... > > -- Cannot start Java debug process VM -- > > java.lang.NullPointerException > > Is there a java command line in the message pane? Also, could you type "ping localhost" in the cmd.exe prompt? The output from this command should be something like: pinging <computer_name> [127.0.0.1]. Now, type "ping <computer_name>". Does it run successfully? > > -Hin > > > > Woojin Oh wrote: > > >When I start to debug project, this message happens always and the JBuilder > >is stop after a few menu-clicks. > > > >-- Cannot start Java debug process VM -- > > > >java.lang.NullPointerException > > > > > >I tested it for 6 PCs, only two of them fail like this. the others are OK. > > > >For the failed PC, I uninstalled JBuilder9, deleted a user preference folder > >'.jbuilder9' and a program folder 'jbuilduer9', and restarted windows. After > >all, I reinstalled JBuilder9 but the result is same. > > > >I also checked whole JVM installed on my pc and delete all JVM except > >JBuilder9's jvm. At this time, it shows same. > > > >When I install JBuilderX trial, the sympton is same but the result message > >is slightly different from previous one. > > > >-- Cannot configure Java debug process arguments -- > > > >com.sun.jdi.connect.IllegalConnectorArgumentsException: Not listening > > > > > >Test Environment: > >CPU: Pentium 4 2.0GHz > >Memory: 512M RAM > >HDD: 36GB SCSI > >Dell Precision 340 > > > > > > > > >
Technical Details
Message-ID:
<3fe12369@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!crtntx1-snh1.gtei.net!news.gtei.net!newsfeed1.easynews.com!newsfeed2.easynews.com!easynews.com!easynews!newsfeed.news2me.com!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<3fde5801@newsgroups.borland.com> <3fdfd2f8$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5c5,4060177d38c6dad6 X-Google-Attributes: gidff5c5,public X-Google-ArrivalTime: 2003-12-17 20:10:38 PST From: "Woojin Oh" <aziya@orgio.net> Newsgroups: borland.public.jbuilder.debugger References: <3fde5801@newsgroups.borland.com> <3fdfd2f8$1@newsgroups.borland.com> Subject: Re: -- Cannot start Java debug process VM -- Date: Thu, 18 Dec 2003 12:50:35 +0900 Lines: 73 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 NNTP-Posting-Host: 165.213.1.1 Message-ID: <3fe12369@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1071719273 165.213.1.1 (17 Dec 2003 19:47:53 -0700) Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!crtntx1-snh1.gtei.net!news.gtei.net!newsfeed1.easynews.com!newsfeed2.easynews.com!easynews.com!easynews!newsfeed.news2me.com!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail