• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB creation failed

 
Rajkumar Katudia
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey guys I am trying to port a application that used to run on Weblogic8.1 to weblogic 10.3.

I get the following error in the log files.

The java.naming.provider.url was t3://localhost:7021 earlier. I got a similar error so I changed it to t3://localhost:7001. I still get the same error.

Says EJB CREATION FAILED.

Please help me.


Some additional information:
Application used to run on Weblogic8.1 in the past.
I have two domins in the setup




environment:{java.naming.provider.url=t3://localhost:7001, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory, java.naming.referral=throw}
CLASS :class com.drapl.ds.adapter.MqToIvrsAdapter_3l1x87_Impl
TRANSACTION :null
EJB CREATION FAILED
javax.naming.NameNotFoundException: Unable to resolve 'com.drapl.bivr.cf.MQConnectionFactory'. Resolved 'com.drapl.bivr.cf'; remaining name 'MQConnectionFactory'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.drapl.bivr.ds.adapter.AbstractMQAdapter.getQueueReceiver(AbstractMQAdapter.java:257)
at com.drapl.bivr.ds.adapter.AbstractMQAdapter.getQueueReceiver(AbstractMQAdapter.java:228)
at com.drapl.bivr.ds.adapter.AbstractMQAdapter.start(AbstractMQAdapter.java:130)
at com.drapl.bivr.ds.adapter.AbstractMQAdapter.ejbCreate(AbstractMQAdapter.java:69)
at com.drapl.bivr.ds.adapter.MqToIvrsAdapter_3l1x87_Impl.ejbCreate(MqToIvrsAdapter_3l1x87_Impl.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:205)
at weblogic.ejb.container.pool.Pool.createInitialBeans(Pool.java:300)
at weblogic.ejb.container.manager.StatelessManager.initializePool(StatelessManager.java:444)
at weblogic.ejb.container.deployer.EJBDeployer.initializePools(EJBDeployer.java:1546)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:1377)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:589)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Stacktrace wrote: javax.naming.NameNotFoundException: Unable to resolve 'com.drapl.bivr.cf.MQConnectionFactory'. Resolved 'com.drapl.bivr.cf'; remaining name 'MQConnectionFactory'
 
Rajkumar Katudia
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
David O'Meara wrote:
Stacktrace wrote: javax.naming.NameNotFoundException: Unable to resolve 'com.drapl.bivr.cf.MQConnectionFactory'. Resolved 'com.drapl.bivr.cf'; remaining name 'MQConnectionFactory'



David baba, please dont play around.

People help me please.

Any clue any pointer would be a great help.
 
Rajkumar Katudia
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just wanted to know what does the following denote:


is port 7021 a standard port where ejbs are available for lookup?

Actually the original error was:




I tried searching for the port 7021 in the code and in the server config files and could not find it anywhere so I changed it to 7001 and then I get the error that i have posted in the first post.
 
Rajkumar Katudia
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Guys dont waste you time listening to poeple like David O'Meara who is a Sheriff here.

They're really good in wastin other's time.


As I've told in my previous post, it turned out to be the port that was the issue. The application used to pick port 7021 from the database.

I changed it there and things started working fine.

Hey, David O'Meara (Sheriff) you should not trouble people around here else I'm gonna tell your mamma....
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm on holidays. How much do you expect for nothing?
 
sudipto shekhar
Ranch Hand
Posts: 826
Chrome Eclipse IDE Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Raj,

I think you should refer to all the cross posts that you have done related to the same topic:

This is what I am talking about:

http://forums.oracle.com/forums/thread.jspa?threadID=1133902

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic