[JBoss JIRA] (WFLY-10067) Failover does not work with HTTP conncetors/acceptors
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10067?page=com.atlassian.jira.plugin... ]
Erich Duda updated WFLY-10067:
------------------------------
Description:
Failover does not work with HTTP connectors/acceptors.
*Scenario:*
# There are two Wildfly servers configured as Live-Backup pair
# There is one JMS producer and one JMS receiver which sends/receives messages
# Live server is several times killed and restarted.
*Expectation:* Always when the Live server is killed or restarted, clients do failover or failback.
*Reality*: Sometimes happens that clients don't do failover.
*Users impact:* One of basics feature of HA, failover, does not work properly.
*Blocker* priority was set because this is regression against previous releases of Wildfly.
*Detail description of issue*
In the trace logs it can be seen that clients send HTTP handshake request to active backup, but the handshake fails. All checks (and logs) say that the backup is active in this time period. I tried to run the test with Netty connectors/acceptors and I didn't see this issue.
{code:title=Backup log}
07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=55, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=56, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485068, b=2147485067]
07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485076, b=2147485075]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484450, b=2147484449]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485072, b=2147485071]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484454, b=2147484453]
07:52:47,866 WARN [org.apache.activemq.artemis.core.client] (activemq-discovery-group-thread-dg-group1) AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=0dee81c9-2d9d-11e8-ba3f-cc3d825f79a4
07:52:47,867 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221007: Server is now live
{code}
{code:title=Clients log}
07:52:49,274 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
07:52:49,274 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=8080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1081] Trying backup config = TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:447] Connector NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] using native epoll
07:52:49,275 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET HTTP/1.1
host: localhost
upgrade: activemq-remoting
connection: upgrade
activemqServerName: default
httpUpgradeEndpoint: acceptor
Sec-ActiveMQRemoting-Key: QWV3bCfgh75NjWH3pZV5Ew==
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:601] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to localhost:9080
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
07:52:49,276 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET HTTP/1.1
host: localhost
upgrade: activemq-remoting
connection: upgrade
activemqServerName: default
httpUpgradeEndpoint: acceptor
Sec-ActiveMQRemoting-Key: P9xBwRk1eZP5QjDWjqYuIg==
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Connection: keep-alive
Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
Content-Length: 2426
Content-Type: text/html
Accept-Ranges: bytes
Date: Thu, 22 Mar 2018 06:52:49 GMT
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Connection: keep-alive
Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
Content-Length: 2426
Content-Type: text/html
Accept-Ranges: bytes
Date: Thu, 22 Mar 2018 06:52:49 GMT
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
07:52:49,277 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
{code}
was:
Failover does not work with HTTP connectors/acceptors.
*Scenario:*
# There are two Wildfly servers configured as Live-Backup pair
# There is one JMS producer and one JMS receiver which sends/receives messages
# Live server is several times killed and restarted.
*Expectation:* Always when the Live server is killed or restarted, clients do failover or failback.
*Reality*: Sometimes happens that clients don't do failover.
*Users impact:* One of basics feature of HA, failover, does not work properly.
*Detail description of issue*
In the trace logs it can be seen that clients send HTTP handshake request to active backup, but the handshake fails. All checks (and logs) say that the backup is active in this time period. I tried to run the test with Netty connectors/acceptors and I didn't see this issue.
{code:title=Backup log}
07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=55, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=56, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485068, b=2147485067]
07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485076, b=2147485075]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484450, b=2147484449]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485072, b=2147485071]
07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484454, b=2147484453]
07:52:47,866 WARN [org.apache.activemq.artemis.core.client] (activemq-discovery-group-thread-dg-group1) AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=0dee81c9-2d9d-11e8-ba3f-cc3d825f79a4
07:52:47,867 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221007: Server is now live
{code}
{code:title=Clients log}
07:52:49,274 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
07:52:49,274 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=8080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1081] Trying backup config = TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:447] Connector NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] using native epoll
07:52:49,275 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET HTTP/1.1
host: localhost
upgrade: activemq-remoting
connection: upgrade
activemqServerName: default
httpUpgradeEndpoint: acceptor
Sec-ActiveMQRemoting-Key: QWV3bCfgh75NjWH3pZV5Ew==
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:601] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to localhost:9080
07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
07:52:49,276 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET HTTP/1.1
host: localhost
upgrade: activemq-remoting
connection: upgrade
activemqServerName: default
httpUpgradeEndpoint: acceptor
Sec-ActiveMQRemoting-Key: P9xBwRk1eZP5QjDWjqYuIg==
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Connection: keep-alive
Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
Content-Length: 2426
Content-Type: text/html
Accept-Ranges: bytes
Date: Thu, 22 Mar 2018 06:52:49 GMT
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Connection: keep-alive
Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
Content-Length: 2426
Content-Type: text/html
Accept-Ranges: bytes
Date: Thu, 22 Mar 2018 06:52:49 GMT
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
07:52:49,277 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
{code}
> Failover does not work with HTTP conncetors/acceptors
> -----------------------------------------------------
>
> Key: WFLY-10067
> URL: https://issues.jboss.org/browse/WFLY-10067
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: feature-branch-blocker
> Attachments: clients.log, server1.log, server2.log, test.log
>
>
> Failover does not work with HTTP connectors/acceptors.
> *Scenario:*
> # There are two Wildfly servers configured as Live-Backup pair
> # There is one JMS producer and one JMS receiver which sends/receives messages
> # Live server is several times killed and restarted.
> *Expectation:* Always when the Live server is killed or restarted, clients do failover or failback.
> *Reality*: Sometimes happens that clients don't do failover.
> *Users impact:* One of basics feature of HA, failover, does not work properly.
> *Blocker* priority was set because this is regression against previous releases of Wildfly.
> *Detail description of issue*
> In the trace logs it can be seen that clients send HTTP handshake request to active backup, but the handshake fails. All checks (and logs) say that the backup is active in this time period. I tried to run the test with Netty connectors/acceptors and I didn't see this issue.
> {code:title=Backup log}
> 07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=55, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
> 07:52:47,856 WARN [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@1f01f347)) AMQ222029: Could not locate page transaction 3 995, ignoring message on position PagePositionImpl [pageNr=2, messageNr=56, recordID=-1] on address=jms.queue.testQueue queue=jms.queue.testQueue
> 07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485068, b=2147485067]
> 07:52:47,863 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485076, b=2147485075]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484450, b=2147484449]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147485072, b=2147485071]
> 07:52:47,864 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221005: Deleting pending large message as it was not completed: Pair[a=2147484454, b=2147484453]
> 07:52:47,866 WARN [org.apache.activemq.artemis.core.client] (activemq-discovery-group-thread-dg-group1) AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=0dee81c9-2d9d-11e8-ba3f-cc3d825f79a4
> 07:52:47,867 INFO [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=null) AMQ221007: Server is now live
> {code}
> {code:title=Clients log}
> 07:52:49,274 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
> 07:52:49,274 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=8080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1081] Trying backup config = TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:447] Connector NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] using native epoll
> 07:52:49,275 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
> GET HTTP/1.1
> host: localhost
> upgrade: activemq-remoting
> connection: upgrade
> activemqServerName: default
> httpUpgradeEndpoint: acceptor
> Sec-ActiveMQRemoting-Key: QWV3bCfgh75NjWH3pZV5Ew==
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:601] AMQ211002: Started EPOLL Netty Connector version 4.1.16.Final to localhost:9080
> 07:52:49,275 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:726] Remote destination: localhost/127.0.0.1:9080
> 07:52:49,276 Thread-79 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector:797] Sending HTTP request DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
> GET HTTP/1.1
> host: localhost
> upgrade: activemq-remoting
> connection: upgrade
> activemqServerName: default
> httpUpgradeEndpoint: acceptor
> Sec-ActiveMQRemoting-Key: P9xBwRk1eZP5QjDWjqYuIg==
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
> HTTP/1.1 200 OK
> Connection: keep-alive
> Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
> Content-Length: 2426
> Content-Type: text/html
> Accept-Ranges: bytes
> Date: Thu, 22 Mar 2018 06:52:49 GMT
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
> HTTP/1.1 200 OK
> Connection: keep-alive
> Last-Modified: Thu, 22 Mar 2018 06:47:03 GMT
> Content-Length: 2426
> Content-Type: text/html
> Accept-Ranges: bytes
> Date: Thu, 22 Mar 2018 06:52:49 GMT
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:876] Received msg=DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
> 07:52:49,276 Thread-2 (ActiveMQ-client-netty-threads) DEBUG [org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector$HttpUpgradeHandler:903] AMQ214023: HTTP Handshake failed, received DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 829, cap: 829/829, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1024, widx: 1024, cap: 1024)), decoderResult: success)
> 07:52:49,277 Thread-80 (ActiveMQ-client-global-threads) DEBUG [org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl:1040] Connector towards NettyConnector [host=localhost, port=9080, httpEnabled=false, httpUpgradeEnabled=true, useServlet=false, servletPath=/messaging/ActiveMQServlet, sslEnabled=false, useNio=true, activemqServerName=default, httpUpgradeEndpoint=acceptor] failed
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
3 months
[JBoss JIRA] (WFLY-12135) error deploying web service without http-listener (only https-listener)
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-12135?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-12135:
---------------------------------------
This is actually reported downstream as JBEAP-14818 -- linked now. The whole exception is:
{noformat}
19:01:37,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."helloworld-ws.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-ws.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-ws.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: WFLYUT0063: Could not find the port number listening for protocol HTTP/1.1
at org.wildfly.extension.undertow.WebServerService.getPort(WebServerService.java:68)
at org.jboss.as.webservices.config.WebServerInfoImpl.getPort(WebServerInfoImpl.java:36)
at org.jboss.ws.common.management.AbstractServerConfig.getConnectorPort(AbstractServerConfig.java:328)
at org.jboss.ws.common.management.AbstractServerConfig.getWebServicePort(AbstractServerConfig.java:237)
at org.jboss.wsf.spi.metadata.config.SOAPAddressRewriteMetadata.getWebServicePort(SOAPAddressRewriteMetadata.java:66)
at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getPortValue(EndpointAddressDeploymentAspect.java:224)
at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getValue(EndpointAddressDeploymentAspect.java:217)
at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect.start(EndpointAddressDeploymentAspect.java:84)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
... 8 more
{noformat}
easily reproducible by removing http listener and deploying quickstart with WS.
{noformat}
/subsystem=undertow/server=default-server/http-listener=default:remove
deploy ~/git/wildfly-quickstarts/helloworld-ws/target/helloworld-ws.war
{noformat}
The part of the problem is mismatch between how ws {{org.jboss.ws.common.management.AbstractServerConfig#getConnectorPort}} are trying to use the {{org.jboss.as.webservices.config.WebServerInfoImpl}}. The undertow implementation {{org.wildfly.extension.undertow.WebServerService#getPort}} is designed to consume values http/https/ajp rather than full protocol name.
Moreover, I don't see a reason why WS are not defaulting to https when http is unavailable.
> error deploying web service without http-listener (only https-listener)
> ------------------------------------------------------------------------
>
> Key: WFLY-12135
> URL: https://issues.jboss.org/browse/WFLY-12135
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 17.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Jim Ma
> Priority: Major
>
> Deploying a application with only a https-listener (default http-listener was removed) gives error:
> Caused by: java.lang.IllegalStateException: WFLYUT0063: Could not find the port number listening for protocol HTTP/1.1
> at org.wildfly.extension.undertow.WebServerService.getPort(WebServerService.java:68)
> at org.jboss.as.webservices.config.WebServerInfoImpl.getPort(WebServerInfoImpl.java:36)
> at org.jboss.ws.common.management.AbstractServerConfig.getConnectorPort(AbstractServerConfig.java:328)
> at org.jboss.ws.common.management.AbstractServerConfig.getWebServicePort(AbstractServerConfig.java:237)
> at org.jboss.wsf.spi.metadata.config.SOAPAddressRewriteMetadata.getWebServicePort(SOAPAddressRewriteMetadata.java:66)
> at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getPortValue(EndpointAddressDeploymentAspect.java:224)
> at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getValue(EndpointAddressDeploymentAspect.java:217)
> at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect.start(EndpointAddressDeploymentAspect.java:84)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> A workaround is to use webservices configuration to define modify-wsdl-address and wsdl-port (for wsdl soap address rewriting) or jboss-webservices.xml to define wsdl.soapAddress.rewrite.wsdl-port.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
3 months, 2 weeks
[JBoss JIRA] Created: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method
by Tom Fennelly (JIRA)
Need support for notification generatoin from within ActionProcessor.process method
-----------------------------------------------------------------------------------
Key: JBESB-193
URL: http://jira.jboss.com/jira/browse/JBESB-193
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.1
In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message.
For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener).
The getOk and getErro methods can then be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 months
[JBoss JIRA] Created: (JGRP-1257) ENCRYPT protocol UnrecoverableKeyException: Given final block not properly padded
by Andres Garcia Garcia (JIRA)
ENCRYPT protocol UnrecoverableKeyException: Given final block not properly padded
---------------------------------------------------------------------------------
Key: JGRP-1257
URL: https://jira.jboss.org/browse/JGRP-1257
Project: JGroups
Issue Type: Bug
Affects Versions: 2.11, 2.8, 2.7
Environment: Windows XP SP3, Java 1.6
Reporter: Andres Garcia Garcia
Assignee: Bela Ban
Recently I updated my jgroups version from 2.4.x to 2.11. Suddenly my applications thrown this exception.
org.jgroups.ChannelException: unable to setup the protocol stack: Given final block not properly padded
at org.jgroups.JChannel.init(JChannel.java:1574)
at org.jgroups.JChannel.<init>(JChannel.java:257)
at org.jgroups.JChannel.<init>(JChannel.java:240)
at org.jgroups.demos.Draw.<init>(Draw.java:52)
at org.jgroups.demos.Draw.main(Draw.java:141)
Caused by: java.security.UnrecoverableKeyException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_z.a(DashoA13*..)
at com.sun.crypto.provider.JceKeyStore.engineGetKey(DashoA13*..)
at java.security.KeyStore.getKey(Unknown Source)
at org.jgroups.protocols.ENCRYPT.initConfiguredKey(ENCRYPT.java:269)
at org.jgroups.protocols.ENCRYPT.init(ENCRYPT.java:231)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:641)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:468)
at org.jgroups.JChannel.init(JChannel.java:1570)
... 4 more
The ENCRYPT protocol config is
<ENCRYPT sym_init="448"
sym_algorithm="Blowfish"
encrypt_entire_message="true"
key_store_name="cloudencrypt.keystore"
store_password="password"
alias="test"/>
I tested the same code with different versions. 2.6.15 GA is the last working version, and every version I tested from 2.7 GA to 2.11 GA throw the same exception. I made a little use case with it. Maybe I am missing something?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 months, 1 week
[JBoss JIRA] Created: (AS7-782) Hudson/Jenkins won't work in AS7b3
by Fred Bricon (JIRA)
Hudson/Jenkins won't work in AS7b3
----------------------------------
Key: AS7-782
URL: https://issues.jboss.org/browse/AS7-782
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Fedora 14, JDK 1.6.0_24, JBoss AS7 beta 3
Reporter: Fred Bricon
Assignee: Jason Greene
After patching AS7b3 with the latest jboss-vfs from github/master and
deploying hudson ( http://search.maven.org/remotecontent?filepath=org/jvnet/hudson/main/huds...) or jenkins on AS7, an exception is thrown when accessing the homepage (or any page) :
{noformat}
17:39:33,429 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/hudson-war-2.0.0].[Stapler]] (http-localhost.localdomain-127.0.0.1-8080-2) "Servlet.service()" pour la servlet Stapler a généré une exception: java.net.MalformedURLException: unknown protocol: jndi
at java.net.URL.<init>(URL.java:574) [:1.6.0_24]
at java.net.URL.<init>(URL.java:464) [:1.6.0_24]
at java.net.URL.<init>(URL.java:413) [:1.6.0_24]
at org.kohsuke.stapler.Stapler.selectResourceByLocale(Stapler.java:227) [stapler-1.155.jar:]
at org.kohsuke.stapler.Stapler.openResourcePathByLocale(Stapler.java:203) [stapler-1.155.jar:]
at org.kohsuke.stapler.Stapler.service(Stapler.java:145) [stapler-1.155.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) [hudson-core-2.0.0.jar:]
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:388) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:658) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
{noformat}
I first mentioned this issur on irc (see http://echelog.matzon.dk/logs/browse/jboss-as7/1305151200 [13:42:43] -> [13:48:58])
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 months, 1 week
[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3330:
--------------------------------
Description:
Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Rationale:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
was:
Creating this jira to investigate if it would be possible to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Rationale:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
> DMN Properties panel - Style menu
> ---------------------------------
>
> Key: DROOLS-3330
> URL: https://issues.jboss.org/browse/DROOLS-3330
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Priority: Optional
> Labels: UX, UXTeam, drools-tools
> Attachments: styles.png
>
>
> Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
> Rationale:
> * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
> * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
> * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 months, 1 week
[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 months, 2 weeks
[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10796:
-----------------------------
Description:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
was:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present.
> Warning about JSF version 'NONE' is shown in logs
> --------------------------------------------------
>
> Key: WFLY-10796
> URL: https://issues.jboss.org/browse/WFLY-10796
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
>
> Following warning is shown in log upon server start:
> {code}
> 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
> {code}
> Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 months, 1 week
[JBoss JIRA] (DROOLS-4849) SudokuExample cannot solve hard samples any more in Drools 7
by Didier Loiseau (Jira)
Didier Loiseau created DROOLS-4849:
--------------------------------------
Summary: SudokuExample cannot solve hard samples any more in Drools 7
Key: DROOLS-4849
URL: https://issues.redhat.com/browse/DROOLS-4849
Project: Drools
Issue Type: Bug
Affects Versions: 7.30.0.Final
Reporter: Didier Loiseau
Assignee: Mario Fusco
It appears {{SudokuExample}} is capable to resolve the Simple and Medium samples, but none of the Hard ones. They resolve a few cells but end with
{quote}
Sorry - can't solve this grid.
{quote}
in the console.
With explain = true, I can see that the "single" and "hidden single" rules fire (not always both, depends on the puzzle), but clearly when it stops, at least the latter should still fire for some cells.
There is also a small bug in the code, which is that the {{unsolvable}} flag is not reset during setup, so when you get the above error you also get it for any other example you solve afterwards.
I have checked with Drools 6.5.0.Final (checked out the examples from GitHub) and the solver works fine. The Sudoku example appears to be mostly the same though.
I am running the examples with Java 8 from IntelliJ or command line, if that matters. I tested this on 2 different machines.
It is a bit unfortunate because it is the first example in the GUI.
Full console output for sample Hard 1:
{code}
12:14:28.256 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.notifyKieModuleFound:133 - Found kmodule: file:/C:/Users/Public/Documents/projects/drools/drools-examples/target/classes/META-INF/kmodule.xml
12:14:30.424 [main] WARN o.d.c.k.b.impl.ClasspathKieProject.getPomPropertiesFromFileSystem:322 - Unable to find pom.properties in /C:/Users/Public/Documents/projects/drools/drools-examples/target/classes
12:14:30.475 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.generatePomPropertiesFromPom:354 - Recursed up folders, found and used pom.xml C:\Users\Public\Documents\projects\drools\drools-examples\pom.xml
12:14:42.619 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintCave.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
12:14:42.632 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintSensor.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
12:14:42.687 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/ui.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
Validation complete.
Col: 0 Col: 1 Col: 2 Col: 3 Col: 4 Col: 5 Col: 6 Col: 7 Col: 8
Row 0: 2 4 7 9 2 4 6 4 67 9 23 6 9 --- 5 --- --- 1 --- 3 67 9 --- 8 --- 4 67
Row 1: 12 7 9 --- 8 --- 1 67 9 23 6 9 --- 4 --- 23 6 1 3 67 9 3 67 9 --- 5 ---
Row 2: 1 4 9 1 456 --- 3 --- 6 89 --- 7 --- 6 8 --- 2 --- 4 6 9 1 4 6
Row 3: 1234 1234 1 4 1 5 8 --- 6 --- 5 78 5 7 45 7 --- 9 ---
Row 4: --- 6 --- --- 7 --- --- 5 --- --- 4 --- --- 2 --- --- 9 --- --- 8 --- --- 1 --- --- 3 ---
Row 5: --- 8 --- 12 4 1 4 9 1 5 --- 3 --- 5 7 567 4567 2 4 67
Row 6: 1 3 7 1 3 6 --- 2 --- 3 56 --- 8 --- 3 56 --- 4 --- 3 567 9 1 67
Row 7: --- 5 --- 1 34 6 1 4 678 3 6 --- 9 --- 34 6 1 3 67 --- 2 --- 1 678
Row 8: 34 --- 9 --- 4 6 8 --- 7 --- --- 1 --- 23456 3 56 3 56 6 8
Sorry - can't solve this grid.
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
8 months, 1 week
[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension
by Florian Sailer (Jira)
Florian Sailer created WFLY-12461:
-------------------------------------
Summary: Can't use smallrye-health without weld extension
Key: WFLY-12461
URL: https://issues.jboss.org/browse/WFLY-12461
Project: WildFly
Issue Type: Bug
Components: MP Health
Affects Versions: 17.0.1.Final
Reporter: Florian Sailer
Assignee: Jeff Mesnil
Since this commit in the smallrye implementation it was possible to use smallrye without CDI.
https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29...
I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld.
I am getting the following exception while starting:
14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.weld; There are no known registration points which can provide this capability.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
1 year, 1 month
[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3944:
--------------------------------------
Sprint: 2019 Week 23-25
> DMN Editor: Data type usability study
> -------------------------------------
>
> Key: DROOLS-3944
> URL: https://issues.jboss.org/browse/DROOLS-3944
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Environment: Version 7.4
> Reporter: Elizabeth Clayton
> Assignee: Sarahjane Clark
> Priority: Major
> Labels: UX, UXTeam, Usability, drools-tools
>
> Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
> GOALS: Access the Data Type editor in terms of productivity and usability.
> * Ease of use when creating a complex type (concern: minimizing the mouse usage.)
> * Ease of use when saving a basic data type (e.g. age: number)
> * Discoverability of actions in the kebab menu, especially, insert nested, delete.
> * Ease of use/accuracy: Type-ahead of the data type selector.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
1 year, 9 months
[JBoss JIRA] (WFLY-13026) Upgrade jboss-ejb-client to 4.0.29.Final
by Tomasz Adamski (Jira)
[ https://issues.redhat.com/browse/WFLY-13026?page=com.atlassian.jira.plugi... ]
Tomasz Adamski updated WFLY-13026:
----------------------------------
Description:
[http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717|Prep 4.0.28.Final]
[http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260|Next is 4.0.29.Final]
[http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d|[EJBCLIENT-364] Standalone EJB-over-HTTP invocation]
[http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e|Merge pull request #446 from tadamski/EJBCLIENT-364]
[http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3|[EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException]
[http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f|Merge pull request #450 from tadamski/EJBCLIENT-361]
[http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de|EJBClientInvocationContext: log exception on the first interceptor only]
[http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660|Prep 4.0.29.Final]
was:
<li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
<li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
<li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
<li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
<li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
<li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
> Upgrade jboss-ejb-client to 4.0.29.Final
> ----------------------------------------
>
> Key: WFLY-13026
> URL: https://issues.redhat.com/browse/WFLY-13026
> Project: WildFly
> Issue Type: Component Upgrade
> Components: EJB
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Major
>
> [http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717|Prep 4.0.28.Final]
> [http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260|Next is 4.0.29.Final]
> [http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d|[EJBCLIENT-364] Standalone EJB-over-HTTP invocation]
> [http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e|Merge pull request #446 from tadamski/EJBCLIENT-364]
> [http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3|[EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException]
> [http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f|Merge pull request #450 from tadamski/EJBCLIENT-361]
> [http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de|EJBClientInvocationContext: log exception on the first interceptor only]
> [http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660|Prep 4.0.29.Final]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13026) Upgrade jboss-ejb-client to 4.0.29.Final
by Tomasz Adamski (Jira)
[ https://issues.redhat.com/browse/WFLY-13026?page=com.atlassian.jira.plugi... ]
Tomasz Adamski updated WFLY-13026:
----------------------------------
Description:
<li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
<li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
<li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
<li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
<li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
<li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
> Upgrade jboss-ejb-client to 4.0.29.Final
> ----------------------------------------
>
> Key: WFLY-13026
> URL: https://issues.redhat.com/browse/WFLY-13026
> Project: WildFly
> Issue Type: Component Upgrade
> Components: EJB
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Major
>
> <li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
> <li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
> <li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
> <li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
> <li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
> <li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
> <li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
> <li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-255:
--------------------------------------
I can see where it's an RFE for sure then. When I filed this I wasn't quite sure of the intentions and I likely should have asked, but that was almost 6 years ago so I can't really remember all the details :)
I do recall the changes when I looked back in October were not simple. I was hoping it was as simple as just looking if those were set with {{boot-time=true}} and allowing them. That was a rather naive hope though in hindsight.
I'll go ahead and change this to a feature request. There may not be a new API needed and nothing user facing should be changed with the exception of documentation.
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-255:
---------------------------------
Issue Type: Feature Request (was: Bug)
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-255:
-----------------------------------------
It was intentional. It's just a limitation because we can't do everything and chose not to implement support for this.
Perhaps it's just an Enhancement instead of a Feature Request, if there is no new API, just that existing resources will accept values they would not have before.
But, I suspect that is not the case, or if it is the case the appropriate work to do it correctly, i.e. analysis, test coverage and docs is basically the same as a feature so might as well handle it as such.
For example, system properties can be set at numerous levels, but for these properties some levels likely are wrong. That all has to be analyzed and documented and perhaps it means the configuration style to use for this is not system properties but is something else that we can properly restrict.
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4996) NotSerializableException is thrown at the serialization of KieBase
by Róbert István (Jira)
Róbert István created DROOLS-4996:
-------------------------------------
Summary: NotSerializableException is thrown at the serialization of KieBase
Key: DROOLS-4996
URL: https://issues.redhat.com/browse/DROOLS-4996
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.25.0.Final
Reporter: Róbert István
Assignee: Mario Fusco
NotSerializableException is thrown at the serialization of KieBase when the 'when' part of a rule contains a query call.
InterceptorMap static subclass doesn't implement the Serializable interface.
When I corrected the source of MVELCompilationUnit and rebuild the drools-core.jar, the issue disappeared.
Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.drools.core.base.mvel.MVELCompilationUnit$InterceptorMap
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1576)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2286)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2210)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2286)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2210)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.rule.QueryArgument$Expression.readExternal(QueryArgument.java:145)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1974)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1566)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.rule.QueryElement.readExternal(QueryElement.java:75)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at java.util.ArrayList.readObject(ArrayList.java:797)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1170)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2177)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.rule.GroupElement.readExternal(GroupElement.java:64)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.definitions.rule.impl.RuleImpl.readExternal(RuleImpl.java:209)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.rule.JavaDialectRuntimeData.readExternal(JavaDialectRuntimeData.java:195)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at java.util.HashMap.readObject(HashMap.java:1412)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1170)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2177)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.rule.DialectRuntimeRegistry.readExternal(DialectRuntimeRegistry.java:60)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.definitions.impl.KnowledgePackageImpl.readExternal(KnowledgePackageImpl.java:306)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2117)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2066)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at java.util.HashMap.readObject(HashMap.java:1412)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1170)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2177)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
at org.drools.core.impl.KnowledgeBaseImpl.readExternal(KnowledgeBaseImpl.java:442)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1418)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation$MethodCallResultProducer.apply(EJBClientChannel.java:1208)
... 64 more
Caused by: java.io.NotSerializableException: org.drools.core.base.mvel.MVELCompilationUnit$InterceptorMap
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.rule.QueryArgument$Expression.writeExternal(QueryArgument.java:138)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1378)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.rule.QueryElement.writeExternal(QueryElement.java:64)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at java.util.ArrayList.writeObject(ArrayList.java:762)
at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.rule.GroupElement.writeExternal(GroupElement.java:69)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.definitions.rule.impl.RuleImpl.writeExternal(RuleImpl.java:169)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.rule.JavaDialectRuntimeData.writeExternal(JavaDialectRuntimeData.java:132)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at java.util.HashMap.internalWriteEntries(HashMap.java:1785)
at java.util.HashMap.writeObject(HashMap.java:1362)
at sun.reflect.GeneratedMethodAccessor1251.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.rule.DialectRuntimeRegistry.writeExternal(DialectRuntimeRegistry.java:49)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.definitions.impl.KnowledgePackageImpl.writeExternal(KnowledgePackageImpl.java:257)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at java.util.HashMap.internalWriteEntries(HashMap.java:1785)
at java.util.HashMap.writeObject(HashMap.java:1362)
at sun.reflect.GeneratedMethodAccessor1251.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at org.drools.core.impl.KnowledgeBaseImpl.writeExternal(KnowledgeBaseImpl.java:548)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:908)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
at org.jboss.ejb.protocol.remote.EJBServerChannel$RemotingInvocationRequest$1.writeInvocationResult(EJBServerChannel.java:956)
at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: an exception which occurred:
in object of type org.drools.core.impl.KnowledgeBaseImpl
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-255:
--------------------------------------
I'll try to think of a better title. I could go either way with it being a feature. I know when I had a look it wasn't a simple task to allow these properties to be defined as system properties. The issue there is no way to override these properties for a server within domain, but it can be done for standalone servers. It's been like this from the start. Maybe it's intentional and we can just accept in which case I'm completely fine with closing this issue.
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-255:
---------------------------------
Summary: jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command. (was: Boot time only system properties should not modify the runtime only the model)
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-255:
-----------------------------------------
The title of this JIRA doesn't match very well with the description.
The description sounds like a Feature Request.
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-4994:
--------------------------------------
Attachment: collection-infotip.png
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton commented on DROOLS-4994:
-------------------------------------------
[~adupliak] Here are mockups for two possible approaches to the first suggestion made, which could be a *short term* enhancements. Would need correct help text from [~stetson.robinson] or yourself.
!collection-inline.png|thumbnail!
!collection-infotip.png|thumbnail!
[~yamer] is working on some related issues in https://issues.redhat.com/browse/DROOLS-4972. I defer to [~yamer] and [~danielezonca] as to whether this will address the concern for the short term, or where you want me to look into a more comprehensive redesign of the widget. Thanks!
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-4994:
--------------------------------------
Attachment: collection-inline.png
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-4972:
------------------------------------
Assignee: Yeser Amer (was: Anna Dupliak)
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4972:
---------------------------------
Tester: Anna Dupliak (was: Jozef Marko)
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Anna Dupliak
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFLY-12093:
--------------------------------------
[~emmartins] I'm not really sure. I don't really know anything about this quickstart. I would assume not, but I honestly don't know.
> bug in tutorial "batch-processing" with column "End Time"
> ---------------------------------------------------------
>
> Key: WFLY-12093
> URL: https://issues.redhat.com/browse/WFLY-12093
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: batch-processing
> Reporter: Святослав Кремлёв
> Assignee: Eduardo Martins
> Priority: Major
> Attachments: 2019-05-18 23_16_51-Batch Processing.png
>
>
> in file
> org/jboss/as/quickstarts/batch/controller/JobData.java
> {code}
> public Date getEndTime() {
> endTime = new Date();
> return endTime.getTime() == 0 ? null : endTime;
> }
> {code}
> its returns current time every time, not the job endTime
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13046) ConcurrentModificationException authenticating JWT under load.
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-13046:
---------------------------------------
Summary: ConcurrentModificationException authenticating JWT under load.
Key: WFLY-13046
URL: https://issues.redhat.com/browse/WFLY-13046
Project: WildFly
Issue Type: Bug
Components: MP JWT, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 19.0.0.Beta2
I don't believe this is specifically related to JWT, however load testing to obtain some performance statistics has led to this ConcurrentModificationException.
As the Roles is HashMap backed by the time this stage is reached no modifications should be possible.
{noformat}
15:53:51,047 ERROR [io.undertow.request] (default task-302) UT005023: Exception handling request to /microprofile-jwt/rest/Sample/helloworld: java.util.ConcurrentModificationException
at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1553)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at org.wildfly.elytron.web.undertow.server.ElytronAccount.<init>(ElytronAccount.java:46)
at org.wildfly.elytron.web.undertow.server.ElytronAccount.<init>(ElytronAccount.java:50)
at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticationComplete(SecurityContextImpl.java:140)
at org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl.authenticate(ServletSecurityContextImpl.java:208)
at org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl.authenticate(ServletSecurityContextImpl.java:99)
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4995) Error popups when collection editor dialog is open
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4995:
------------------------------------
Summary: Error popups when collection editor dialog is open
Key: DROOLS-4995
URL: https://issues.redhat.com/browse/DROOLS-4995
Project: Drools
Issue Type: Bug
Components: Test Scenarios Editor
Affects Versions: 7.32.0.Final
Reporter: Anna Dupliak
Assignee: Yeser Amer
Attachments: overlapError.webm
The error popup overlaps with collection dialog editor wlile navigating to the filing cell and releasing focus again (without clicking)
See the video
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13045) EAT compatibility with OpenJ9
by Panagiotis Sotiropoulos (Jira)
Panagiotis Sotiropoulos created WFLY-13045:
----------------------------------------------
Summary: EAT compatibility with OpenJ9
Key: WFLY-13045
URL: https://issues.redhat.com/browse/WFLY-13045
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Panagiotis Sotiropoulos
Assignee: Panagiotis Sotiropoulos
Verify EAT compatibility with OpenJ9
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Yeray Borges edited comment on WFCORE-4822 at 1/31/20 9:00 AM:
---------------------------------------------------------------
I haven't checked, but my very vague idea is when we cancel a Job, CI could kick it off automatically again, and then if we are not faster enough pushing up the new commit, the new Job picks up the old one.
was (Author: yersan):
I haven't checked, but my very vague idea is when we cancel a Job, CI could kick it off automatically again, and then if we are not faster enough pushing up the new commit, the new Job picks up the latest commit.
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Yeray Borges commented on WFCORE-4822:
--------------------------------------
I haven't checked, but my very vague idea is when we cancel a Job, CI could kick it off automatically again, and then if we are not faster enough pushing up the new commit, the new Job picks up the latest commit.
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-4822:
------------------------------------------
So it looks like the job may have kicked off again before the merge branch was updated. I wonder if we would be better for CI to handle the actual merge.
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFLY-13044:
-----------------------------------------
[~flavia.rainone] Let me know if you would like me to take a look at this one, I suspect it is another case of a change moving to the Jakarta EE API.
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test project and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Description:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test project and the complete log in my environment.
With Wildfly 17 there are not error.
was:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test project and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Yeray Borges commented on WFCORE-4822:
--------------------------------------
GitHub PR Commit SHA:
commit d9c0a6b0682af1fa0d460046bf23f7c594a4572b https://github.com/wildfly/wildfly-core/pull/4073/commits/d9c0a6b0682af1f...
The executed jobs in CI show the picked up a different SHA https://ci.wildfly.org/viewLog.html?buildId=184253&buildTypeId=WFCorePRAg...
{noformat}
Merge b9f86e2c62b533845946b1bbddbed1f36fe5acda into d1e5dea240f3d34c31d9a5974eabc0d7e2a30d8a yersan(a)users.noreply.github.com 0 files d6754b1065c1 29 Jan 20 17:25
{noformat}
My local git relog shows both SHA, being the SHA of the executed jobs the commit before than the PR commit:
{noformat}
git reflog --no-abbrev --date=iso
d1e5dea240f3d34c31d9a5974eabc0d7e2a30d8a HEAD@{2020-01-29 22:19:27 +0000}: checkout: moving from WFCORE-4822 to master
d9c0a6b0682af1fa0d460046bf23f7c594a4572b HEAD@{2020-01-29 17:36:11 +0000}: commit (amend): [WFCORE-4822] Add version 12 of the management schema
b9f86e2c62b533845946b1bbddbed1f36fe5acda HEAD@{2020-01-29 17:22:19 +0000}: commit (amend): [WFCORE-4822] Add version 12 of the management schema
926ccdb456c7ab34e84f22bc0a26132fb804c4a8 HEAD@{2020-01-29 17:22:02 +0000}: commit (amend): [WFCORE-4822] Add version 12 of the management schema
f4dc9f3f2c75c3bdaa3b190b3775feb0ce70a22f HEAD@{2020-01-29 17:10:16 +0000}: rebase -i (finish): returning to refs/heads/WFCORE-4822
{noformat}
Due to the time in the logs, it seems the jbos were executed before I commit the latest change in my local repo, and indeed they used the previous SHA
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Description:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
was:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the implies function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the *"implies"* function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Description:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the implies function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
was:
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*\**.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*\**.htm" pattern, when the implies function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Steps to Reproduce:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*\**.html", "**.htm", or "**.jsp", "**.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
was:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "**.html", "**.htm", or "**.jsp", "**.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Steps to Reproduce:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*\**.html", "*\**.htm", or "*\**.jsp", "*\**.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
was:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*\**.html", "**.htm", or "**.jsp", "**.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Steps to Reproduce:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*\.html", "*\.htm", or "*\.jsp", "*\.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
was:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*.html", "*.htm", or "*.jsp", "*.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
[ https://issues.redhat.com/browse/WFLY-13044?page=com.atlassian.jira.plugi... ]
Franco Gimenez updated WFLY-13044:
----------------------------------
Steps to Reproduce:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "**.html", "**.htm", or "**.jsp", "**.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
was:
Make two constraint, one deny access to all resources (with extension pattern and similar extension like "*\.html", "*\.htm", or "*\.jsp", "*\.js") and other allowing access to certain resource like "/index.html".
Start the application and see the error .
> WFLYSEC0012 Error in web.xml with similar Patterns
> --------------------------------------------------
>
> Key: WFLY-13044
> URL: https://issues.redhat.com/browse/WFLY-13044
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final, 18.0.1.Final, 19.0.0.Beta1
> Reporter: Franco Gimenez
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
>
>
> There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
> In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
> This is the web.xml to test the error:
> !image-2020-01-31-10-28-27-872.png|thumbnail!
> The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
> The log is:
> {code:java}
> 2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
> 2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
> at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
> at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> I add a test proyect and the complete log in my environment.
> With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-4972:
------------------------------------
Assignee: Anna Dupliak (was: Yeser Amer)
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Anna Dupliak
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13044) WFLYSEC0012 Error in web.xml with similar Patterns
by Franco Gimenez (Jira)
Franco Gimenez created WFLY-13044:
-------------------------------------
Summary: WFLYSEC0012 Error in web.xml with similar Patterns
Key: WFLY-13044
URL: https://issues.redhat.com/browse/WFLY-13044
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 19.0.0.Beta1, 18.0.1.Final, 18.0.0.Final
Reporter: Franco Gimenez
Assignee: Flavia Rainone
Attachments: app.zip, image-2020-01-31-10-28-27-872.png, server.log.zip, web.xml.zip
There are a problem while two constraints are limiting the access to the same resource with extensión patterns and exact pattern.
In our web.xml we have two constraints. One limiting the access to all resources and other allowing access to certain files.
This is the web.xml to test the error:
!image-2020-01-31-10-28-27-872.png|thumbnail!
The problem happens when the "*.htm" is evaluated inside of the jboss-jacc-api_1.5 lib. It tries to match "/index.html" against "*.htm" pattern, when the implies function returns false, it throws the exception.
The log is:
{code:java}
2020-01-30 18:44:38,293 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/issue-reproducer-1.0.0.Final-SNAPSHOT' for server 'default-server'
2020-01-30 18:44:38,302 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."issue-reproducer-1.0.0.Final-SNAPSHOT.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
at org.jboss.as.security.service.JaccService.start(JaccService.java:107)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList
at javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:314)
at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
at javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:287)
at org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
at org.jboss.as.security.service.JaccService.start(JaccService.java:86)
... 8 more
{code}
I add a test proyect and the complete log in my environment.
With Wildfly 17 there are not error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ]
Anna Dupliak closed DROOLS-4950.
--------------------------------
QE Status: VERIFIED (was: NEW)
Resolution: Won't Fix
The behavior is expected.
Need to enhance the UX https://issues.redhat.com/browse/DROOLS-4994
> Different behavior of collection unary checks
> ---------------------------------------------
>
> Key: DROOLS-4950
> URL: https://issues.redhat.com/browse/DROOLS-4950
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Anna Dupliak
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Issue was spotted during DROOLS-4698 review. However it can be handled separately.
> There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different.
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-4994:
------------------------------------
Assignee: Elizabeth Clayton (was: Yeser Amer)
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4994:
---------------------------------
Description:
Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
Suggested solution:
- to explain the difference directly in the popup, somewhere close to radio buttons create/define.
Example:
[1]
!Screenshot from 2020-01-17 13-56-02.png|thumbnail!
[2]
!Screenshot from 2020-01-17 13-56-10.png|thumbnail!
How that works now:
Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
What expression should be to make test pass:
(2 in ?)
was:
Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
Suggested solution:
- to explain the difference directly in the popup, somewhere close to radio buttons create/define.
Example:
How that works:
Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ]
Anna Dupliak reassigned DROOLS-4950:
------------------------------------
Assignee: Anna Dupliak (was: Yeser Amer)
> Different behavior of collection unary checks
> ---------------------------------------------
>
> Key: DROOLS-4950
> URL: https://issues.redhat.com/browse/DROOLS-4950
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Anna Dupliak
> Priority: Critical
> Labels: drools-tools
> Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Issue was spotted during DROOLS-4698 review. However it can be handled separately.
> There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different.
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4994:
------------------------------------
Summary: Highlight better that expression and graphical collection editor are different
Key: DROOLS-4994
URL: https://issues.redhat.com/browse/DROOLS-4994
Project: Drools
Issue Type: Enhancement
Components: Scenario Simulation and Testing
Affects Versions: 7.32.0.Final
Reporter: Anna Dupliak
Assignee: Yeser Amer
Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
Suggested solution:
- to explain the difference directly in the popup, somewhere close to radio buttons create/define.
Example:
How that works:
Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4994:
---------------------------------
Labels: BusinessCentral (was: )
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> How that works:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4994:
---------------------------------
Labels: drools-tools (was: BusinessCentral)
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> How that works:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Elizabeth Clayton commented on DROOLS-4972:
-------------------------------------------
Sounds good [~yamer], thank you!
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4993) [DMN Designer] Code Completion - add keywords
by Donato Marrazzo (Jira)
Donato Marrazzo created DROOLS-4993:
---------------------------------------
Summary: [DMN Designer] Code Completion - add keywords
Key: DROOLS-4993
URL: https://issues.redhat.com/browse/DROOLS-4993
Project: Drools
Issue Type: Feature Request
Components: DMN Editor
Reporter: Donato Marrazzo
Assignee: Guilherme Gomes
Manage FEEL expression keywords:
* in
* or
* and
* between
* if ... then ... else ...
* for ... in ... return ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model
by Bartosz Spyrko (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko updated WFCORE-255:
----------------------------------
Labels: domain-mode downstream_dependency (was: domain-mode)
> Boot time only system properties should not modify the runtime only the model
> -----------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-4822:
------------------------------------------
I have had some similar cases where I have not been 100% sure CI ran with the commit I wanted it to. I know CI has been cut back regarding how much it comments on PRs but it may be useful to log the details of the merge commit under test to verify the two SHAs.
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4992) Buildtime benchmark regression
by Daniel Rosa (Jira)
[ https://issues.redhat.com/browse/DROOLS-4992?page=com.atlassian.jira.plug... ]
Daniel Rosa commented on DROOLS-4992:
-------------------------------------
Since the new default is use executable model, we need to set the old behaviour as an argument to the buildAll function.
> Buildtime benchmark regression
> ------------------------------
>
> Key: DROOLS-4992
> URL: https://issues.redhat.com/browse/DROOLS-4992
> Project: Drools
> Issue Type: Bug
> Reporter: Daniel Rosa
> Assignee: Daniel Rosa
> Priority: Major
> Attachments: nightly_regression.png
>
>
> The experimental nightly benchmark dashboard has shown a performance loss 46.01% on the org.drools.benchmarks.buildtime.BuildKJarFromResourceBenchmark.createKJarFromResource benchmark after the merge to the master. It is probably due the change to default to executable model in the kie-maven-plugin issue (DROOLS-4092).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4992) Buildtime benchmark regression
by Daniel Rosa (Jira)
Daniel Rosa created DROOLS-4992:
-----------------------------------
Summary: Buildtime benchmark regression
Key: DROOLS-4992
URL: https://issues.redhat.com/browse/DROOLS-4992
Project: Drools
Issue Type: Bug
Reporter: Daniel Rosa
Assignee: Daniel Rosa
Attachments: nightly_regression.png
The experimental nightly benchmark dashboard has shown a performance loss 46.01% on the org.drools.benchmarks.buildtime.BuildKJarFromResourceBenchmark.createKJarFromResource benchmark after the merge to the master. It is probably due the change to default to executable model in the kie-maven-plugin issue (DROOLS-4092).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ]
Yeray Borges reopened WFCORE-4822:
----------------------------------
[~jmesnil] It looks like CI took the wrong commit, I just rebased and I am getting a checkstyle error on StandaloneXml_11
I reopen the issue to fix it up.
> Upgrade Management API Version to 12.0
> --------------------------------------
>
> Key: WFCORE-4822
> URL: https://issues.redhat.com/browse/WFCORE-4822
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 11.0.0.Beta8
>
>
> We need to fix the version state before WildFly 19 is released.
> * The KernelAPIVersion must be bumped to 12.0
> * We also need to release wildly-config-12.0.xsd with the proper host-exclude for
> * WildFlY18, Version.10
> * EAP73, Version.10
> (and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ]
Eduardo Martins commented on WFLY-12093:
----------------------------------------
[~parsharma] not working on it, please reassign to you if you want
[~jamezp] is this issue valid?
> bug in tutorial "batch-processing" with column "End Time"
> ---------------------------------------------------------
>
> Key: WFLY-12093
> URL: https://issues.redhat.com/browse/WFLY-12093
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: batch-processing
> Reporter: Святослав Кремлёв
> Assignee: Eduardo Martins
> Priority: Major
> Attachments: 2019-05-18 23_16_51-Batch Processing.png
>
>
> in file
> org/jboss/as/quickstarts/batch/controller/JobData.java
> {code}
> public Date getEndTime() {
> endTime = new Date();
> return endTime.getTime() == 0 ? null : endTime;
> }
> {code}
> its returns current time every time, not the job endTime
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Description:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
- Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
was:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> - Consider renaming the action to "Add list value" or whatever most closely describes the action.
> - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
> - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFCORE-4830) HCs (slaves) can not register to the DC (master) during DC and its servers start up
by Yeray Borges (Jira)
[ https://issues.redhat.com/browse/WFCORE-4830?page=com.atlassian.jira.plug... ]
Yeray Borges moved JBEAP-18604 to WFCORE-4830:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4830 (was: JBEAP-18604)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Management
(was: Management)
Affects Version/s: 10.0.0.Final
(was: 7.2.6.GA)
Fix Version/s: (was: 7.2.8.GA)
> HCs (slaves) can not register to the DC (master) during DC and its servers start up
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4830
> URL: https://issues.redhat.com/browse/WFCORE-4830
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 10.0.0.Final
> Reporter: Yeray Borges
> Assignee: JBoss SET
> Priority: Major
>
> Host Controller (slave) can not register to Domain Controller during its start up when there are managed servers starting.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Component/s: Scenario Simulation and Testing
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> - Consider renaming the action to "Add list value" or whatever most closely describes the action.
> - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
> Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Labels: drools-tools (was: )
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> - Consider renaming the action to "Add list value" or whatever most closely describes the action.
> - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
> Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Description:
When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
Consider renaming the action to "Add list value" or whatever most closely describes the action.
Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> Consider renaming the action to "Add list value" or whatever most closely describes the action.
> Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Description:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
https://issues.redhat.com/browse/DROOLS-4991#
https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
was:
When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
Consider renaming the action to "Add list value" or whatever most closely describes the action.
Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> - Consider renaming the action to "Add list value" or whatever most closely describes the action.
> - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> https://issues.redhat.com/browse/DROOLS-4991#
> https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
> Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4991:
-------------------------------
Description:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
was:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
https://issues.redhat.com/browse/DROOLS-4991#
https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Minor changes on Collection Editor UI
> -------------------------------------
>
> Key: DROOLS-4991
> URL: https://issues.redhat.com/browse/DROOLS-4991
> Project: Drools
> Issue Type: Enhancement
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
> - Consider renaming the action to "Add list value" or whatever most closely describes the action.
> - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right.
> https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png
> Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
> Thanks!
> Liz
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4972:
------------------------------------
[~uxdlc] I think I can easily handle most of these requirements in this ticket. I'll keep you updated.
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ]
Parul Sharma commented on WFLY-12093:
-------------------------------------
Hi [~emmartins] [~svkreml],
As per my understanding end time should not be update, after clicking on Update list button.
And also please let me if you are working on this issue?
Thanks,
Parul Sharma
> bug in tutorial "batch-processing" with column "End Time"
> ---------------------------------------------------------
>
> Key: WFLY-12093
> URL: https://issues.redhat.com/browse/WFLY-12093
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: batch-processing
> Reporter: Святослав Кремлёв
> Assignee: Eduardo Martins
> Priority: Major
> Attachments: 2019-05-18 23_16_51-Batch Processing.png
>
>
> in file
> org/jboss/as/quickstarts/batch/controller/JobData.java
> {code}
> public Date getEndTime() {
> endTime = new Date();
> return endTime.getTime() == 0 ? null : endTime;
> }
> {code}
> its returns current time every time, not the job endTime
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4990) NullPointerException with executable model using accumulate max with null Date field
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4990?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-4990:
--------------------------------
Sprint: 2020 Week 04-06 (from Jan 20)
> NullPointerException with executable model using accumulate max with null Date field
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-4990
> URL: https://issues.redhat.com/browse/DROOLS-4990
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Affects Versions: 7.32.0.Final
> Reporter: Martin Weiler
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
>
> Executing a rule containing accumulate max, eg:
> {code}
> rule AccumulateMaxDate
> when
> $max1 : Number() from accumulate(
> StockTick(isSetDueDate == true
> ,$time : dueDate);
> max($time.getTime().getTime()))
> then
> end
> {code}
> fails with a NPE at runtime if the StockDate.dueDate field is null:
> {noformat}
> Caused by: java.lang.NullPointerException
> at defaultpkg.RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.lambda$rule_AccumulateMaxDate$c9e019d8$1(RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.java:34)
> at org.drools.model.functions.Function1$Impl.apply(Function1.java:35)
> at org.drools.model.view.BindViewItem1.eval(BindViewItem1.java:85)
> at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:39)
> at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:35)
> at org.drools.modelcompiler.constraints.LambdaAccumulator$BindingAcc.getAccumulatedObject(LambdaAccumulator.java:154)
> at org.drools.modelcompiler.constraints.LambdaAccumulator.accumulate(LambdaAccumulator.java:88)
> at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:97)
> ... 53 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
