teamsport
asked on
Empty server reply weblogic
I am running Weblogic 9.2 (weblogic.home=C:/bea/webl ogic92). When I try to do my an Ant deployment I continue to get the error. Everything was working fine, I tried to updated WLS to 10.3 and ran into this problem. Now I am trying to convert back and cannot do the deployment now. Any suggestions or ideas would be greatly appreciaited.
C:\workspace\FVO\build.xml :403: weblogic.Deployer$Deployer Exception: weblogic.deploy.api.tools. deployer.D eployerExc eption: Unable to connect to 't3://127.0.0.1:7001': invalid type code: 31. 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.
I have tried numerous things.
I can ping the server at 127.0.0.1, the weblogic console runs just fine. The console works as 127.0.0.2 or as localhost.
Enable Tunneling is checked
I have supplied my .properties example below
C:\workspace\FVO\build.xml
I have tried numerous things.
I can ping the server at 127.0.0.1, the weblogic console runs just fine. The console works as 127.0.0.2 or as localhost.
Enable Tunneling is checked
I have supplied my .properties example below
build_local.properties file and deployment script
weblogic.home=C:/bea/weblogic92
#weblogic.home=C:/bea/wlserver_10.3
weblogic.userid=weblogic
weblogic.password=weblogic
verbose="true"
#weblogic.adminurl=http://localhost:7001
weblogic.adminurl=t3://127.0.0.1:7001
weblogic.server=examplesServer
Deplyment
<target name="deploy" description="Deploy exploded web application">
<echo message="Deploying exploded web application" level="verbose" />
<!-- <echo> target ${weblogic.server}</echo>
<echo> source ${build.fvowar} </echo> -->
<wldeploy action="deploy"
source="${build.fvowar}" name="${appName}"
user="${weblogic.userid}" password="${weblogic.password}" verbose="true" adminurl="${weblogic.adminurl}"
debug="true" targets="${weblogic.server}" />
</target>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe you should add this to the bea weblogic zone as well.
ASKER
Thank you very much - sometimes we forget to try the obvious things when in a rush. Changing back to a later version of the JRE solved this problem.
Thanks Much
Thanks Much