• Post Reply Bookmark Topic Watch Topic
  • New Topic

Deployment/runtime problems with EJBs under j2eesdk-1_4-dr-windows-eval  RSS feed

 
Anton Kampter
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've been writing a very simple Stateful session bean compiled it and deployed it. The deploytool returned the message that deployment was successful. Just the server reported the following error messages:
[#|2004-02-04T15:25:14.609+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:14.609+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:14.625+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:29.796+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:29.812+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:29.968+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
[#|2004-02-04T15:25:30.062+0100|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM030:The ObjectName [ias:type=clusters,category=config] cant be registered as the configuration does not have it|#]
Starting the client returned the following error message:
C:\ex\Hello>java -cp helloworldClient.jar;%CLASSPATH% usingj2ee.hello.TestHello
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:640)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:280)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at usingj2ee.hello.TestHello.main(TestHello.java:15)


The strange thing is that the same program ran without any problems under j2sdkee-1_3_1-win, but it doesn't under j2eesdk-1_4-dr-windows-eval. It seems that my bean isn't registered in JNDI but i don't think that I have to do some specific configuration forn JNDI under j2eesdk-1_4-dr-windows-eval, do I? By the way, I got the same problem when I tried to run the example in the j2ee-1_4-dr-doc-tutorial. I assume that quite a few of you came across this problem when trying to run EJBs under j2eesdk-1_4-dr-windows-eval.
Thanks for your help!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!