Deployment time NameNotFoundException

[Mark Herschberg]

I'm trying to deploy my EJBs to WebLogic 7.0, using JBuilder 8.0 (Enterprise). For some reason,
I'm getting a NameNotFoundException during deployment. I'd expect to see these at
runtime, but at deployment time, it suggests I have some configuration setting wrong--but I can't
find any. A co-worker has been able to successfuly deploy to and run his EJBs on the server.
Any ideas?

Log file:

D:\JBuilder8\jdk1.4\bin\javaw  -classpath D:\bea\weblogic700\server\lib\weblogic_sp.jar;D:\bea\weblogic700\server\lib\weblogic.jar;D:\bea\weblogic700\server\lib\webservices.jar; weblogic.Deployer  -user admin  -adminurl <a href="http://192.168.2.110:7001" target="_blank" rel="nofollow">http://192.168.2.110:7001</a>  -password XXXXXX  -activate  -name trading -upload  -source "C:/Documents and Settings/Administrator/Desktop/HBS/JBuilderFiles/SimTrade/trading.jar" -targets myserver
Operation started, waiting for notifications...
.
#TaskIDActionStatusTargetTypeApplicationSource
10ActivateFailedmyserverServertradingC:\bea\user_projects\SimTradeDomain\myserver\upload\trading\trading.jar
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 10
Module: tradingError: Exception while rollback of module : EJBModule(trading,status=NEW)
trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'

Exception:

weblogic.management.ApplicationException: Prepare failed. Task Id = 5
Start server side stack trace:
weblogic.management.ApplicationException: Prepare failed. Task Id = 5
{
Module Name: trading, Error: Exception while rollback of module : EJBModule(trading,status=NEW)
trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
 TargetException: weblogic.ejb20.UnDeploymentException: trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
}
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:697)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:576)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1064)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End  server side stack trace
{
Module Name: trading, Error: Exception while rollback of module : EJBModule(trading,status=NEW)
trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
 TargetException: weblogic.ejb20.UnDeploymentException: trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
Start server side stack trace:
weblogic.ejb20.UnDeploymentException: trading.jar; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:223)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:187)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
at weblogic.ejb20.deployer.EJBDeployer.cleanupAppContext(EJBDeployer.java:1759)
at weblogic.ejb20.deployer.EJBDeployer.rollback(EJBDeployer.java:1442)
at weblogic.ejb20.deployer.EJBModule.doRollback(EJBModule.java:587)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:257)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1504)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:690)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:576)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1064)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End  server side stack trace
; nested exception is: 
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/trading.jar#OrderCrosser' Resolved: 'app/ejb' Unresolved:'trading.jar#OrderCrosser' ; remaining name 'trading.jar#OrderCrosser'
}
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:697)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:576)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1064)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

I do have an EJB named OrderCrosser in trading.jar (along with a few other beans, session, entity, and message-driver), however I never named it, placed it, or otherwise referenced it by app/ejb/trading.jar#OrderCrosser I'm guessing that's something WebLogic did and some setting is misconfigured.
--Mark

(Hmm, looks like the password is included in the error log, I better fix that :-)
[ December 17, 2002: Message edited by: Mark Herschberg ]

[Chris Mathews]

Actually my first guess would be JBuilder 8 did something funny with the descriptors. It would be helpful to see the actual ejb-jar.xml and weblogic-ejb-jar.xml that gets generated by JBuilder.
Personally, I don't think you should use JBuilder to deploy your ejbs (and other J2EE components). It makes it very hard to create builds that are exactly reproduceable among all team members. You should look into using ANT to build your components to be deployed. This way all the team members can use the same build process and errors will be easily traceable. You can even use your ANT scripts to kick off Unit Tests. This can also lead itself easily to automation and allow you to take advantage of XP practices such as continous integration. I find continous integration extremely useful at identifying errors early.
As it is, you could merely have a difference in your JBuilder settings compared to your co-worker. This could be what is causing all of your problems.
Your problem could also result from the order of your deployments. Are you deploying separate ejb jars or just a single jar?
Last question, have you tried running ejbc on your jar outside of JBuilder? Does is pass compile correctly?

[Mark Herschberg]

First, thanks for replying, Chris.

Originally posted by Chris Mathews:
Actually my first guess would be JBuilder 8 did something funny with the descriptors. It would be helpful to see the actual ejb-jar.xml and weblogic-ejb-jar.xml that gets generated by JBuilder.

I was debating including them, I'll list them below.

Originally posted by Chris Mathews:
Personally, I don't think you should use JBuilder to deploy your ejbs (and other J2EE components). It makes it very hard to create builds that are exactly reproduceable among all team members. You should look into using ANT to build your components to be deployed. This way all the team members can use the same build process and errors will be easily traceable. You can even use your ANT scripts to kick off Unit Tests. This can also lead itself easily to automation and allow you to take advantage of XP practices such as continous integration. I find continous integration extremely useful at identifying errors early.

I would generally agree with you. However, We have only a 2 person development team, so coordinating settings shouldn't be too difficult. JBuilder has some nice features, like one-click deploy (and one-click unit testing, too), that make it very attractive, especially for small projects. We will probably ultimately switch to Ant at the end of development, so future iterations aren't tied to JBuilder, of course, event hen JBuilder can create the Ant files for us (I'll be sure to check them to make sure they are not JBuilder dependent).

Originally posted by Chris Mathews:
As it is, you could merely have a difference in your JBuilder settings compared to your co-worker. This could be what is causing all of your problems.
Your problem could also result from the order of your deployments. Are you deploying separate ejb jars or just a single jar?
Last question, have you tried running ejbc on your jar outside of JBuilder? Does is pass compile correctly?

Yes, it could be setting--although we haven't found anything yet.
Order of deployments? I'm deploying a single jar. Do you think I should put each bean into its own jar?
No, I haven't tried compiling seperately, but that's a good idea.
What we did find was some JBuilder idosynchrocies. In one case I accidentally had the bean set to "remote interface" as opposed to "local interface." I changed it using the EJB designer, but I didn't seem to update the descriptor files consistently with the other EJBs. We ultimately checked each JNDI name and interface name by hand to make sure we were calling the names to which they were set.

Here are the descriptor files:
ejb-jar.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
    <enterprise-beans>
        <session>
            <display-name>OrderChecker</display-name>
            <ejb-name>OrderChecker</ejb-name>
            <local-home>com.hbs.simtrade.server.trading.OrderCheckerLocalHome</local-home>
            <local>com.hbs.simtrade.server.trading.OrderCheckerLocal</local>
            <ejb-class>com.hbs.simtrade.server.trading.OrderCheckerBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
        <session>
            <display-name>SetupBean</display-name>
            <ejb-name>SetupBean</ejb-name>
            <local-home>com.hbs.simtrade.server.trading.SetupLocalHome</local-home>
            <local>com.hbs.simtrade.server.trading.SetupLocal</local>
            <ejb-class>com.hbs.simtrade.server.trading.SetupBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
        <session>
            <display-name>OrderUpdateSender</display-name>
            <ejb-name>OrderUpdateSender</ejb-name>
            <local-home>com.hbs.simtrade.server.trading.OrderUpdateSenderLocalHome</local-home>
            <local>com.hbs.simtrade.server.trading.OrderUpdateSenderLocal</local>
            <ejb-class>com.hbs.simtrade.server.trading.OrderUpdateSenderBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
        <session>
            <display-name>OrderCrosser</display-name>
            <ejb-name>OrderCrosser</ejb-name>
            <local-home>com.hbs.simtrade.server.trading.OrderCrosserLocalHome</local-home>
            <local>com.hbs.simtrade.server.trading.OrderCrosserLocal</local>
            <ejb-class>com.hbs.simtrade.server.trading.OrderCrosserBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
        <entity>
            <display-name>OrderUpdateQueueLookupTableBean</display-name>
            <ejb-name>OrderUpdateQueueLookupTableBean</ejb-name>
            <local-home>com.hbs.simtrade.server.trading.OrderUpdateQueueLookupTableHome</local-home>
            <local>com.hbs.simtrade.server.trading.OrderUpdateQueueLookupTable</local>
            <ejb-class>com.hbs.simtrade.server.trading.OrderUpdateQueueLookupTableBean</ejb-class>
            <persistence-type>Bean</persistence-type>
            <prim-key-class>java.lang.String</prim-key-class>
            <reentrant>False</reentrant>
        </entity>
        <message-driven>
            <display-name>OrderReceiver</display-name>
            <ejb-name>OrderReceiver</ejb-name>
            <ejb-class>com.hbs.simtrade.server.trading.OrderReceiverBean</ejb-class>
            <transaction-type>Container</transaction-type>
            <message-driven-destination>
                <destination-type>javax.jms.Queue</destination-type>
            </message-driven-destination>
        </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
        <container-transaction>
            <method>
                <ejb-name>OrderReceiver</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <container-transaction>
            <method>
                <ejb-name>OrderChecker</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <container-transaction>
            <method>
                <ejb-name>SetupBean</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <container-transaction>
            <method>
                <ejb-name>OrderUpdateQueueLookupTableBean</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <container-transaction>
            <method>
                <ejb-name>OrderUpdateSender</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <container-transaction>
            <method>
                <ejb-name>OrderCrosser</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
    </assembly-descriptor>
</ejb-jar>

weblogic-ejb-jar.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
    <weblogic-enterprise-bean>
        <ejb-name>OrderChecker</ejb-name>
        <local-jndi-name>OrderCheckerLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
        <ejb-name>SetupBean</ejb-name>
        <local-jndi-name>SetupBeanLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
        <ejb-name>OrderUpdateSender</ejb-name>
        <local-jndi-name>OrderUpdateSenderLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
        <ejb-name>OrderCrosser</ejb-name>
        <local-jndi-name>OrderCrosserLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
        <ejb-name>OrderUpdateQueueLookupTableBean</ejb-name>
        <local-jndi-name>OrderUpdateQueueLookupTableBean</local-jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
        <ejb-name>OrderReceiver</ejb-name>
        <message-driven-descriptor>
            <pool>
                <max-beans-in-free-pool>1</max-beans-in-free-pool>
                <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
            </pool>
        </message-driven-descriptor>
    </weblogic-enterprise-bean>
</weblogic-ejb-jar>

--Mark

[Chris Mathews]

Mark Herschberg
I'm deploying a single jar. Do you think I should put each bean into its own jar?

Keep them all in one jar. They will be easier to maintain and an ejb-jar with N ejbs deploys faster than N ejb-jars.

Mark Herschberg
What we did find was some JBuilder idosynchrocies.

This is another reason I prefer using a build tool like Ant.

Mark Herschberg
JBuilder can create the Ant files for us

Are you sure? I know JBuilder supports Ant (only the $3000 version mind you) but I wasn't aware it supported generating Ant scripts for projects.
Onward to your problem...
Your deployment descriptors look fine to me, except that you do not specify the WebLogic JMS Queue for your MDB in your weblogic-ejb-jar.xml.
Looking in Google Groups it appears others have had this same problem, most during runtime though. There is at least one post of someone having this problem during deployment and he was using JBuilder to deploy. JBuilder has had deployment bugs with WebLogic in the past, so that could be an issue.
Have you done a diff between your DDs and your co-workers? If they are the same then the only other thing I can suggest is to delete all of WebLogic's working directories (.wlstaging, .wlnotdelete, etc.) and try to manually deploy the ejb-jar. Drop the jar into your Application directory and deploy thru the Admin console. If that does not work, then try to deploy your co-worker's ejb-jar (which works right?) on your WebLogic Server. At this point you should be able to tell if it is your build or your server that is causing the problems.

[Mark Herschberg]

Well, we're still not 100% certain of the cause, but it seems to be fixed. All I did was start over, and recreate the first bean. but the settings are all as before. My best guess is some bits didn't get switched when I switched some settings in the bean designer. Lesson learned: deploy one bean at a time. Thanks for your help, Chris.
--Mark

[Chris Mathews]

Originally posted by Mark Herschberg:
Well, we're still not 100% certain of the cause, but it seems to be fixed. All I did was start over, and recreate the first bean. but the settings are all as before. My best guess is some bits didn't get switched when I switched some settings in the bean designer. Lesson learned: deploy one bean at a time. Thanks for your help, Chris.
--Mark

That is why I dislike using tools like JBuilder that hide settings for the sake of simplicity. Things are great and wonderful... until they break.

[Chris Mathews]

Originally posted by Chris Mathews:

That is why I dislike using tools like JBuilder that hide settings for the sake of simplicity. Things are great and wonderful... until they break.

I just want to qualify my statements. I am referring to JBuilder's wizards, not JBuilder as an editor. I have used JBuilder since version 3.0 and it was my favorite IDE up until the first time I used IntellJ IDEA. IDEA is the best IDE I have ever used, regardless of platform (I have never worked with Smalltalk though).