• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Seperate JBoss / Tomcat not talking

 
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, similar to a previous problem posted here, I have Tomcat and JBoss seperately installed and previously was able to use a servlet to access a session bean. Now I have an entity bean and it appears as thought Tomcat can no longer find the JBoss JNDI service. I understand this from the message:
Name: myName
Type: java.lang.String
Value: Matthew Webster
Name: ejb
Type: org.apache.naming.NamingContext
Value: org.apache.naming.NamingContext@29ab3e
javax.naming.NamingException: Name Service is not bound in this Context
at org.apache.naming.NamingContext.lookup(NamingContext.java:837)
at org.apache.naming.NamingContext.lookup(NamingContext.java:181)

I was expecting another output of the session bean info - the bean being known as 'Service'. But it cannot find it.
I think I am correct in saying that JBoss and Tomcat are now running seperate JNDI services, but I don't understand how I should get Tomcat to use JBoss's service (so that it can access ejb's, obviously) and what has changed - I thought it was only my code.
Does anyone have any ideas? (pleeeease)
Matt.
 
Ranch Hand
Posts: 346
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Matthew Webster:
Hi, similar to a previous problem posted here, I have Tomcat and JBoss seperately installed and previously was able to use a servlet to access a session bean. Now I have an entity bean and it appears as thought Tomcat can no longer find the JBoss JNDI service. I understand this from the message:
Name: myName
Type: java.lang.String
Value: Matthew Webster
Name: ejb
Type: org.apache.naming.NamingContext
Value: org.apache.naming.NamingContext@29ab3e
javax.naming.NamingException: Name Service is not bound in this Context
at org.apache.naming.NamingContext.lookup(NamingContext.java:837)
at org.apache.naming.NamingContext.lookup(NamingContext.java:181)

I was expecting another output of the session bean info - the bean being known as 'Service'. But it cannot find it.
I think I am correct in saying that JBoss and Tomcat are now running seperate JNDI services, but I don't understand how I should get Tomcat to use JBoss's service (so that it can access ejb's, obviously) and what has changed - I thought it was only my code.
Does anyone have any ideas? (pleeeease)
Matt.


By having Tomcat and JBoss separately running do you mean that when Tomcat starts that it is reading the Jboss classes in order to talk to Jboss?
If you are unsure what I mean, look in your tomcat startup file..you should be seeing some extra lines of cod with Jboss classes..if not than refer to the previous notes on this forum on how to do that..
If that is not theproblem than something else is wrong obviously..
 
Bras cause cancer. And tiny ads:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic