[jboss-jira] [JBoss JIRA] Commented: (JBAS-3691) NoClassDefFoundError performing remote lookup of dynamic proxy using IBM JDK

[Sidney Zurch (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3691?page=comments#action_12347566 ] 
            
Sidney Zurch commented on JBAS-3691:
------------------------------------

t's going to be hard to blame the IBM JDK for this one.

I'm running basically the same JNDI code from within an EJB under JBoss 3.2.8.SP1 and from a JSP page.

	Properties properties = new Properties();
	properties.setProperty(Context.INITIAL_CONTEXT_FACTORY,
		"org.jnp.interfaces.NamingContextFactory");
	properties.setProperty(Context.URL_PKG_PREFIXES,
		"org.jnp.interfaces");	
	properties.setProperty(Context.PROVIDER_URL,
			"jnp://" + host + ":1099/");
	Context context = new InitialContext(properties);
	
The EJB context lookup croaks with the dreaded:  java.lang.NoClassDefFoundError: $Proxy xxxxx	

but the JSP lookup succeeds!

Both pieces of code use the same IBM JDK, so it's hard to fault IBM for this.

The EJB is packaged in an .ear; the JSP is packaged in a .war within the .ear.

Could this be as simple as maybe disabling the IBM JIT? 



> NoClassDefFoundError performing remote lookup of dynamic proxy using IBM JDK
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-3691
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3691
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: IBM JDK 1.5 32bit and 64bit
> IBM JDK 1.4 64bit
>            Reporter: Darran Lofthouse
>         Assigned To: Darran Lofthouse
>             Fix For: JBossAS-4.2.0.CR1
>
>
> Using the IBM JDKs listed in the environment, performing a remote lookup of a dynamic proxy from within JBoss cases a NoClassDefFoundError.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira