[Joel Rosi-Schwartz]

Hi,

I have been using the myeclipse app server facitility to run and debug my applications on JBoss 3.2.1 for some time. Today it stopped working and I can no longer launch the server in debug mode. I can, however, launch it from within Eclispe in normal run mode. I also started up an Eclipse in a clean workspace, and there I can launch JBoss in debug mode just fine. I would, however, be a real drag to have to rebuild my entire workspace to fix this.

The stack looks like this:

Thread [main] (Suspended (exception NumberFormatException))
    Integer.parseInt(String, int) line: 436
    Integer.<init>(String) line: 609
    InetAddressCachePolicy.<clinit>() line: 77
    InetAddress.<clinit>() line: 572
    AgentID.create() line: 49
    MBeanServerDelegate.<init>() line: 29
    MBeanServerImpl.<init>(String) line: 177
    NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method]
    NativeConstructorAccessorImpl.newInstance(Object[]) line: 39
    DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 27
    Constructor.newInstance(Object[]) line: 274
    MBeanServerFactory.createMBeanServer(String, boolean) line: 108
    MBeanServerFactory.createMBeanServer(String) line: 66
    ServerImpl.doStart() line: 308
    ServerImpl.start() line: 272
    Main.boot(String[]) line: 150
    Main$1.run() line: 388
    Thread.run() line: 534

Any idea as to what is causing this?

Thanks,
Joel

– System Setup ——————————-
Operating System and version: w2k professional
Eclipse version: 3.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 7
MyEclipse version: 200407091200-3.8-Beta2
Eclipse JDK version: 1.4.2 04
Application Server JDK version: 1.4.2 04
Are there any exceptions in the Eclipse log file? no
– Message Body ——————————-

[Scott Anderson]

Joel,

That’s really peculiar, and I don’t believe we’ve ever seen JBoss behave like this before. Something has obviously changed, but the real question is what could it be? Have you installed a new JDK, or version of JBoss? Updated Eclipse or changed something else in your installation? Is there any information in the log file (<workspace>/.metadata/log)?

[Joel Rosi-Schwartz]

Scott,

Yes it is very peculiar. Deeper investigation indicated that the problem was also evident in debugging Eclipse plugins, so this was not a myeclipse specific issus as I had first thought. To answer your questions, nothing whatsoever changed between everything working fine and the problem mainfiesting itself. There was not even a crash of Eclipse or other incident that I could point at and say maybe it was that. In the end I gave up my ponderings and rebuilt my workspace afresh. While this was not a joy to to do, it most certainly was the expedient course of action.

Thanks in any case for your reply and sorry to bother you folks with a non myeclipse issue.

Cheers,
Joel

[Scott Anderson]

Joel,

Glad to hear you’re up and running. I too have had workspaces “go bad” on me, but it was mainly an Eclipse 2.x problem that I have not experienced since 3.0.

[Author]

Posts