Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://hostname:port'
Trying to deploy custom code on weblogic server using ant but getting exception like below?
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://hostname:port': User: custadmin , failed to be authenticated.. 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.
Please check below points and apply configurations as required:
1) Ensure hostname, port and credentials are correct
2) Enable tunneling as required in weblogic console
- Login to weblogic console http://hostname:port/console
- Environmnets -> Server -> Select Sever
- Go to Protcols -> HTTP
- Check Enable Tunneling
- Apply changes
- No restart required
Strangely this 'authentication failed' exception did not disappear from build.log file after trying to deploy the code several times.
So tried another workaround. Created another admin user 'weblogic' in weblogic console with the same password as user custadmin and assigned it to administrators group.
Ran the deployment script again (after updating weblogic.username=weblogic in custom deployment config files) and there were no authentication failed exceptions seen.
Still wondering why authentication failed exception appeared for non weblogic user !!
Did you encounter such bizarre issue before? Do leave a comment if you faced similar issue and if you were able to resolve this.
Trying to deploy custom code on weblogic server using ant but getting exception like below?
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://hostname:port': User: custadmin , failed to be authenticated.. 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.
Please check below points and apply configurations as required:
1) Ensure hostname, port and credentials are correct
2) Enable tunneling as required in weblogic console
- Login to weblogic console http://hostname:port/console
- Environmnets -> Server -> Select Sever
- Go to Protcols -> HTTP
- Check Enable Tunneling
- Apply changes
- No restart required
Strangely this 'authentication failed' exception did not disappear from build.log file after trying to deploy the code several times.
So tried another workaround. Created another admin user 'weblogic' in weblogic console with the same password as user custadmin and assigned it to administrators group.
Ran the deployment script again (after updating weblogic.username=weblogic in custom deployment config files) and there were no authentication failed exceptions seen.
Still wondering why authentication failed exception appeared for non weblogic user !!
Did you encounter such bizarre issue before? Do leave a comment if you faced similar issue and if you were able to resolve this.
No comments:
Post a Comment