Dazed and confused

[thummp]

I have been trying for over a week to deploy a client server application on JBoss. We are considering switching over from Weblogic where it has been running successfully for years.

While I have no problem getting the excellent OReilly examples to run, I am unable to get my own EJBs to deploy. Like the titan examples, I have my home, remote, and bean classes. I have carefully created the ejb-jar.xml and jboss.xml files with the proper settings.

But when I deploy the .jar file all I see is that it has been started and deployed. I do not see the output telling me the bean itself has been deployed and I cannot find the jndi name on the jmx-console. What vexes me is the lack of an error telling me why the bean failed to deploy.

How do I even start to determine the cause of this problem?

[raja05]

> But when I deploy the .jar file all I see is that it
> has been started and deployed. I do not see the

Thats your confirmation that the jar has been deployed. Otherwise you should get something like a "Invalid Deployments blah blah blah...."

> and I cannot find the jndi name on the jmx-console.

Look in the jboss.j2ee space for ur ejbs. That will specify the JMX Names for ur EJBs.

Did u try running a client ? What errors are you getting(If any)

-Raj

[thummp]

Thanks for your reply. Yes I am looking for the JMX name under the jboss.j2ee. The EJBs for the Titan example are there, but my EJBs are not. When I try to do the context.lookup, I get the not bound error.

It seems as though if a .jar file contains an EJB and the correct descriptors, then the server log notates it upon startup - somthing along the lines of

[EjbModule] Deploying MEJB

I get that for the examples I run, but not for my .jar file.

[thummp]

My wife is pregnant. We were going with the name Zeno (after Zeno of Citium) but I will change it to whomever can help me to get these EJBs to load.

[juha]

Attach your server.log.

-- Juha

[thummp]

attached

[juha]

It's deploying your package as a regular Java archive, not as an EJB jar. Check the contents of the package and make sure you've got the ejb-jar.xml correctly in META-INF directory. Notice that META-INF is case sensitive.

-- Juha

[thummp]

I have checked and rechecked my ejb-jar.xml file a hundred times, along with my jboss.xml file. I am on windows 2000. Is META-INF still case sensitive? If so, then that is the problem because I am sure that mine is lower case. I can't check it till tomorrow, but if so, I'm gonna name the kid META-INF and maybe just shoot myself.

Thanks for the help.