Skip to Content
author's profile photo Former Member
Former Member

After bean deployment, no entires in JNDI

I guess I'll start a new thread for this, even though all my problems are revolving around getting a simple RFC to work.

I have created my Java module project - it matches the template Piers supplied in antoher thread. I created the .ear and deployed the bean successfully. However, when I look at the JNDI directory with the Visual Administrator, there are no entries for the name of my bean, or under the JNDI name I also supplied for the bean.

If it's of any help, here are the xml files:















<description>EAR description</description>



















<description>EJB JAR description</description>

<display-name>EJB JAR</display-name>














I have also specified a JNDI name for the bean of Z_RFC_SAMPLE.

Anybody got any ideas I can try?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 24, 2004 at 08:12 PM

    I have an update on the status of this problem, which prompts yet other questions:

    Rereading one of Stefan's answers in another thread, I saw that for the entries I need to be put in the JNDI directory, not only did the deployment have to be successful (which it was), but the "application needed to be running". Using Visual Administrator, under the Deploy >Server >EJBContainer, I saw that my bean had a big, fat red 'X' beside it. I took that to mean that it wasn't running. I clicked the button for "Start Application" and voila! I am now communicating with my RFM bean!

    Here's my new questions: how come the application (my bean) wasn't "running"? I want it to run when the server is started - is there some way to specify that?

    Thanks for your help...

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi David,

      first of all it's nice, that you managed it finally. According your question:

      An application is normally started after deployment by the corresponding container (EJB/Web..) without any user (administrator) interaction. On server restart, all already deployed apps are also restarted.

      The start can fail in both cases for many reasons, like missing applications, services, libraries... the starting application refers to.

      Please have a look at the "Log Viewer" service in the visual admin and open the log 8:defaultTrace.trc under the server node. There should be some entries describing the problem(s) why your actual app couldn't be started.

      To reproduce the problem you could remove your app using the Deploy service in the visual admin, redeploy it, check, if it has been started and look at the log again.

      Hope that helps.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.