[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant edited comment on ISPN-7392 at 1/25/17 9:35 AM:
----------------------------------------------------------------
The fix I implemented, aside from correctly parsing policy attributes, enables no-anonymous implicitly if it has not been specified, as that is the expected behaviour.
was (Author: nadirx):
The fix I implemented for upstream, aside from correctly parsing policy attributes, enables no-anonymous implicitly if it has not been specified, as that is the expected behaviour.
> The policy elements are ignored in the server sasl configuration
> ----------------------------------------------------------------
>
> Key: ISPN-7392
> URL: https://issues.jboss.org/browse/ISPN-7392
> Project: Infinispan
> Issue Type: Bug
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
>
> Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic reassigned ISPN-7228:
-----------------------------------------
Assignee: (was: Vladimir Blagojevic)
> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
> Key: ISPN-7228
> URL: https://issues.jboss.org/browse/ISPN-7228
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Priority: Minor
> Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic reassigned ISPN-7228:
-----------------------------------------
Assignee: Vladimir Blagojevic
> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
> Key: ISPN-7228
> URL: https://issues.jboss.org/browse/ISPN-7228
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7228:
-------------------------------------------
[~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles?
> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
> Key: ISPN-7228
> URL: https://issues.jboss.org/browse/ISPN-7228
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7228:
-------------------------------------------
[~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles?
[1] https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec8858413006...
> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
> Key: ISPN-7228
> URL: https://issues.jboss.org/browse/ISPN-7228
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7228:
--------------------------------------
Comment: was deleted
(was: [~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles?
[1] https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec8858413006...)
> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
> Key: ISPN-7228
> URL: https://issues.jboss.org/browse/ISPN-7228
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months