Weblogic.deploy tool

I tried to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
on 7001. When I try to run it gives me following error: [java] JNDI naming exception:
Naming exception trying to connect to: t3://localhost:7001 as: system: password
system password is correct. I have tried http://localhost:7001 to but doesen't seem
to work. Any ideas.
HS

Similar Messages

Error using weblogic.deploy tool, while deploying a war

          Hi all, I'm trying to deploy a war with the follw command:
          java weblogic.deploy -host localhost -port 7001 -component NewScreenWar:BEAserver
          deploy beasystem NewScreenWar d:\newsscreen\weblogic\NewScreenWar.war
          It gives me following error:
          weblogic.j2ee.DeploymentException: Application NewScreenWar does not contain com
          ponent NewScreenWar at weblogic.deploy.deploy(deploy.java:668) at weblogic.deploy.runBody(deploy.java:358)
          at weblogic.utils.compiler.Tool.run(Tool.java:79) at weblogic.deploy.main(deploy.java:1601)
          Application NewScreenWar does not contain component NewScreenWar
          how do I resolve this...??
          thanx --anjaly


Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org

How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
Neeraj

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Deploy tool for weblogic 6.1

Hello all,
I have used j2ee refrence server and am really new to weblogic,
i am not adble to find the UI for the deploy tool like we have in t he the j2ee
server ,... do we have one in the WLS6.0 ??
if yes plz tell me the steps where i can find it ?
Thanks
Sunil

Sunil,
Unfortunately there isn't one for WLS 6.0. Are you using an IDE ? I would suggest
looking at both JBuilder and VisualCafe. They come with a deploy tool for WLS.
We have also addressed this issue in WLS 6.1. Please look at the DDE Editor -
http://edocs.bea.com/wls/docs61/programming/environment.html#ConsoleDDE. We have
defined various ANT tasks like DDInit which in conjunction with the DD Editor will
allow to to construct and deploy applications on WLS>
Nirav.
sunil wrote:
Hello all,
I have used j2ee refrence server and am really new to weblogic,
i am not adble to find the UI for the deploy tool like we have in t he the j2ee
server ,... do we have one in the WLS6.0 ??
if yes plz tell me the steps where i can find it ?
Thanks

Weblogic deployment APIs giving error for deployment on weblogic 10.3.2

I am using weblogic deployment APIs to distribute my war file on weblogic 10.3.2 but it gives the following error on distribute
weblogic.management.ManagementException: [Deployer:149003]Unable to access application source information in '<!DOCTYPE HTML PUBLIC "-/W3C/DTD HTML 4.0 Draft/EN">/app/jamagent.war' for application 'jamagent.war'. The specific error is: No application files exist.
My sample code is below.
DeploymentOptions options = null;
Target[] targets = myConnectedManager.getTargets();
Class wlsFactoryClass = Class.forName("weblogic.deploy.api.tools.SessionHelper");
Method m = wlsFactoryClass.getDeclaredMethod("getDeploymentManager",new Class[]{String.class,String.class,String.class,String.class});
m.setAccessible(true);
WebLogicDeploymentManager myConnectedManager = (WebLogicDeploymentManager)m.invoke(wlsFactoryClass, new Object[]{hostname,port,weblogicUsername,weblogicPasswd});
myConnectedManager.enableFileUploads();
options = new DeploymentOptions();
options.setName(destWarName);
ProgressObject po = myConnectedManager.distribute(targets, new File("/tmp/jamagent_orig.war), null,options);
The header of web.xml is
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
Can someone help why this is happening? I am not including weblogic-application.xml in the war file as i think this is not required for a war file. Is that the reason?
Edited by: user790199 on Dec 28, 2009 7:37 AM

Hi,
The DTD used in "web.xml" should not cause any issue ...though it's the OLD "web.xml"...Please try to run the Following command to Generate the New Deployment Descriptors from the Existing Application:
Step1). Open a Command Window and Run "setWLSEnv.sh" or "setWLSEnv.cmd".
Step2). In the Command Prompt move to the Current Directory where you have placed your Application and then Run the Following Command
java weblogic.DDConverter -d NewDDs jamagent.war
Here Above Command Will read the "jamagent.war" War archive and then It will generate the New DDs in "NewDDs" directory...Which we need to replace with the OLD DDs present in our WebApplication..
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

Can any body help me in creating a jar using Weblogic server tool

I have created the class files of the container manged bean successfully.I want to create the jar file using the weblogic tool.
I have created a new jar file and now I have to add a bean class file and a home class file to it.In the tool I choose a the path using the choose button.When I say next it complaints that it cannot locate the bean files.
Can any body please help me soon..
waiting for your reply.

I had similar problems with the WLS deploy tool. I think they were solved by making sure that I started the tool from the directory that contained the root package of my EJBs.
It might work...

Weblogic deploying an already deployed application!

Hi,
These are the following errors that I get. This is an already deployed application so not sure why weblogic deploys it again. This does not happen in all the machines.
Can someone tell me why it is doing this and how to make the application come up?
This is the error that I get when logging into the application:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Webserver console errors:
Unable to deploy EJB: jar from jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath, D:\bea\user_projects\ESMdomain\t
mp_ejbSramamoorthy7001myserver\-au306wtcrywq;D:\bea\user_projects\ESMdomain\applications\esm.ear\jar;D:\bea\j
dk131_06\jre\lib\rt.jar;D:\bea\jdk131_06\jre\lib\i18n.jar;D:\bea\jdk131_06\jre\lib\sunrsasign.jar;D:\bea\jdk1
31_06\jre\classes;D:\bea\jdk131_06\jre\lib\tools.jar;D:/bea/weblogic700\server\lib\weblogic_sp.jar;D:/bea/web
logic700\server\lib\weblogic.jar;D:\bea\jdk131_06\jre\jre\lib\rt.jar;JAVA_HOME\lib\dt.jar;D:/bea/weblogic700/
server/lib/mbeantypes/wlManagement.jar;D:/bea/weblogic700/server/lib/mbeantypes/ESMSecurityProviders.jar;D:/b
ea/user_projects/ESMdomain/applications/esmconfig;D:/bea/user_projects/ESMdomain/applications/esm.ear/jar;D:/
bea/user_projects/ESMdomain/esmlib/avalon.jar;D:/bea/user_projects/ESMdomain/esmlib/batik.jar;D:/bea/user_pro
jects/ESMdomain/esmlib/bsh-1.2b7.jar;D:/bea/user_projects/ESMdomain/esmlib/comm.jar;D:/bea/user_projects/ESMd
omain/esmlib/multipartrequest.jar;D:/bea/user_projects/ESMdomain/esmlib/crimson.jar;D:/bea/user_projects/ESMd
omain/esmlib/fop.jar;D:/bea/user_projects/ESMdomain/esmlib/gnu-regexp-1.1.4.jar;D:/bea/user_projects/ESMdomai
n/esmlib/jdom.jar;D:/bea/user_projects/ESMdomain/esmlib/oracle.jar;D:/bea/user_projects/ESMdomain/esmlib/repo
rting.jar;D:/bea/user_projects/ESMdomain/esmlib/xerces.jar, -d, tmp_ejbSramamoorthy7001myserver\-au306wtcrywq
, @C:\DOCUME~1\SRAMAM~1\LOCALS~1\Temp\compileList29351.tmp])
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:249)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:344)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServer
LifeCycleImpl.java:150)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Jul 29, 2004 11:44:23 AM EDT> <Error> <Deployer> <149231> <The slave deployer was unable to set the activati
on state to true for the application appsdiresm_ear-0
weblogic.management.ApplicationException: activate failed forwar
Module Name: war, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested excepti
on:
[weblogic.deployment.EnvironmentException: Could not resolve ejbLink: RackManager]
TargetException:
Unable to deploy EJB: jar from jar:Error 503--Service Unavailable
Thanks in advance and any help will be greatly appreciated!
Message was edited by sssd at Jul 29, 2004 10:56 AM

Hi,
These are the following errors that I get. This is an already deployed application so not sure why weblogic deploys it again. This does not happen in all the machines.
Can someone tell me why it is doing this and how to make the application come up?
This is the error that I get when logging into the application:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Webserver console errors:
Unable to deploy EJB: jar from jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath, D:\bea\user_projects\ESMdomain\t
mp_ejbSramamoorthy7001myserver\-au306wtcrywq;D:\bea\user_projects\ESMdomain\applications\esm.ear\jar;D:\bea\j
dk131_06\jre\lib\rt.jar;D:\bea\jdk131_06\jre\lib\i18n.jar;D:\bea\jdk131_06\jre\lib\sunrsasign.jar;D:\bea\jdk1
31_06\jre\classes;D:\bea\jdk131_06\jre\lib\tools.jar;D:/bea/weblogic700\server\lib\weblogic_sp.jar;D:/bea/web
logic700\server\lib\weblogic.jar;D:\bea\jdk131_06\jre\jre\lib\rt.jar;JAVA_HOME\lib\dt.jar;D:/bea/weblogic700/
server/lib/mbeantypes/wlManagement.jar;D:/bea/weblogic700/server/lib/mbeantypes/ESMSecurityProviders.jar;D:/b
ea/user_projects/ESMdomain/applications/esmconfig;D:/bea/user_projects/ESMdomain/applications/esm.ear/jar;D:/
bea/user_projects/ESMdomain/esmlib/avalon.jar;D:/bea/user_projects/ESMdomain/esmlib/batik.jar;D:/bea/user_pro
jects/ESMdomain/esmlib/bsh-1.2b7.jar;D:/bea/user_projects/ESMdomain/esmlib/comm.jar;D:/bea/user_projects/ESMd
omain/esmlib/multipartrequest.jar;D:/bea/user_projects/ESMdomain/esmlib/crimson.jar;D:/bea/user_projects/ESMd
omain/esmlib/fop.jar;D:/bea/user_projects/ESMdomain/esmlib/gnu-regexp-1.1.4.jar;D:/bea/user_projects/ESMdomai
n/esmlib/jdom.jar;D:/bea/user_projects/ESMdomain/esmlib/oracle.jar;D:/bea/user_projects/ESMdomain/esmlib/repo
rting.jar;D:/bea/user_projects/ESMdomain/esmlib/xerces.jar, -d, tmp_ejbSramamoorthy7001myserver\-au306wtcrywq
, @C:\DOCUME~1\SRAMAM~1\LOCALS~1\Temp\compileList29351.tmp])
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:249)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:344)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServer
LifeCycleImpl.java:150)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Jul 29, 2004 11:44:23 AM EDT> <Error> <Deployer> <149231> <The slave deployer was unable to set the activati
on state to true for the application appsdiresm_ear-0
weblogic.management.ApplicationException: activate failed forwar
Module Name: war, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested excepti
on:
[weblogic.deployment.EnvironmentException: Could not resolve ejbLink: RackManager]
TargetException:
Unable to deploy EJB: jar from jar:Error 503--Service Unavailable
Thanks in advance and any help will be greatly appreciated!
Message was edited by sssd at Jul 29, 2004 10:56 AM

Java application deployment tool

Hey everyone, i'm having some serious difficulty deploying an ejb application on bea weblogic.
I cannot find the java application deployment tool, or any concise documentation for that matter.
I have experience writing jsps, javabeans, servlets etc. and deploying them with ant.
Thanks for any help on this tool and or deployment techniques for ejb.
/jeff

You may want to direct your query to one of the web forums run by BEA. Most folks here are familiar with the j2ee specs and the Sun implementations of those specs.
These news groups may be a good place to start. http://newsgroups2.bea.com/cgi-bin/dnewsweb
vbk

Regarding deployment tool

hi freinds
i installed j2ee from sun site...now i want deployment tool to work with ejb....
how can i get that

NetBeans 5.5 integrates nicely with JavaEE SDK, glassfish, Sun Java System Application Server, Jboss, weblogic...making it easy to develop and deploy EJB apps.
-cheng

Question related to remote weblogic deployment using wldeploy task

Problem Description: Iam trying to perform a remote deployment using wldeploy task from one of the unix box(this box does not have a weblogic instance at all) to a remote unix weblogic server. I get the following connection exception. This script works fine when I do a remote deployment from my windows machine(this has a local weblogic server)to the same remote unix weblogic server.
Question:
1. Do I need to have a weblogic instance locally where this wldeploy task is executing?
2. What configuration should be done in the remote weblogic server to support remote deployment?
The ant task is:
<property name="wlantjars" value="/ftmp/users/usrgrb/tmp/antjars" />
<path id="wlappc.classpath">
<fileset dir="${wlantjars}">
<include name="*.jar"/>
</fileset>
</path>
<taskdef name="wldeploy" classpathref="wlappc.classpath" classname="weblogic.ant.taskdefs.management.WLDeploy"/>
<target name="deployear_dev2">
<wldeploy user="weblogic" password="*******" adminurl="t3://he3unxd189v01:9100" action="deploy" upload="true" remote="true" source="${build.dir}/mktpx.ear" name="mktpx" targets="devCluster" />
</target>
I receive the following error when I execute the ant task "deployear_dev2"
Buildfile: build.xml
deployear_dev2:
[wldeploy] weblogic.Deployer -remote -upload -noexit -name mktpx -source /usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/dist/mktpx.ear -targets devCluster -adminurl t3://he3unxd189v01:9100 -user weblogic -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -remote -upload -noexit -name mktpx -source /usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/dist/mktpx.ear -targets devCluster -adminurl t3://he3unxd189v01:9100 -user weblogic -deploy
[wldeploy] javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://he3unxd189v01:9100' as user, 'weblogic'. Error received: Couldn't connect to any host
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
[wldeploy] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
[wldeploy] at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
[wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy] at weblogic.Deployer.run(Deployer.java:70)
[wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:348)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:357)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:698)
[wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:199)
[wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[wldeploy] Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://he3unxd189v01:9100' as user, 'weblogic'. Error received: Couldn't connect to any host
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:251)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:191)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:147)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
[wldeploy] ... 32 more
[wldeploy] Caused by: java.io.IOException: Couldn't connect to any host
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:156)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
[wldeploy] at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
[wldeploy] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:240)
[wldeploy] ... 36 more
[wldeploy] Caused by: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST vmcid: 0x0 minor code: 0 completed: No]
[wldeploy] at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)
[wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:590)
[wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:547)
[wldeploy] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
[wldeploy] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
[wldeploy] at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
[wldeploy] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
[wldeploy] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
[wldeploy] at javax.naming.InitialContext.init(InitialContext.java:223)
[wldeploy] at javax.naming.InitialContext.<init>(InitialContext.java:197)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:143)
[wldeploy] ... 40 more
[wldeploy] Caused by: org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST vmcid: 0x0 minor code: 0 completed: No
[wldeploy] at weblogic.iiop.LocateReplyMessage.needsForwarding(LocateReplyMessage.java:171)
[wldeploy] at weblogic.iiop.IORManager.locateInitialReference(IORManager.java:254)
[wldeploy] at weblogic.corba.orb.ORB.resolve_initial_references(ORB.java:258)
[wldeploy] at weblogic.corba.client.naming.ClientORBInfo.<init>(ClientORBInfo.java:34)
[wldeploy] at weblogic.corba.client.naming.ClientORBHelper.createORBInfo(ClientORBHelper.java:42)
[wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.cacheORB(ORBHelper.java:314)
[wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.cacheORBAndCreateURL(ORBHelper.java:323)
[wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:583)
[wldeploy] ... 49 more
BUILD FAILED
/usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/build/build.xml:366: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://he3unxd189v01:9100': Unknown object in LOCATE_REQUEST. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
Total time: 9 seconds

regarding error:
Caused by: org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST vmcid: 0x0 minor code: 0 completed: No
Make sure to place the wlfullclient.jar at the beginning of the classpath ...any other WLS specific Jars need not to be added additionally. For above error please refer to : Client SAF error
Few Things:
1). When I execute the ant build from a remote box , should I have a weblogic server running...the reason I ask is..does the wldeploy task work only if there is an active weblogic domain in the local machine. When I execute the same build from my windows machine where I have a local instance of weblogic , it works uccessfully .Whenever you try to deploy any application on WebLogic Domain then the Admin Server must be running. Because the deployment entries goes inside the "config.xml" and the original copy of this file is maintained by AdminServer only. So the Admin Server must be running for any kind of configuration changes or for Deployment.
2). I am told that http protocol is not an option in my work place and I have to use t3 protocol only. In that case, based on the error below, is it possible that the connection between my local unix box and the remote weblogic box is stricted? How to I test the connectivity using t3? I pinged the server from the local unix server and it came back with reply, but could not telnet to that remote box nor ftp to that box does not work.You can check t3 protcol is working fine or not by using the following one line command:
java weblogic.Admin -url t3://he3unxd189v01:9100 -username weblogic -password weblogic PING
If above command fails to ping the server it means either you are using a wrong HostName & Port OR your N/W is doesnot allow t3 protocol connections OR there may be a N/W Issue.
Thanks
Jay SenSharma

Receiving ERRORS using WEBLOGIC.DEPLOY

Hi everybody,
I am getting strange errors when using the weblogic.deploy command-line
function. I am using WL6.0 on W2000.
Deploy/Update
command: java weblogic.deploy -port 7001 -host localhost update
beapasword MyWebApplication stage\MyWebApplication.war
error: java.lang.NullPointerException
at
weblogic.deploy.deployApplication(deploy.java:383)
at weblogic.deploy.deploy(deploy.java:340)
at weblogic.deploy.runBody(deploy.java:219)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.deploy.main(deploy.java:954)
Undeploy
Command: java weblogic.deploy -port 7001 -host localhost undeploy
beapasword MyWebApplication
error: giving up after two minutes
And it looks that just a Update doens't work. I have to undeploy first and
the do a update to see the changes I've made in my file.
Any suggestions....
M-

Hi.
WLS version and service pack level? Please post the entire weblogic.deploy command along
with the exception that follows.
Thanks,
Michael
Harjeet Singh wrote:
I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
on 7001. When I try to run it gives me following error:
[java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
as: system: password
system password is correct. I have tried http://localhost:7001 to but doesen't seem
to work.
Any ideas.
HS--
Michael Young
Developer Relations Engineer
BEA Support

Unable to start MS NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory

Hi Folks,
I really need ur assistance on this, I am failing to start my weblogic managed server which is on WL 10.3.4 and hosted on Windows 2008R2 server.
I am getting the below exception:
<<WLS Kernel>> <> <> <1365769487402> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
     at weblogic.sip.plugin.SipPlugin.startService(SipPlugin.java:25)
     at weblogic.server.ServiceActivator.start(ServiceActivator.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: java.lang.ClassNotFoundException: weblogic.sip.tools.SipToolsFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     at weblogic.sip.plugin.SipPlugin.startService(SipPlugin.java:25)
     at weblogic.server.ServiceActivator.start(ServiceActivator.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Now the I dont want to use the SIP and have done the following:
1. Disabled the SIP from my Weblogic Console and restarted the Admin Server
2. Modified my init script from
<setenv name="WLSS_HOME">
<value>E:\Oracle\Middleware\wlserver_10.3/sip</value>
</setenv>
     <setenv name="SIP_ENABLED">
          <value>true</value>
     </setenv>
to
<setenv name="WLSS_HOME">
<value>E:\Oracle\Middleware\wlserver_10.3/sip</value>
     </setenv>
          <setenv name="SIP_ENABLED">
          <value>false</value>
               </setenv>
3. Modified my class paths so SIP wont be called.
Now the interesting part, actually this setup is a running setup and I have installed it from scratch..The thing here is it might sound silly....But the weblogic still picks up the Classpath for SIP during startup, be it via node manger or even on the server.
<WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
E:\Oracle\Middleware\user_projects\domains\DOMAIN_XYZ\lib\sipactivator.jar>
<BEA-002647> <The service plugin, com.oracle.core.sip.activator, was added from E:\Oracle\Middleware\user_projects\domains\DOMAIN_XYZ\lib\sipactivator.jar.>
If you see its a extension lib file, now my query without deleting the file from the extension lib how can i get rid of it.
Hope someone can help me out.
Thanks

Hi Kishore,
Thanks for the update, but I had already done those changes, please find my current config.xml but I noticed one thing when I restart my weblogic instance it creates a new config.xml with a name like this config.xml and it doesnt reflect the original config.xml which I am trying to use. I some how feel that the config.xml is being picked up while stating the instance instead of the original config.xml.
I am placing both of them below with the respective names.
config.xml (the one i am trying to use)
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>TEST</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration>
<name>TEST</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}xxxxx</credential-encrypted>
<node-manager-username>wlxxxx</node-manager-username>
<node-manager-password-encrypted>{AES}xxxxx</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<machine>localhost</machine>
<listen-address></listen-address>
</server>
<server>
<name>Test01</name>
<machine>localhost</machine>
<listen-port>9001</listen-port>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
</server-start>
</server>
<server>
<name>Test02</name>
<machine>Machine2</machine>
<listen-port>9001</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test03</name>
<machine>localhost</machine>
<listen-port>9002</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test04</name>
<machine>Machine2</machine>
<listen-port>9002</listen-port>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test_ES01</name>
<machine>localhost</machine>
<listen-port>9003</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES02</name>
<machine>Machine2</machine>
<listen-port>9003</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES03</name>
<machine>localhost</machine>
<listen-port>9004</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES04</name>
<machine>Machine2</machine>
<listen-port>9004</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK01</name>
<machine>localhost</machine>
<listen-port>9005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK02</name>
<machine>Machine2</machine>
<listen-port>9005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK03</name>
<machine>localhost</machine>
<listen-port>9006</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK04</name>
<machine>Machine2</machine>
<listen-port>9006</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test05</name>
<machine>localhost</machine>
<listen-port>9007</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>Test07</name>
<machine>localhost</machine>
<listen-port>9008</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>Test06</name>
<machine>Machine2</machine>
<listen-port>9007</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test08</name>
<machine>Machine2</machine>
<listen-port>9008</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test_IN01</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>localhost</machine>
<listen-port>9003</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.application</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.classloader</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.cluster</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.connector</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.core</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.debug</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.deploy</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.descriptor</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.diagnostics</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.ejb</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.iiop</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jdbc</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jms</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jpa</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.management</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.messaging</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.messagingbridge</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.protocol</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.sca</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.security</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.servlet</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.store</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.t3</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.transaction</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.work</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.workarea</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.wtc</name>
<enabled>false</enabled>
</debug-scope>
</server-debug>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Direct-Write</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN02</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>Machine2</machine>
<listen-port>9003</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic</name>
<enabled>false</enabled>
</debug-scope>
<debug-libraries>true</debug-libraries>
<class-finder>true</class-finder>
<classpath-servlet>true</classpath-servlet>
<class-loader>true</class-loader>
<debug-server-life-cycle>true</debug-server-life-cycle>
</server-debug>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Cache-Flush</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN03</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>localhost</machine>
<listen-port>9004</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Cache-Flush</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN04</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine>Machine2</machine>
<listen-port>9004</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<java-compiler>javac</java-compiler>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
<server-diagnostic-config>
<wldf-diagnostic-volume>Low</wldf-diagnostic-volume>
</server-diagnostic-config>
</server>
<embedded-ldap>
<name>TEST</name>
<credential-encrypted>{AES}xxxxx</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<app-deployment>
<name>Test_hkapp01</name>
<target>Test_HK01</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkapp01</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkrp01</name>
<target>Test_HK03</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkrp01</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testapp05</name>
<target>Test05</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testapp05\test.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>testrp07</name>
<target>Test07/target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testrp07\Testrp.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testrp08</name>
<target>Test08</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testrp08\Testrp.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testapp06</name>
<target>Test06</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testapp06\Test.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkrp04</name>
<target>Test_HK04</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkrp04</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkapp02</name>
<target>Test_HK02</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkapp02</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<machine>
<name>localhost</name>
<node-manager>
<name>localhost</name>
<nm-type>SSL</nm-type>
<listen-address>xxx-xxx-xxx-xxx</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<machine>
<name>Machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>xxx-xxx-xxx-xxx</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>Test01app_DS</name>
<target>Test01</target>
<descriptor-file-name>jdbc/Test01app_DS-4659-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test03rp_DS</name>
<target>Test03</target>
<descriptor-file-name>jdbc/Test03rp_DS-3850-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test02app_DS</name>
<target>Test02</target>
<descriptor-file-name>jdbc/Test02app_DS-7531-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test04rp_DS</name>
<target>Test04</target>
<descriptor-file-name>jdbc/Test04rp_DS-5676-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Starting up j2ee and EJB deployment tool on Windows 98

I will start off this question with an apology if it is too stupid,
basic, or placed in the wrong group. I am relatively new to the world
of Java and even newer to the world of Server-side Java and EJBs.
However, I am plugging away.
I am using my trusty 4 year old system with Windows 98 second edition
to dabble with Server-side Java and EJB applications. I am using
Tomcat 4.0 as my server. When I try and start the j2ee server or the
EJB deployment tool I get the following scrolling messages:
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Syntax error
Syntax error
Syntax error
Out of environment space
Bad command or file name
I have tried to adjust the memory settings in the DOS window with no
success. My question has three parts:
1) Can these applications be run using Windows 98 and if so what are
the exact DOS window memory settings for this?
2) Where exactly can I find the documentation that specifies this?
(please be specific as possible as I have read the readme.txt files
supplied with j2ee)
3) Should this and similar questions be posted in another
group/section?
I truly appreciate anyone's help with this.
Sincerely,
Tim

You're going to have a lot of pain unless you upgrade to Windows 2000 or XP.
In the mean time, set your environment size much larger (google for "Out of
environment space") and use WinOne from http://www.cia.com.au/luke/ ...
that's how I scraped by on Windows 98 for a while.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Tim" <[email protected]> wrote in message
news:[email protected]..
I will start off this question with an apology if it is too stupid,
basic, or placed in the wrong group. I am relatively new to the world
of Java and even newer to the world of Server-side Java and EJBs.
However, I am plugging away.
I am using my trusty 4 year old system with Windows 98 second edition
to dabble with Server-side Java and EJB applications. I am using
Tomcat 4.0 as my server. When I try and start the j2ee server or the
EJB deployment tool I get the following scrolling messages:
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Syntax error
Syntax error
Syntax error
Out of environment space
Bad command or file name
I have tried to adjust the memory settings in the DOS window with no
success. My question has three parts:
1) Can these applications be run using Windows 98 and if so what are
the exact DOS window memory settings for this?
2) Where exactly can I find the documentation that specifies this?
(please be specific as possible as I have read the readme.txt files
supplied with j2ee)
3) Should this and similar questions be posted in another
group/section?
I truly appreciate anyone's help with this.
Sincerely,
Tim

Problem with weblogic.deploy and cluster

          I'm having some problems with the weblogic.deploy class when trying to refresh
          a jsp file. Using the following command to redeploy the entire application works
          fine:
          java weblogic.deploy -port 9876 -host apptest01 update
          administrator portal c:\portal-site
          However using the following command to refresh just one jsp
          file:
          java weblogic.deploy -url t3://apptest01:9876 -username system
          -jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
          refresh administrator portal
          produces the following stack trace:
          javax.naming.NameNotFoundException: Unable to resolve
          weblogic.management.home.olbcluster.
          Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
          remaining name ''
          at weblogic.rmi.internal.BasicOutboundRequest.
          sendReceive(BasicOutboundRequest.java:85)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          invoke(ReplicaAwareRemoteRef.java:255)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          invoke(ReplicaAwareRemoteRef.java:222)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy0.lookup(Unknown Source)
          at weblogic.jndi.internal.WLContextImpl.
          lookup(WLContextImpl.java:323)
          at weblogic.management.tools.WebAppComponentRefreshTool.
          getMBeanHomeForManagedServer
          WebAppComponentRefreshTool.java:498)
          at weblogic.management.tools.
          WebAppComponentRefreshTool.
          getComponentMBeanForServer
          (WebAppComponentRefreshTool.java:225)
          at weblogic.management.tools.
          WebAppComponentRefreshTool.findInternalPaths
          (WebAppComponentRefreshTool.java:187)
          at weblogic.management.tools.WebAppComponentRefreshTool.
          refresh(WebAppComponentRefreshTool.java:151)
          at weblogic.deploy.refresh(deploy.java:704)
          at weblogic.deploy.runBody(deploy.java:374)
          at weblogic.utils.compiler.Tool.run(Tool.java:79)
          at weblogic.deploy.main(deploy.java:1601)
          Unable to resolve weblogic.management.home.olbcluster.
          Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
          Any ideas?


          "John Murphy" <[email protected]> wrote:
          >
          >I'm having some problems with the weblogic.deploy class when trying to
          >refresh
          >a jsp file. Using the following command to redeploy the entire application
          >works
          >fine:
          >
          >java weblogic.deploy -port 9876 -host apptest01 update
          >administrator portal c:\portal-site
          >
          >However using the following command to refresh just one jsp
          >file:
          >
          >java weblogic.deploy -url t3://apptest01:9876 -username system
          >-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
          >refresh administrator portal
          >
          >produces the following stack trace:
          >
          >javax.naming.NameNotFoundException: Unable to resolve
          >weblogic.management.home.olbcluster.
          >Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
          >remaining name ''
          > at weblogic.rmi.internal.BasicOutboundRequest.
          > sendReceive(BasicOutboundRequest.java:85)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          > invoke(ReplicaAwareRemoteRef.java:255)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          > invoke(ReplicaAwareRemoteRef.java:222)
          > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          > at $Proxy0.lookup(Unknown Source)
          > at weblogic.jndi.internal.WLContextImpl.
          > lookup(WLContextImpl.java:323)
          > at weblogic.management.tools.WebAppComponentRefreshTool.
          > getMBeanHomeForManagedServer
          > WebAppComponentRefreshTool.java:498)
          > at weblogic.management.tools.
          > WebAppComponentRefreshTool.
          > getComponentMBeanForServer
          > (WebAppComponentRefreshTool.java:225)
          > at weblogic.management.tools.
          > WebAppComponentRefreshTool.findInternalPaths
          > (WebAppComponentRefreshTool.java:187)
          > at weblogic.management.tools.WebAppComponentRefreshTool.
          > refresh(WebAppComponentRefreshTool.java:151)
          > at weblogic.deploy.refresh(deploy.java:704)
          > at weblogic.deploy.runBody(deploy.java:374)
          > at weblogic.utils.compiler.Tool.run(Tool.java:79)
          > at weblogic.deploy.main(deploy.java:1601)
          >Unable to resolve weblogic.management.home.olbcluster.
          >Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
          >
          >Any ideas?
          >
          Hi John,
          How's tricks?
          It looks to me as though the olbcluster JNDI reference isn't being resolved from
          the tree. A similar error results when a Connection Pool cannot be resolved, the
          JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
          it often turns out to be an error in the correlation between the deployment descriptors,
          settings applied via the console and references made in the code.
          That's my tuppence worth,
          James :-)

Weblogic.deploy update -- and that null message

So, does anyone else receive an inexplicable error message when running "weblogic.deploy update" in version 6.0, stating that a "java.lang.NullPointerException" has been thrown?
The update occurs anyway, but seeing a message like this is always disconcerting. Anyone have an idea why this is happening?
(The exact trace that I receive is cut-n-pasted below.)
T Fenstermaker
Online Resources
McLean VA
java.lang.NullPointerException
at weblogic.deploy.deployApplication(deploy.java:383)
at weblogic.deploy.deploy(deploy.java:340)
at weblogic.deploy.runBody(deploy.java:219)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.deploy.main(deploy.java:954)

If you use the -debug setting with weblogic.deploy you get more
info. I'm deploying an .ear file, deployment works if I use the
console, and if I just copy the ear file to the domain and WLS
autodeploys.
I getting the following error.
[java] java.net.MalformedURLException: unknown protocol: d
[java] at java.net.URL.<init>(URL.java:480)
[java] at java.net.URL.<init>(URL.java:376)
[java] at java.net.URL.<init>(URL.java:330)
[java] at weblogic.deploy.parseSource(deploy.java:539)
[java] at weblogic.deploy.init(deploy.java:299)
[java] at weblogic.deploy.runBody(deploy.java:214)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:81)
[java] at weblogic.deploy.main(deploy.java:1036)
[java] javax.management.InstanceNotFoundException: harmony
[java] at weblogic.rmi.internal.AbstractOutboundRequest.sendRecei
OutboundRequest.java:90)
[java] at weblogic.management.internal.AdminMBeanHomeImpl_WLStub.
minMBeanHomeImpl_WLStub.java:1147)
[java] at weblogic.deploy.findMBean(deploy.java:815)
[java] at weblogic.deploy.findApplicationMBean(deploy.java:804)
[java] at weblogic.deploy.deploy(deploy.java:312)
[java] at weblogic.deploy.runBody(deploy.java:222)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:81)
[java] at weblogic.deploy.main(deploy.java:1036)
[java] java.lang.NullPointerException
[java] at weblogic.deploy.deployApplication(deploy.java:420)
[java] at weblogic.deploy.deploy(deploy.java:367)
[java] at weblogic.deploy.runBody(deploy.java:222)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:81)
[java] at weblogic.deploy.main(deploy.java:1036)
[java] Java Result: 1
"T Fenstermaker" <[email protected]> wrote:
>
So, does anyone else receive an inexplicable
error message when running "weblogic.deploy
update" in version 6.0, stating that a
"java.lang.NullPointerException" has been thrown?I take it from the lack of response that the answer to
this question must be either:
a) No, no one else receives this inexplicable error, or,
b) Yes, everyone else receives this inexplicable error
and it's so well known how dare I ask.
Anyone want to give me a clue which of these two is correct?
T Fenstermaker
Online Resources
McLean VA

Weblogic.deploy tool

Similar Messages

Maybe you are looking for