JmsAdapter Fails To Deploy Error is "BEA-149205" with "Security:090304 Authentication Failed: User denied"
Last updated on SEPTEMBER 05, 2017
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
***Checked for relevance on 02-June-2014***
In a shared testing environment, multiple users may have made changes to include unknown modifications to your JMSAdapter Deployments configuration.
Upon restart, you find the following errors in your <DOMAIN_HOME>/servers/<soa_server1>/logs/<soa_server1>.out file:
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User denied javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User denied
The JmsAdapter shows an Active status in the Admin Console, but does not have the expected OK green checkmark in the Health Column.
In this case ,the changes made to the environment included the accidental use of a white space in the JmsAdapter's Deployment configuration settings.
- The user navigates in the WebLogic Server Admin Console to "Deployments"
- Selects "JmsAdapter". The "Settings for JmsAdapter" page is shown with the "Overview" tab shown.
- Near the bottom of the page, there is a field for "Deployment Principal Name:".
- If a previous value has been removed or if the user updates this field with empty spaces and saves the update, you could see this issue when the server is restarted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms