• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

RSA and JBOSS issue

Sander Evanfield
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

We use RSA (RAD) for development and use a seperate test build to deploy our tests on the JBOSS server. Both servers are on the same machine (Windows XP). The main app.ear is deployed on RSA and JBOSS(as part of cargo maven cactus). app.ear makes a call to a thirdparty (made by some other project group) jar which is deployed on RSA. The thirdparty jar cannot be deployed on JBOSS.
On the RSA admin console we have the namespace binding for the server and port for populating Context.PROVIDER_URL

service_ejb is in the thirdparty jar

Binding Identifier

Name in name space

String value

The app.ear on RSA is successful in making call to thirdparty jar and works fine.

For the JUnit side

The ServerJNDI.xml in JBOSS has a entry
jndiName="a/b/c/service_ejb_jndi_url" stringToBind="iiop::I.Paddr(same machine as RSA):2812"

On the coding side we have JUnit which talks to API in the app.ear deployed on JBOSS which has the
following code to talk to the ejb service in the thirdparty jar (deployed only on RSA)

InitialContext initContext = new InitialContext();
String toBePutInContextPROVIDERURL = (String)jndiContext.lookup("a/b/c/service_ejb_jndi_url");

javax.naming.NameNotFoundException: a not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:351)

I dont understand but looks like something fundamentally is wrong.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic