[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-11827:
----------------------------------
Description:
The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
*1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
*2) Writing the invalid value to the attribute should fail the management operation.*
* reported as WFLY-11830
Starting vanilla server:
{noformat}
09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{noformat}
Write operation:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
{noformat}
...
09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
...
{noformat}
was:
The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
*1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
*2) Writing the invalid value to the attribute should fail the management operation.* - reported as WFLY-11830
Starting vanilla server:
{noformat}
09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{noformat}
Write operation:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
{noformat}
...
09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
...
{noformat}
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Petr Kremensky
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> * reported as WFLY-11830
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11830) Writing an invalid operation to pooled-connection-factory's transaction attribute should fail the mgmt operation
by Petr Kremensky (Jira)
Petr Kremensky created WFLY-11830:
-------------------------------------
Summary: Writing an invalid operation to pooled-connection-factory's transaction attribute should fail the mgmt operation
Key: WFLY-11830
URL: https://issues.jboss.org/browse/WFLY-11830
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 16.0.0.Final
Reporter: Petr Kremensky
Assignee: ehsavoie Hugonnet
Current behaviour:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
10:26:37,062 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
The management operation should fail in this case, and "Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied." message should be part of failure description instead.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-11827:
---------------------------------------
I'll file a separate issue for the other problem (success of invalid mgmt operation).
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Chao Wang
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky edited comment on WFLY-11827 at 3/11/19 5:18 AM:
----------------------------------------------------------------
I've submit an MR for fixing the problem of validation where the attribute value is 'xa'. Not sure about the other part of the issue.
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=asd)
10:16:58,115 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value asd for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
[~soul2zimate] this behaviour is imho wrong, wdyt?
was (Author: pkremens):
I've submit an MR for fixing the problem of validation where the attribute value is 'xa'. Not sure about the other part of the issue.
[~soul2zimate]
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=asd)
10:16:58,115 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value asd for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
This behaviour is imho wrong,
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Chao Wang
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-11827:
---------------------------------------
I've submit an MR for fixing the problem of validation where the attribute value is 'xa'. Not sure about the other part of the issue.
[~soul2zimate]
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=asd)
10:16:58,115 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value asd for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
This behaviour is imho wrong,
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Chao Wang
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3715) Zipkiemodule nullpointerexception
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3715?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-3715:
----------------------------------
Sprint: 2019 Week 11-13 (was: 2019 Week 08-10)
> Zipkiemodule nullpointerexception
> ---------------------------------
>
> Key: DROOLS-3715
> URL: https://issues.jboss.org/browse/DROOLS-3715
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.16.0.Final, 7.17.0.Final
> Reporter: Łukasz Szmolke
> Assignee: Tibor Zimányi
> Priority: Major
>
> o During ZipKieModule loading in “org.drools.compiler.kie.builder.impl.ZipKieModule:142” nullpointerexception is thrown:
>
> urlPath = urlPath.substring( urlPath.lastIndexOf( '!' ) + 1 );
> ArrayList<ZipEntry> entries = new ArrayList<>();
> // read jar file from uber-jar
> InputStream in = this.getClass().getResourceAsStream(urlPath); // nullpointerexception
>
> For example full UrlPath on windows to internal .jar is:
> C:\Users\xbbnv0c\IdeaProjects\ais-data-exchange\data-exchange-app\target\data-exchange-app-1.0.1-SNAPSHOT.jar!\BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar
> So the result of this first line will be:
> \BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar
> It will be perfect, but during accessing internal resource file separator should be “/” not “\”. So InputStream in = null.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months