[ 
https://issues.apache.org/jira/browse/QPID-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966557#comment-13966557
 ] 

Robbie Gemmell commented on QPID-5682:
--------------------------------------

Hi Justin,

If you are only doing the steps listed above then this is probably currently 
'expected'. The exception was thrown because you cant delete the authentication 
provider while it is still assigned to a port (in this case all of them). The 
UI could admittedly be smarter so it doesnt let you even try, or tells you 
without asking the broker to actually do anything.

To actually do what you were presumably trying to, after you add the anonymous 
provider you need to open the AMQP port and edit it to use the new 
authentication provider. I believe you currently still have to restart the 
broker after that, editing ports is one of the things we dont yet support doing 
most of live.

Robbie

> Error when removing passwordFile auth provider
> ----------------------------------------------
>
>                 Key: QPID-5682
>                 URL: https://issues.apache.org/jira/browse/QPID-5682
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.26, 0.29
>         Environment: Fedora 19 x86-64, Java 1.7.0_51
>            Reporter: Justin Ross
>
> Steps:
> 1. Add anonymous provider
> 2. Checkbox select the existing passwordFile provider
> 3. Click delete
> Error:RequestError: Unable to load 
> rest/authenticationprovider?id=4e86d14a-54e7-42dc-8f17-7403738e5b0a status: 
> 409
> {noformat}
> org.apache.qpid.server.model.IntegrityViolationException: Authentication 
> provider 'passwordFile' is set on port JMX_CONNECTOR           
>         at 
> org.apache.qpid.server.model.adapter.AuthenticationProviderAdapter.setState(AuthenticationProviderAdapter.java:242)
>           
>         at 
> org.apache.qpid.server.model.adapter.AbstractAdapter.setDesiredState(AbstractAdapter.java:122)
>                                
>         at 
> org.apache.qpid.server.configuration.updater.ChangeStateTask.call(ChangeStateTask.java:59)
>                                    
>         at 
> org.apache.qpid.server.configuration.updater.ChangeStateTask.call(ChangeStateTask.java:28)
>                                    
>         at 
> org.apache.qpid.server.configuration.updater.TaskExecutor.executeTask(TaskExecutor.java:213)
>                                  
>         at 
> org.apache.qpid.server.configuration.updater.TaskExecutor.access$200(TaskExecutor.java:46)
>                                    
>         at 
> org.apache.qpid.server.configuration.updater.TaskExecutor$CallableWrapper$1.run(TaskExecutor.java:252)
>                        
>         at java.security.AccessController.doPrivileged(Native Method)         
>                                                           
>         at javax.security.auth.Subject.doAs(Subject.java:415)                 
>                                                           
>         at 
> org.apache.qpid.server.configuration.updater.TaskExecutor$CallableWrapper.call(TaskExecutor.java:247)
>                         
>         at java.util.concurrent.FutureTask.run(FutureTask.java:262)           
>                                                           
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>                                               
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>                                               
>         at java.lang.Thread.run(Thread.java:744)                              
>                                                           
> 2014-04-11 09:56:12,356 DEBUG [qtp1115359418-26 - 
> /rest/authenticationprovider?id=4e86d14a-54e7-42dc-8f17
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to