[JBoss JIRA] (WFLY-3566) JMXSubsystemRemove is unsafe
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3566?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3566:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1087711|https://bugzilla.redhat.com/show_bug.cgi?id=1087711] from MODIFIED to ON_QA
> JMXSubsystemRemove is unsafe
> ----------------------------
>
> Key: WFLY-3566
> URL: https://issues.jboss.org/browse/WFLY-3566
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMX
> Affects Versions: 8.1.0.Final
> Reporter: Brian Stansberry
> Assignee: Kabir Khan
> Fix For: 9.0.0.Alpha1
>
>
> The service installed by JMXSubsytemAdd is used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it.
> 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header.
> 2) The rollbackRuntime method needs to be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-86) Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-86?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-86:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1103052|https://bugzilla.redhat.com/show_bug.cgi?id=1103052] from MODIFIED to ON_QA
> Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-86
> URL: https://issues.jboss.org/browse/WFCORE-86
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Dominik Pospisil
> Assignee: Dominik Pospisil
>
> java.lang.Exception: Http request failed.
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:423)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.testRollbackAcrossGroupsRolloutPlan(RolloutPlanTestCase.java:322)
> ...
> Caused by: java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:201)
> at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:50)
> at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:80)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:420)
> ... 43 more
> Standard Output
> [Host Controller] [0m[0m14:49:48,985 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> [Server:main-two] 14:49:49,579 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:49,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,586 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:49,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,696 INFO [org.jboss.web] (ServerService Thread Pool -- 73) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-one] 14:49:49,710 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 73) RolloutServlet initialized: 1401389389710
> [Server:main-three] 14:49:49,791 INFO [org.jboss.web] (ServerSe[Server:main-two] 14:49:49,762 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-two] 14:49:49,788 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 58) RolloutServlet initialized: 1401389389786
> [Server:test-one] 14:49:49,784 INFO [org.jboss.web] (ServerService Thread Pool -- 21) JBAS018210: Register web context: /RolloutPlanTestCase
> rvice Thread Pool -- 67) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-three] 14:49:49,804 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 67) RolloutServlet initialized: 1401389389803
> [Server:test-one] 14:49:49,820 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 21) RolloutServlet initialized: 1401389389820
> [Server:other-two] 14:49:49,891 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:49:50,826 INFO [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:other-two] 14:49:50,845 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 71) RolloutServlet initialized: 1401389390845
> [Server:main-two] 14:49:51,172 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:51,174 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:51,169 INF[Server:other-two] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> O [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:11,333 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:test-one] 14:50:11,346 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-three] 14:50:11,376 INFO [org.jboss.web] (ServerService Thread Pool -- 69) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-two] 14:50:11,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 62ms
> [Server:test-one] 14:50:11,397 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 59ms
> [Server:main-three] 14:50:11,548 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 175ms
> [Server:other-two] 14:50:11,634 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:other-two] 14:50:11,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 132ms
> [Server:main-one] 14:50:11,748 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-one] 14:50:11,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 385ms
> [Server:main-three] 14:50:12,225 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/main-three/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-three] 14:50:12,226 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:50:12,217 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/test-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:test-one] 14:50:12,218 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:12,218 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-two/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-two] 14:50:12,219 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:50:12,221 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-one] 14:50:12,223 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:50:12,237 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/other-two/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:other-two] 14:50:12,252 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Host Controller] [0m[0m14:50:12,261 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> ERROR [org.jboss.as.cli.CommandContext] {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"test-binding\")
> ]' not found"},
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3269) XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3269?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3269:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1133961|https://bugzilla.redhat.com/show_bug.cgi?id=1133961] from MODIFIED to ON_QA
> XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-3269
> URL: https://issues.jboss.org/browse/WFLY-3269
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Emmanuel Hugonnet
> Fix For: 9.0.0.Alpha1
>
>
> {code}
> Trying so, I run in the error (when starting WildFly) :
> 10:28:29,674 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[76,25]
> Message: JBAS014724: Missing required attribute(s): FORCE
> at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.domain.management.parsing.ManagementXml.parseUsernameToDn_2_0(ManagementXml.java:2118) [wildfly-domain-management-8.0.0.Final.jar:8.0.0.Final]
> {code}
> {code}
> <security-realm name="MgtRealm">
> <authentication>
> <ldap connection="ovodavLDAP" base-dn="ou=People,dc=hydrogenic,dc=local">
> <!-- <advanced-filter filter="(&(cn=jboss-admin)(member=uid={0},ou=People,dc=hydrogenic,dc=local))" recursive="true"/> -->
> <username-filter attribute="uid"/>
> </ldap>
> </authentication>
> <authorization>
> <ldap connection="ovodavLDAP">
> <username-to-dn>
> <username-filter base-dn="ou=People,dc=hydrogenic,dc=local" recursive="false" attribute="uid" user-dn-attribute="dn" />
> </username-to-dn>
> <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="uid">
> <group-to-principal base-dn="ou=Groups,dc=hydrogenic,dc=local" recursive="true" search-by="DISTINGUISHED_NAME">
> <membership-filter principal-attribute="uniqueMember" />
> </group-to-principal>
> </group-search>
> </ldap>
> </authorization>
> </security-realm>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2964) Missing i18n
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2964?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2964:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1067024|https://bugzilla.redhat.com/show_bug.cgi?id=1067024] from MODIFIED to ON_QA
> Missing i18n
> ------------
>
> Key: WFLY-2964
> URL: https://issues.jboss.org/browse/WFLY-2964
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMX, Patching
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 9.0.0.Alpha1
>
>
> system-jmx/src/main/java/org/jboss/system/ServiceMBeanSupport.java
> 379 log.error(e);
> patching/src/main/java/org/jboss/as/patching/validation/PatchArtifact.java
> 102 ctx.getErrorHandler().error("Failed to load identity info for patch " + patch.getPatchId(), e);
> 116 ctx.getErrorHandler().error("Failed to load previous patch", e);
> patching/src/main/java/org/jboss/as/patching/validation/XmlFileState.java
> 51 ctx.getErrorHandler().error("File doesn't exist: " + file.getAbsolutePath());
> 56 ctx.getErrorHandler().error("Failed to parse file: " + file.getAbsolutePath(), e);
> patching/src/main/java/org/jboss/as/patching/validation/PatchElementProviderArtifact.java
> 84 ctx.getErrorHandler().error("Layer not found: " + metadata.getName());
> patching/src/main/java/org/jboss/as/patching/runner/IdentityPatchContext.java
> 435 PatchLogger.ROOT_LOGGER.warnf(e, "failed to undo change (%s)", modification);
> ejb3/src/main/java/org/jboss/as/ejb3/tx/CMTTxInterceptor.java
> 169 EjbLogger.ROOT_LOGGER.error(t);
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-2461) refactoring of character escaping in operation parameter values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2461?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2461:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1056933|https://bugzilla.redhat.com/show_bug.cgi?id=1056933] from MODIFIED to ON_QA
> refactoring of character escaping in operation parameter values
> ---------------------------------------------------------------
>
> Key: WFLY-2461
> URL: https://issues.jboss.org/browse/WFLY-2461
> Project: WildFly
> Issue Type: Task
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.CR1
>
>
> There are potential issues with unescaping operation parameter values and command argument values that will be used as operation request parameter values.
> The culprit is that these values are parsed twice: first, with the general command line parser and the second time with the value type parser (which depends on the type of the value: could be list, property list, DMR, etc). Both parsers support and may perform unescaping. Which may lead to confusions and issues like WFLY-161 or WFLY-1791 and then confusing conditions in the code.
> The goal of this task is to not unescape parameter/argument values on the first parsing and leave it to the value type parsers. This concerns *only* parameter and argument value parsing, parsing of the other parts of operation requests and commands will remain as it is.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-7) MapAttributeDefinition and ListAttributeDefinition incorrectly assume valid types in convertParameterExpressions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-7?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFCORE-7:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1056578|https://bugzilla.redhat.com/show_bug.cgi?id=1056578] from MODIFIED to ON_QA
> MapAttributeDefinition and ListAttributeDefinition incorrectly assume valid types in convertParameterExpressions
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-7
> URL: https://issues.jboss.org/browse/WFCORE-7
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha3
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha4
>
>
> The AttributeDefinition.convertParameterExpression method is called before the validator has validated the model node. This is because the conversion is part of doing any configured "cleanup" of the node before validation. (See AS7-6224.)
> MapAttributeDefinition and ListAttributeDefinition break this in their overrides of the method by doing unsafe type conversions. When these fail, users get unfriendly failure messages instead of the ones that the validators would provide.
> For example, this bogus CLI command:
> {code}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:write-attribute(name=valid-connection-checker-properties, value=1)
> {code}
> Produces this in the server log:
> {code}
> 15:46:42,167 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS")
> ]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:100) [jboss-dmr-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:384) [jboss-dmr-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.as.controller.MapAttributeDefinition.convertParameterExpressions(MapAttributeDefinition.java:252) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2]
> at org.jboss.as.controller.AttributeDefinition.validateAndSet(AttributeDefinition.java:439) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2]
> at org.jboss.as.controller.AbstractWriteAttributeHandler.execute(AbstractWriteAttributeHandler.java:88) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2]
> at org.jboss.as.controller.operations.global.WriteAttributeHandler.execute(WriteAttributeHandler.java:98) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2]
> {code}
> There should be nothing in the server log at all for that error; the validator should have caught it and generated an appropriate failure response to the client.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years