[Robert Beltran]

I’m running jboss 3.5.5 and here’s my eclipse info:
Version: 3.0.0
Build id: 200310101454

My jboss setup in eclipse is pointing to the 1.4.1_05 jdk that I got from sun and actually it’s been working terrificly for weeks this problem just popped up yesterday.

I get an NPE in java.io.Reader. It dies in the same place everytime. JBOSS runs fine from the command line using run.bat -c <server>. Also runs well in run mode. But I’ve been running it in debug mode for weeks. Any help would be appreciated.

Here’s the jboss output:

13:26:40,112 INFO [Server] Starting JBoss (MX MicroKernel)…
13:26:40,112 INFO [Server] Release ID: JBoss [WonderLand] 3.2.2 (build: CVSTag=JBoss_3_2_2 date=200310182216)
13:26:40,122 INFO [Server] Home Dir: C:\jboss-3.2.2
13:26:40,122 INFO [Server] Home URL: file:/C:/jboss-3.2.2/
13:26:40,122 INFO [Server] Library URL: file:/C:/jboss-3.2.2/lib/
13:26:40,122 INFO [Server] Patch URL: null
13:26:40,122 INFO [Server] Server Name: worldline
13:26:40,122 INFO [Server] Server Home Dir: C:\jboss-3.2.2\server\worldline
13:26:40,122 INFO [Server] Server Home URL: file:/C:/jboss-3.2.2/server/worldline/
13:26:40,122 INFO [Server] Server Data Dir: C:\jboss-3.2.2\server\worldline\data
13:26:40,132 INFO [Server] Server Temp Dir: C:\jboss-3.2.2\server\worldline\tmp
13:26:40,132 INFO [Server] Server Config URL: file:/C:/jboss-3.2.2/server/worldline/conf/
13:26:40,132 INFO [Server] Server Library URL: file:/C:/jboss-3.2.2/server/worldline/lib/
13:26:40,132 INFO [Server] Root Deployemnt Filename: jboss-service.xml
13:26:40,142 INFO [Server] Starting General Purpose Architecture (GPA)…
13:26:40,352 INFO [ServerInfo] Java version: 1.4.1_05,Sun Microsystems Inc.
13:26:40,352 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_05-b01,Sun Microsystems Inc.
13:26:40,352 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
13:26:40,392 INFO [ServiceController] Controller MBean online
13:26:40,772 INFO [MainDeployer] Started jboss.system:service=MainDeployer
13:26:40,853 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@15db314
13:26:40,853 INFO [JARDeployer] Started jboss.system:service=JARDeployer
13:26:40,883 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@de1b8a
13:26:40,893 INFO [SARDeployer] Started jboss.system:service=ServiceDeployer
13:26:40,893 INFO [Server] Core system initialized
13:26:40,903 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.2/server/worldline/conf/jboss-service.xml

Here’s the stack trace:

org.jboss.Main at localhost:1423
System Thread [Finalizer] (Running)
System Thread [Reference Handler] (Running)
System Thread [Signal Dispatcher] (Running)
Thread [DestroyJavaVM] (Running)
Thread [main] (Suspended (exception NullPointerException))
InputStreamReader(Reader).<init>(Object) line: 61 [local variables unavailable]
InputStreamReader.<init>(InputStream, String) line: 80
PropertyMap(Properties).load(InputStream) line: 189
Main.<init>(String) line: 108
NamingService.<init>() line: 52
NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method]
NativeConstructorAccessorImpl.newInstance(Object[]) line: 39
DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 27
Constructor.newInstance(Object[]) line: 274
MBeanServerImpl.instantiate(String, ClassLoader, Object[], String[]) line: 847
MBeanServerImpl.instantiate(String, ObjectName, Object[], String[]) line: 291
MBeanServerImpl.createMBean(String, ObjectName, ObjectName, Object[], String[]) line: 318
ServiceCreator.install(ObjectName, ObjectName, Element) line: 98
ServiceConfigurator.internalInstall(Element, List, ObjectName) line: 155
ServiceConfigurator.install(Element, ObjectName) line: 118
ServiceController.install(Element, ObjectName) line: 225
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object[]) line: 324
ReflectedMBeanDispatcher.invoke(String, Object[], String[]) line: 284
MBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 546
MBeanProxyExt.invoke(Object, Method, Object[]) line: 177
$Proxy4.install(Element, ObjectName) line: not available
SARDeployer.create(DeploymentInfo) line: 183
MainDeployer.create(DeploymentInfo) line: 786
MainDeployer.deploy(DeploymentInfo) line: 641
MainDeployer.deploy(URL) line: 605
MainDeployer.deploy(String) line: 589
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object[]) line: 324
ReflectedMBeanDispatcher.invoke(String, Object[], String[]) line: 284
MBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 546
MBeanProxyExt.invoke(Object, Method, Object[]) line: 177
$Proxy5.deploy(String) line: not available
ServerImpl.doStart() line: 384
ServerImpl.start() line: 291
Main.boot(String[]) line: 150
Main$1.run() line: 395
Thread.run() line: 536
Thread [Thread-1] (Running)

[Scott Anderson]

I’m really sorry that I just found this post. Sometimes I miss a few due to the volume and this one fell between the cracks. If this is still a problem please let us know. If you’ve resolved it, could you post a followup to let everyone else know how you did it?\

–Scott
MyEclipse Support

[Robert Beltran]

Yes, I cannot run jboss in debug mode. It would be helpful to fix this problem for me.

[Scott Anderson]

My jboss setup in eclipse is pointing to the 1.4.1_05 jdk that I got from sun and actually it’s been working terrificly for weeks this problem just popped up yesterday.

This typically means that something changed in your JDK implementation. Did you install or uninstall any software? Have you tried reinstalling the JDK or running with a different one? Personally, that’s where I’d start, since the issue seems to be in a native method used by the Reader class.

Also, if you could post the information we request in the Posting Guidelines thread in this forum it will give us more information to help run this down. But, I’d still start with a JDK reinstall, given the symptoms.

–Scott
MyEclipse Support

[Robert Beltran]

Thanks for the tips but I didn’t reinstall the jdk or modify it at all. One thing I may have done was extract the src.jar I always do that in case I need to read the java source. Also you didn’t give me an actual remedy if the case was the I reinstalled the jdk. Would I have to reinstall myeclipse. I’m gonna search around for that data you requested in the guidelines. Maybe you guys should make a form asking for this stuff. That would have saved us some time.

BTW, I know this level of support is not normally available even in commercial software apps and I definitely appreciate this.

-Robert

[Robert Beltran]

OS windows xp pro

Version: 3.0.0
Build id: 200310101454

Yes it was freshly installed for my eclipse

no external plugins

pde.build_3.0.0
pde.core
pde.doc.user
pde.junit.runtime
pde.runtime
pde.source
pde.ui
pde_

all 3.0.0

my eclipse version 3.6.3

C:\j2sdk1.4.1_05

I couldn’t tell you what steps I took to result in this issue.

No reporting to the C:\Program Files\eclipse\workspace\.metadata\.log file when this error occurs.

[Riyad Kalla]

Was that a milestone build of Eclipse or just a integration build you happened to pull down?

[Robert Beltran]

I’m pretty sure our whole company is using M4.

[support-michael]

Try undeploying all applications and then verify that JBoss will start up. Looking at the stack we are curious as to the “Main” stack frame and what it might indicate.

Michael
MyEclipse

[Robert Beltran]

undeployed all, started up jboss in debug mode. Nothing new, same problem.

[Scott Anderson]

Also you didn’t give me an actual remedy if the case was the I reinstalled the jdk. Would I have to reinstall myeclipse.

Sorry about that. What I’m trying to do is eliminate a “bad JDK installation” from consideration as a cause for the problem. To do this, we need to try launching JBoss with a differnt JDK to see if the behavior changes. You can either do this by reconfiguring the JDK setting for JBoss within the MyEclipse preferences, or by reinstalling the same JDK again. Truthfully, I’d prefer the former. And no, you won’t need to install MyEclipse again.

–Scott
MyEclipse Support

[Robert Beltran]

I thought that might work as well so I installed the newest jdk 1.4.2_03 same problem. How else could I reconfigure the jdk?

[Scott Anderson]

And I’ll assume after installation you configured the JBoss connector to use that JDK to launch the server. One other test: can you shutdown Eclipse and modify your alias to it so that Eclipse launches using the new JDK also? The Eclipse option is like: -vm <path-to-javaw.exe>

If that doesn’t work, I’d try to install a new Eclipse/MyEclipse combination in parallel to my existing one to see if that new install launches JBoss properly. This will eliminate a bad installation of Eclipse/MyEclipse as a possibility, as we continue to whittle down the possibilities.

–Scott
MyEclipse Support

[Riyad Kalla]

Question: Rbeltran:

In your original post you mention that JBoss runs fine from CONSOLE and also in RUN mode, but it does not run in DEBUG mode. Is this still correct? In which case I’d start debugging the MyEclipse installation assuming it does any magic or adds any hooks when running an app server in debug mode.

[Robert Beltran]

This is true, I can still launch jboss in run mode and also from the command line just fine. I do not however know all the syntax to get jboss to run in debug mode from the command line so I haven’t tried it. I have done it before but I’ve been to lazy to try it. I’ll have to try that today. I’ll also try reinstalling eclipse and myeclipse.

Thanks.

[Author]

Posts