Exception from jbossall-client.jar

[Schandha Ravi]

Hi All,

I created a sample Servlet-BMP bean application, where in I'm calling create methods for inserting application. But after deploying my ear file and lauched the application, I'm getting the following error

    
18:25:35,593 INFO  [STDOUT] at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:965)
18:25:35,593 INFO  [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:614)
18:25:35,593 INFO  [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:643)
18:25:35,593 INFO  [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:508)
18:25:35,593 INFO  [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:351)
 

Even my servlet is not called as the System.out.println statement placed in init method itself not called.

when I clicked on InitialContext.java from the error message, it shows error message as

    
Decompiled from: C:\Sun\jboss-4.0.0\client\jbossall-client.jar
Total time: 0 ms
Jad reported messages/errors:
Exit status: 0
Caught exceptions:
java.io.IOException: CreateProcess: %jadnt158_directory%\jad.exe -p -t4 -dead -lnc -stat -v -8 -lradix10 -radix10 NamingContext.class error=2
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at net.sf.jadclipse.JadDecompiler.decompile(JadDecompiler.java:160)
        .........................
        .........................
 
*/

From this I believe something going wrong with jbossall-client.jar
I'm not very much experienced with jboss. Can some one tell me what would have gone wrong

[Schandha Ravi]

can someone help me out

[Jaikiran Pai]

Can you post the entire exception stacktrace that you see on the server? Where are you calling the create method from?

[Schandha Ravi]

Hi JaiKiran,

I investigated problem. Previously I didn't see the entire log as my IDE didn't show me up the previous thing. So I went to log file generated and found that something went wrong in my ejbCreate() method. I'm further looking into this.

[Schandha Ravi]

After further investigation I found that there is something which went wrong with my Datasource bindng.

Before I can go further , I would like to clarify one thing.

My mysql-ds.xml which I copied into deploy folder has the following structure

    
<?xml version="1.0" encoding="UTF-8"?>
 
<!-- $Id: mysql-ds.xml,v 1.3 2004/09/15 14:37:40 loubyansky Exp $ -->
<!--  Datasource config for MySQL using 3.0.9 available from:
<a href="http://www.mysql.com/downloads/api-jdbc-stable.html" target="_blank" rel="nofollow">http://www.mysql.com/downloads/api-jdbc-stable.html</a>
-->
 
<datasources>
  <local-tx-datasource>
    <jndi-name>MySQL</jndi-name>
    <connection-url>jdbc:mysql://localhost:3306/MySQL</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>root</user-name>
    <password>root</password>
 
      <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
      <metadata>
         <type-mapping>mySQL</type-mapping>
      </metadata>
  </local-tx-datasource>
 
</datasources>

and my ejb-jar.xml has

    
<resource-ref>
[B]<res-ref-name>jdbc/MySQL</res-ref-name>[/B]
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

and my jboss.xml has

    
<resource-ref>
        <res-ref-name>jdbc/MySQL</res-ref-name>
        <jndi-name>java:/comp/env/jdbc/MySQL</jndi-name>
</resource-ref>

From the stack over flow I can see some thing went wrong while trying to lookup for the datasource.

The error log shows

    
2008-03-16 10:52:52,890 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null
2008-03-16 10:52:52,890 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@188e490, cl=org.jboss.mx.loading.UnifiedClassLoader3@15651df{ url=null ,addedOrder=0}
2008-03-16 10:52:52,890 INFO  [STDOUT] AccountBean Created
2008-03-16 10:52:52,890 INFO  [STDOUT] com.util.ServiceLocator@1944ae
2008-03-16 10:52:52,890 INFO  [STDOUT] [B]Before Create Lookup[/B]
2008-03-16 10:52:53,156 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected Error in method: public abstract com.bank.entity.Account com.bank.entity.AccountHome.create(java.lang.String,java.lang.String,java.lang.String,double) throws java.rmi.RemoteException,javax.ejb.CreateException:
java.lang.StackOverflowError
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.naming.internal.VersionHelper12.getContextClassLoader(VersionHelper12.java:158)
at com.sun.naming.internal.ResourceManager.getFactory(ResourceManager.java:339)
at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:575)
at javax.naming.spi.NamingManager.getURLContext(NamingManager.java:533)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:279)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:965)

One more thing which I do not understand here is , why the error is coming from create() method... we haven't completed the construtor of the bean itself. After the error message "Before Create Lookup" I'm trying to lookup the datasource using

    
try{
System.out.println("Before Create Lookup");
ds=(DataSource)sl.lookUp("java:/comp/env/jdbc/MySQL");
System.out.println("DataSource :"+ ds);
}
catch(NamingException ne){
System.out.println("Naming Exception in Account Bean");
ne.printStackTrace();
}
catch(Exception e){
System.out.println("Exception in Accountbean ");
e.printStackTrace();

I'm totally confused here. Did I do anything wrong with my Datasource or in create method.....
[ March 16, 2008: Message edited by: Schandha Ravi ]

[Jaikiran Pai]

<resource-ref>
<res-ref-name>jdbc/MySQL</res-ref-name>
<jndi-name>java:/comp/env/jdbc/MySQL</jndi-name>
</resource-ref>

The jndi-name here looks wrong. The jndi-name that you specify in the resource-ref is the actual jndi-name of the resource (in this case the datasource) to which the resource is already bound. This is not the jndi-name by which the client will lookup. So change this to

<resource-ref>
        <res-ref-name>jdbc/MySQL</res-ref-name>
        <jndi-name>java:/MySQL</jndi-name>
</resource-ref>

You dont have to change the lookup code. You will continue using java:/comp/env/jdbc/MySQL jndi-name for the lookup, because this is the res-ref-name that you have specified above (Note that the res-ref-name is prefixed with java:/comp/env).

[Schandha Ravi]

Thanks JaiKiran, as you suggested I changed the <jndi-name> in jboss.xml to java:/MySQL and it is working now.

But, I have couple of things which I would like to get clarified.

1) When we use ejb-jar.xml and jboss.xml, we are try to achieve a level of indirection, so that when our ear is deployed in some other ApplicationServer, we need not change our code. So in this process, we map the name <res-ref-name> of ejb-jar.xml to <res-ref-name> of jboss.xml. Is my understanding correct ?

2) Is there any mapping beween the <jndi-name> of mysql-ds.xml and jboss.xml
in mysql-ds.xml, I mentioned <jndi-name> as MySQL and
in jboss.xml, I mentioned <jndi-name> as java:/MySQL.

How can container map between these two values.

Thanks in advance.

[Jaikiran Pai]

Originally posted by Schandha Ravi:

1) When we use ejb-jar.xml and jboss.xml, we are try to achieve a level of indirection, so that when our ear is deployed in some other ApplicationServer, we need not change our code. So in this process, we map the name <res-ref-name> of ejb-jar.xml to <res-ref-name> of jboss.xml. Is my understanding correct ?

Yes, that's correct.

Originally posted by Schandha Ravi:
2) Is there any mapping beween the <jndi-name> of mysql-ds.xml and jboss.xml
in mysql-ds.xml, I mentioned <jndi-name> as MySQL and
in jboss.xml, I mentioned <jndi-name> as java:/MySQL.

How can container map between these two values.

Actually, when you specify the jndi-name in the ds.xml file of JBoss, the server *by default* prefixes the java: namespace to the jndi-name and binds it in the java: JNDI namespace. So your datasource is actually available at java:/MySQL and you use this exact name in the jndi-name of the resource-ref element of jboss.xml

[Schandha Ravi]

Thanks Jaikiran, for clarifying my doubts .