This particular error occured while deploying the jar file after succesfully generating the container.What is the cause for this error and what might be the solution.Please explain.
While attempting to connect to myserver, we were unable to create an InitialContext for the url http://localhost:7001/. This usually indicates that there is no server listening at that host/port. Please make sure that there is a server at the location specified by the default server profile.
weblogic.ejb.common.DeploymentException: javax.naming.CommunicationException:nullat weblogic.ejb.ui.deployer.WLSDeployAgent.getEJBManager(WLSDeployAgent.java:149)at weblogic.ejb.ui.deployer.WLSDeployAgent.getEJBManager(WLSDeployAgent.java:109)at weblogic.ejb.ui.deployer.WLSDeployAgent.access$0(WLSDeployAgent.java:108)at weblogic.ejb.ui.deployer.WLSDeployAgent$DeployThread.run(WLSDeployAgent.java:316)
Deployment failed.
rodjohnson@bigfoot.com
andy@contenttype.com
While attempting to connect to myserver, we were unable to create an InitialContext for the url http://localhost:7001/. This usually indicates that there is no server listening at that host/port. Please make sure that there is a server at the location specified by the default server profile.
weblogic.ejb.common.DeploymentException: javax.naming.CommunicationException:nullat weblogic.ejb.ui.deployer.WLSDeployAgent.getEJBManager(WLSDeployAgent.java:149)at weblogic.ejb.ui.deployer.WLSDeployAgent.getEJBManager(WLSDeployAgent.java:109)at weblogic.ejb.ui.deployer.WLSDeployAgent.access$0(WLSDeployAgent.java:108)at weblogic.ejb.ui.deployer.WLSDeployAgent$DeployThread.run(WLSDeployAgent.java:316)
Deployment failed.
rodjohnson@bigfoot.com
andy@contenttype.com