[JBoss JIRA] (JGRP-2294) ForkProtocolStack ignores UnknownForkHandler for message batches
by Dan Berindei (JIRA)
Dan Berindei created JGRP-2294:
----------------------------------
Summary: ForkProtocolStack ignores UnknownForkHandler for message batches
Key: JGRP-2294
URL: https://issues.jboss.org/browse/JGRP-2294
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.13
Reporter: Dan Berindei
Assignee: Bela Ban
{{ForkProtocolStack.up(MessageBatch)}} discards messages if it doesn't the fork channel id isn't registered and they are part of a batch:
{code:java}
log.debug("fork-channel for id=%s not found; discarding message", fork_channel_id);
{code}
I believe the check should also be enhanced to invoke the {{UnknownForkHandler}} if the {{ForkChannel}} is registered but is not yet connected. Otherwise messages that arrive after the {{ForkChannel}} registers itself in the constructor and before our {{JGroupsTransport}} registers itself as an {{UpHandler}} with the {{ForkChannel}} will also be discarded.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Description:
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code}
was:
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code}
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Workaround Description:
# Add custom load metric module as a resource to {{org.wildfly.extension.mod_cluster}} module: {code:xml}
<resources>
<resource-root path="mod_cluster-custom-metric.jar"/>
<resource-root path="wildfly-mod_cluster-extension-[version].jar"/>
</resources>
{code}
# Add {{<module name="org.jboss.as.server"/>}} as a dependency to {{org.wildfly.extension.mod_cluster}} module
# Restart server
was:
# Add custom load metric module as a resource to {{org.wildfly.extension.mod_cluster}} module: {code}
<resources>
<resource-root path="mod_cluster-custom-metric.jar"/>
<resource-root path="wildfly-mod_cluster-extension-[version].jar"/>
</resources>
{code}
# Add {{<module name="org.jboss.as.server"/>}} as a dependency to {{org.wildfly.extension.mod_cluster}} module
# Restart server
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Workaround Description:
# Add custom load metric module as a resource to {{org.wildfly.extension.mod_cluster}} module: {code}
<resources>
<resource-root path="mod_cluster-custom-metric.jar"/>
<resource-root path="wildfly-mod_cluster-extension-[version].jar"/>
</resources>
{code}
# Add {{<module name="org.jboss.as.server"/>}} as a dependency to {{org.wildfly.extension.mod_cluster}} module
# Restart server
was:
# Add custom load metric module as a resource to {{org.wildfly.extension.mod_cluster}} module
# Add {{<module name="org.jboss.as.server"/>}} as a dependency to {{org.wildfly.extension.mod_cluster}} module
# Restart server
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Workaround Description:
# Add custom load metric module as a resource to {{org.wildfly.extension.mod_cluster}} module
# Add {{<module name="org.jboss.as.server"/>}} as a dependency to {{org.wildfly.extension.mod_cluster}} module
# Restart server
Workaround: Workaround Exists
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11027) [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-11027?page=com.atlassian.jira.plugin... ]
Miroslav Novak closed WFLY-11027.
---------------------------------
Fix Version/s: 14.0.0.Final
Resolution: Cannot Reproduce
After more than 150x runs I cannot reproduce this issue again with WF14. Closing.
> [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-11027
> URL: https://issues.jboss.org/browse/WFLY-11027
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Fix For: 14.0.0.Final
>
>
> There undelivered/lost messages in sceario where MDB is connected to remote Artemis cluster in which nodes are killed and restarted. Issue is intermittent.
> Test Scenario:
> * start cluster containing node 1 and 3 with deployed inQueue and outQueue
> ** JDBC store with Oracle 12c is used
> * start node 2 and 4
> * producer sends 5000 small and large messages to inQueue to node-1
> * wait for producer to finish
> * deploy MDBs to node-2 and node-4 which read messages from inQueue and sends them to outQueue in XA transactions
> * kill and start following nodes in this sequence: 1,3,1,3,1
> * wait until all messages are processed
> * start Consumer which consumes messages form outQueue
> * Check that number of messages sent to InQueue and received from OutQueue is the same
> Result:
> 7 messages were missing in OutQueue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Lowry Cui (JIRA)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Lowry Cui edited comment on ELY-1525 at 9/19/18 1:30 AM:
---------------------------------------------------------
I also got same issue with keycloak-saml-wildfly-elytron-adapter, and I reported a bug in Keycloak community. please see https://issues.jboss.org/browse/KEYCLOAK-8318
was (Author: laocui):
I also got same issue with keycloak-saml-wildfly-elytron-adapter, and I report a bug in Keycloak community. please see https://issues.jboss.org/browse/KEYCLOAK-8318
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Lowry Cui (JIRA)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Lowry Cui edited comment on ELY-1525 at 9/18/18 11:04 PM:
----------------------------------------------------------
I also got same issue with keycloak-saml-wildfly-elytron-adapter, and I report a bug in Keycloak community. please see https://issues.jboss.org/browse/KEYCLOAK-8318
was (Author: laocui):
I also get same issue with keycloak-saml-wildfly-elytron-adapter, please see https://issues.jboss.org/browse/KEYCLOAK-8318
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Lowry Cui (JIRA)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Lowry Cui edited comment on ELY-1525 at 9/18/18 11:03 PM:
----------------------------------------------------------
I also get same issue with keycloak-saml-wildfly-elytron-adapter, please see https://issues.jboss.org/browse/KEYCLOAK-8318
was (Author: laocui):
I also get same issue, please see https://issues.jboss.org/browse/KEYCLOAK-8318
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months