[JBoss JIRA] (WFCORE-4253) SNICombinedWithALPNTestCase fails with security manager on Java 11
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFCORE-4253?page=com.atlassian.jira.plugi... ]
Bartosz Baranowski reassigned WFCORE-4253:
------------------------------------------
Assignee: Bartosz Baranowski (was: Darran Lofthouse)
> SNICombinedWithALPNTestCase fails with security manager on Java 11
> ------------------------------------------------------------------
>
> Key: WFCORE-4253
> URL: https://issues.jboss.org/browse/WFCORE-4253
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Environment: Java 11
> Reporter: Ondrej Kotek
> Assignee: Bartosz Baranowski
> Priority: Major
>
> {{org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase}} fails with security manager on Java 11 due to missing permissions:
> {noformat}
> [ERROR] Failure when constructing test Time elapsed: 0.029 s <<< FAILURE!
> java.lang.AssertionError:
> Failed to deploy test.jar: 10 assets: {"WFLYCTL0080: Failed services" => {"jboss.undertow-test-server" => "Failed to start service
> Caused by: java.lang.ExceptionInInitializerError
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.io.FilePermission\" \"/home/okotek/test/asts-core-intermit/testsuite/standalone/target/wildfly-core/modules/system/layers/base/io/undertow/core/main/undertow-core-2.0.15.Final.jar\" \"read\")\" in code source \"(vfs:/content/test.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.test.jar\" from Service Module Loader\")"}}
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase.deploy(SNICombinedWithALPNTestCase.java:414)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase$Setup.setup(SNICombinedWithALPNTestCase.java:188)
> at org.wildfly.core.testrunner.WildflyTestRunner.runSetupTasks(WildflyTestRunner.java:121)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:107)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> ...
> {noformat}
> -A customer should not be asked to add such permission for reading a module file, it brings bad UX and it could bring security flaws.-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3461) Outdated documentation on GEF
by Vinicius Scheidegger (Jira)
Vinicius Scheidegger created DROOLS-3461:
--------------------------------------------
Summary: Outdated documentation on GEF
Key: DROOLS-3461
URL: https://issues.jboss.org/browse/DROOLS-3461
Project: Drools
Issue Type: Bug
Components: docs
Affects Versions: 7.15.0.Final
Reporter: Vinicius Scheidegger
Assignee: Mario Fusco
The documentation on:
https://docs.jboss.org/drools/release/7.15.0.Final/drools-docs/html_singl...
states that if I want to install the eclipse plugin I need to install GEF, then it points me to a Eclipse update site from GEF, which no longer has the options mentioned and shown in the print screen.
The version for GEF shown is 3.4.2 (probably from 2008), but apparently GEF was remodeled and its current version 5 does not have the same components.
Probably the Drools plugin was updated but the documentation was not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11547) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-11547?page=com.atlassian.jira.plugin... ]
Teresa Miyar updated WFLY-11547:
--------------------------------
Affects Version/s: 15.0.0.Final
> Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
> ----------------------------------------------------------------------------
>
> Key: WFLY-11547
> URL: https://issues.jboss.org/browse/WFLY-11547
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 15.0.0.Final
> Reporter: Teresa Miyar
> Assignee: Teresa Miyar
> Priority: Major
>
> The issue is that the xsd says it is using a blocking queue but it is using an incomplete bounded one since there are properties that cannot be set.
> jboss-cli returns:
> {code:java}
> /subsystem=jca/workmanager=default/long-running-threads=default:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "A thread pool executor with a bounded queue where threads submittings tasks will not block. Such a thread pool has a core and maximum size and a specified queue length. When a task is submitted, if the number of running threads is less than the core size, a new thread is created. Otherwise, if there is room in the queue, the task is enqueued. Otherwise, if the number of running threads is less than the maximum size, a new thread is created. Otherwise, the task is handed off to the designated handoff executor, if one is specified. Otherwise, the task is discarded.",
> ......
> "handoff-executor" => {
> "type" => STRING,
> "description" => "An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ....
> {code}
> But the xsd does not allow to set a hand-off executor for the short/long running threads
> The xsd:
> <xs:annotation>
> <xs:documentation>
> <![CDATA[
> See threads:blocking-bounded-queue-thread-pool.
> ]]>
> </xs:documentation>
> </xs:annotation>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11547) [GSS](7.2.z) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-11547?page=com.atlassian.jira.plugin... ]
Teresa Miyar moved JBEAP-16084 to WFLY-11547:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11547 (was: JBEAP-16084)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
(was: JCA)
> [GSS](7.2.z) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-11547
> URL: https://issues.jboss.org/browse/WFLY-11547
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Teresa Miyar
> Assignee: Teresa Miyar
> Priority: Major
>
> The issue is that the xsd says it is using a blocking queue but it is using an incomplete bounded one since there are properties that cannot be set.
> jboss-cli returns:
> {code:java}
> /subsystem=jca/workmanager=default/long-running-threads=default:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "A thread pool executor with a bounded queue where threads submittings tasks will not block. Such a thread pool has a core and maximum size and a specified queue length. When a task is submitted, if the number of running threads is less than the core size, a new thread is created. Otherwise, if there is room in the queue, the task is enqueued. Otherwise, if the number of running threads is less than the maximum size, a new thread is created. Otherwise, the task is handed off to the designated handoff executor, if one is specified. Otherwise, the task is discarded.",
> ......
> "handoff-executor" => {
> "type" => STRING,
> "description" => "An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ....
> {code}
> But the xsd does not allow to set a hand-off executor for the short/long running threads
> The xsd:
> <xs:annotation>
> <xs:documentation>
> <![CDATA[
> See threads:blocking-bounded-queue-thread-pool.
> ]]>
> </xs:documentation>
> </xs:annotation>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11547) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-11547?page=com.atlassian.jira.plugin... ]
Teresa Miyar updated WFLY-11547:
--------------------------------
Summary: Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads (was: [GSS](7.2.z) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads)
> Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
> ----------------------------------------------------------------------------
>
> Key: WFLY-11547
> URL: https://issues.jboss.org/browse/WFLY-11547
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Teresa Miyar
> Assignee: Teresa Miyar
> Priority: Major
>
> The issue is that the xsd says it is using a blocking queue but it is using an incomplete bounded one since there are properties that cannot be set.
> jboss-cli returns:
> {code:java}
> /subsystem=jca/workmanager=default/long-running-threads=default:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "A thread pool executor with a bounded queue where threads submittings tasks will not block. Such a thread pool has a core and maximum size and a specified queue length. When a task is submitted, if the number of running threads is less than the core size, a new thread is created. Otherwise, if there is room in the queue, the task is enqueued. Otherwise, if the number of running threads is less than the maximum size, a new thread is created. Otherwise, the task is handed off to the designated handoff executor, if one is specified. Otherwise, the task is discarded.",
> ......
> "handoff-executor" => {
> "type" => STRING,
> "description" => "An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ....
> {code}
> But the xsd does not allow to set a hand-off executor for the short/long running threads
> The xsd:
> <xs:annotation>
> <xs:documentation>
> <![CDATA[
> See threads:blocking-bounded-queue-thread-pool.
> ]]>
> </xs:documentation>
> </xs:annotation>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2288:
--------------------------------
Done :-)
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16, 3.6.17
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3460) KIE Server REST Command GetObjects with ObjectFilter not working
by Balakrishnan Balasubramanian (Jira)
Balakrishnan Balasubramanian created DROOLS-3460:
----------------------------------------------------
Summary: KIE Server REST Command GetObjects with ObjectFilter not working
Key: DROOLS-3460
URL: https://issues.jboss.org/browse/DROOLS-3460
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 7.15.0.Final
Environment: RHEL 7.5, EAP 7.1.0, Drools 7.15.0.Final
Reporter: Balakrishnan Balasubramanian
Assignee: Maciej Swiderski
Filtering the facts in the GetObjectsCommand doesn't do any object filtering!.
Here are the two code pieces that were used to set the ObjectFilter into GetObjectsCommand, but didn't produce the expected filtered results.
*+Trial 1:+*
{code:java}
ObjectFilter filter = new ObjectFilter() {
@Override
public boolean accept(Object object) {
return object.getClass().getName().equals("a.b.c.PotentialFraudFact");
}
};
Command<?> getObjects = commandsFactory.newGetObjects(filter, "out");
{code}
*+Trial 2:+*
{code:java}
ClassObjectSerializationFilter filter = new ClassObjectSerializationFilter(PotentialFraudFact.class);
Command<?> getObjects = commandsFactory.newGetObjects(filter, "out");
{code}
In the response, the "out" identifier has *all* facts, not just the ones matching the given filter. It's as if it ignores the filter. Also, no error messages appear in the console.
When a ClassObjectFilter is used instead of the aforementioned implementations, a ClassNotFoundException (_shown below_) for the a.b.c.PotentialFraudFact.class occurs. This is incorrect as the deployed container/KJAR has this class!.
{code:java}
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: a.b.c.PotentialFraudFact from [Module "deployment.kie-server.war" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.drools.core.ClassObjectSerializationFilter.accept(ClassObjectSerializationFilter.java:50)
... 73 more
{code}
The issue is with this line https://github.com/kiegroup/drools/blob/4c6856223b8be47b4fc52c35423be8b50... where the class loader used to find the class couldn't find the class that corresponds to the given Fact.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-3971) Jar Services in META-INF/services are not loaded from static modules
by Tomas Repel (Jira)
[ https://issues.jboss.org/browse/WFLY-3971?page=com.atlassian.jira.plugin.... ]
Tomas Repel commented on WFLY-3971:
-----------------------------------
Hello [~tiago.matias], I am sorry, this ticket is too old for me to remember what it was about exactly. There is a link to reproducer in my very first comment to this issue. It is 3 yrs old though. There is also a solution in my comment above. This seemed to be working for WF10 and Spring 4.0.x. Things might have changed since then though. If the solution described in this ticket does not work for you it is probably best to create a new issue. You might link it with this issue as well.
> Jar Services in META-INF/services are not loaded from static modules
> --------------------------------------------------------------------
>
> Key: WFLY-3971
> URL: https://issues.jboss.org/browse/WFLY-3971
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 9.0.0.Final, 10.0.0.Alpha6
> Reporter: Tomas Repel
> Assignee: Stuart Douglas
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> If the web application (war) uses jar file from static module, the content of META-INF/services has no effect. If the jar is located inside WEB-INF/lib, services are loaded successfully.
> Neither adding `Dependencies: my.module.name.com services` into MANIFEST.MF nor adding `services="import"` to jboss-deployment-structure.xml works.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months