HELP! Upgrade JBoss3->3.04 EvThing is broken. W/ JasperExcep

[saint_wrath]

Hi,
I just tried upgrade Jboss 3 -> 3.04 w/ Tomcat. Everything was working under 3 w/tomcat4.0X. Now I can't even call the EJB from the JSP page, and get JasperException Instead.

1. I checked EJB ejb-jar.xml & jboss.xml. They are okay.
2. Deployed without a problem
3. Use everything default for both jboss and tomcat(only thing changed is for tomcat, changed port 8080 to 80)
4. goto jboss JNDIview and the EJB came up as expected. (=>java:comp namespace of the ejb/warehouse/DBquery bean)
5. Create a blank JSP page w/ the following call:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL, "localhost:1099");
Context ctx = new InitialContext(props);
DBqueryHome home = (DBqueryHome)ctx.lookup("ejb/warehouse/DBquery");

6. I scrap the whole server, reinstall 3.0 w/ tomcat 4.0 everything works fine.

7. I recheck all the xml for my bean, match it against the others like jmx-ejb-adaptor.jar from the default deploy. Everything is in order

WHAT AM I DOING WRONG? Been at this problem for about two days, cannot solve this. Is JBoss not ready for anything other than Home-grown server? I'm at a lost as to the changes these developer makes every 0.01 release.

Please any help would be really appreciated..

BT

[saint_wrath]

Oh and the xml files are as follow:
ejb-jar.xml:
====================================================
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
<ejb-jar>
<display-name>ejb/warehouse/DBquery</display-name>
<enterprise-beans>


<ejb-name>ejb/warehouse/DBquery</ejb-name>
com.warehouse.ejb.DBqueryHome
com.warehouse.ejb.DBquery
<ejb-class>com.warehouse.ejb.DBqueryEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>

<env-entry>
<env-entry-name>Server-Name</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>null</env-entry-value>
</env-entry>


</enterprise-beans>
</ejb-jar>
======================================================


jboss.xml:
======================================================
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS//EN"
"http://www.jboss.org/j2ee/dtd/jboss.dtd">

<enterprise-beans>

<ejb-name>ejb/warehouse/DBquery</ejb-name>
<jndi-name>ejb/warehouse/DBquery</jndi-name>
<local-jndi-name>ejb/warehouse/DBqueryLocal</local-jndi-name>

</enterprise-beans>
<resource-managers>
</resource-managers>

======================================================

[jakawan]

I have the exactly the same problem.
Anybody know the solution to this??

Thank

[adrian.brock]

It is probably related to this bug

https://sourceforge.net/tracker/index.php?func=detail&aid=637730&group_id=22866&atid=376685

But then why send the request over RMI anyway?
What is wrong with
new InitialContext()

Regards,
Adrian

[saint_wrath]

Because if I need to seperate the app server and web server, the code would be there.

I'm giving up on the 3.04 and I just want to keep working on the code, instead of tryin every silly things to get the damn app server upgrade to 3.04 from 3.0. For a 0.04 releaes, this's got to be joking to have WHOLE BUNCH (I can see on the forum) of backward-incompatability, and call themselve the best app-server there is. AND with no documentation (the paid one SUCKS BIG TIME, DUN BUY IT UNTIL THEY COME UP SOMETHING USEFUL), this is not for production useage.