This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62928 - NullPointerException using JFluid JVM
Summary: NullPointerException using JFluid JVM
Status: CLOSED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: Other Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 12:22 UTC by skoky
Modified: 2007-02-20 18:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skoky 2005-08-24 12:22:45 UTC
I have started Weblogic Server 8.1 sp4 on the JFluid JVM 1.4.5 deliverred with
the Profiler M8v3-win. I have deployed session stateful EJB and an
nullPointerException occurs while profilling.
This exception does not apper while running WLS on the SUN jdk1.4.2_05
deliverred together with WLS.

The code (impacted method of the EJB):
	public String firstMethod(String name) {
		
		System.out.println("Simple version5 here. Name:" + names);

		System.out.println("Got name:" + name + ".");
		if ("".compareTo(name.trim()) == 0 || name == null) {
			names = new String();
		} else {
			if (names.length() == 0)
				names = name;
			else
				names += " and " + name;

		}

		return names;

	}

Exception apperared:

java.rmi.RemoteException: EJB Exception: ; nested exception is: 
	java.lang.NullPointerException
	at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
	at
weblogic.rmi.internal.activation.ActivatableRemoteRef.invoke(ActivatableRemoteRef.java:83)
	at
com.bea.example.spring_ejb_fascade.SimpleFascade_8syagk_EOImpl_814_WLStub.firstMethod(Unknown
Source)
	at com.bea.example.ejb_client.EJBClient.invoke(EJBClient.java:66)
	at com.bea.example.ejb_client.EJBClient.<init>(EJBClient.java:28)An exception
during ejb invoke:java.rmi.RemoteException: EJB Exception: ; nested exception is: 
	java.lang.NullPointerException

	at com.bea.example.ejb_client.EJBClient.main(EJBClient.java:56)
Caused by: java.lang.NullPointerException
	at java.lang.System.arraycopy(Native Method)
	at java.lang.String.getChars(String.java:491)
	at java.lang.StringBuffer.append(StringBuffer.java:402)
	at java.lang.StringBuffer.<init>(StringBuffer.java:131)
	at ikvc.server.SimpleFascadeImpl.firstMethod(SimpleFascadeImpl.java:30)
	at
com.bea.example.spring_ejb_fascade.SimpleFascade1EJB.firstMethod(SimpleFascade1EJB.java:47)
	at
com.bea.example.spring_ejb_fascade.SimpleFascade_8syagk_EOImpl.firstMethod(SimpleFascade_8syagk_EOImpl.java:53)
	at
com.bea.example.spring_ejb_fascade.SimpleFascade_8syagk_EOImpl_WLSkel.invoke(Unknown
Source)
	at
weblogic.rmi.internal.activation.ActivatableServerRef.invoke(ActivatableServerRef.java:99)
	at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
	at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:364)
	at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
	at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:426)
	at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Exception in thread "main" 

Very last line of the code where is exception reported:

ikvc.server.SimpleFascadeImpl.firstMethod(SimpleFascadeImpl.java:30)

is this line:

return names;


Skoky.
Comment 1 iformanek 2005-08-30 16:15:25 UTC
This is very unlikely a profiler problem. It may be related to the fact that 
the JFLuid modifiled JVM is a different update version than the 1.4 shipped 
with WL.

The NPE seems to be caused by concatenating null String somewhere. Perhaps 
names is initialized as null?

I will close this issue, if you believe this is really a profiler issue, please 
reopen.
Comment 2 ehucka 2006-10-09 12:08:34 UTC
Verification of old issues.
Comment 3 Alexander Kouznetsov 2007-02-12 22:39:41 UTC
Closing old issues.
Comment 4 Alexander Kouznetsov 2007-02-20 18:33:34 UTC
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.