[JBoss JIRA] (WFLY-9433) Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1
by Chao Wang (JIRA)
Chao Wang created WFLY-9433:
-------------------------------
Summary: Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1
Key: WFLY-9433
URL: https://issues.jboss.org/browse/WFLY-9433
Project: WildFly
Issue Type: Enhancement
Components: JMS
Affects Versions: 11.0.0.CR1
Reporter: Chao Wang
Assignee: Chao Wang
There are several attributes defined from ActiveMQ Artemis configuration parameters in ActiveMQClient.java and ActiveMQDefaultConfiguration.java are allowed to take value -1.
As they miss proper InfiniteOrPositiveValidators, they can also take any negative values which is incorrect.
{noformat}
ActiveMQClient.java
public static final long DEFAULT_CLIENT_FAILURE_CHECK_PERIOD_INVM = -1;
public static final long DEFAULT_CONNECTION_TTL_INVM = -1;
public static final int DEFAULT_CONSUMER_MAX_RATE = -1;
public static final int DEFAULT_CONFIRMATION_WINDOW_SIZE = -1;
public static final int DEFAULT_PRODUCER_MAX_RATE = -1;
public static final int DEFAULT_THREAD_POOL_MAX_SIZE = -1;
ActiveMQDefaultConfiguration.java
private static long DEFAULT_CONNECTION_TTL_OVERRIDE = -1;
private static int DEFAULT_JOURNAL_POOL_FILES = -1;
private static long DEFAULT_CONNECTION_TTL_OVERRIDE = -1;
private static int DEFAULT_JOURNAL_PERF_BLAST_PAGES = -1;
private static long DEFAULT_SERVER_DUMP_INTERVAL = -1;
private static long DEFAULT_MEMORY_MEASURE_INTERVAL = -1;
private static int DEFAULT_BRIDGE_INITIAL_CONNECT_ATTEMPTS = -1;
private static int DEFAULT_BRIDGE_RECONNECT_ATTEMPTS = -1;
private static int DEFAULT_BRIDGE_PRODUCER_WINDOW_SIZE = -1;
private static int DEFAULT_CLUSTER_INITIAL_CONNECT_ATTEMPTS = -1;
private static int DEFAULT_CLUSTER_RECONNECT_ATTEMPTS = -1;
private static int DEFAULT_HAPOLICY_BACKUP_REQUEST_RETRIES = -1;
private static int DEFAULT_GROUPING_HANDLER_GROUP_TIMEOUT = -1;
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1759) Not able to load all the kieModule from classpath
by Chandresh Mishra (JIRA)
Chandresh Mishra created DROOLS-1759:
----------------------------------------
Summary: Not able to load all the kieModule from classpath
Key: DROOLS-1759
URL: https://issues.jboss.org/browse/DROOLS-1759
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.4.0.Final
Reporter: Chandresh Mishra
Assignee: Mario Fusco
Hi ,
I am trying to load a rules from classpath in gradle project.
It is a multi module gradle project.It has following structure.
Application
Application-rule
root
Application has compile project(':application-rule') in build.gradle.
application-rule has external dependency on common-rules .
Now when I am trying to load KieContainer from classpath in Application project. It is loading only kiebase in common-rules.jar .It is not loading kiebase in kmodule.xml present in Application-rule.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (ELY-1396) Ensure the length of an ASN.1 SET is calculated properly when it has an element whose length exceeds 127 bytes
by Farah Juma (JIRA)
Farah Juma created ELY-1396:
-------------------------------
Summary: Ensure the length of an ASN.1 SET is calculated properly when it has an element whose length exceeds 127 bytes
Key: ELY-1396
URL: https://issues.jboss.org/browse/ELY-1396
Project: WildFly Elytron
Issue Type: Bug
Components: Utils
Reporter: Farah Juma
Assignee: Farah Juma
When an element's length is greater than 127 bytes, {{DEREncoder#writeLength}} successfully writes the length octets using the long form where bit 8 of first octet has value "1" and bits 7-1 give the number of additional length octets and the second and following octets give the length. However, the value returned by {{writeLength}} in this case is currently just the number of additional length octets. When such an element is part of a SET, this results in the wrong accumulated length for the SET. The value returned by {{writeLength}} should also include the first octet.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1758) Code snippet in doc Traits chapter wrongly formatted
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1758:
--------------------------------------
Summary: Code snippet in doc Traits chapter wrongly formatted
Key: DROOLS-1758
URL: https://issues.jboss.org/browse/DROOLS-1758
Project: Drools
Issue Type: Bug
Components: docs
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Attachments: image-2017-10-10-22-27-42-739.png, image-2017-10-10-22-29-11-525.png
Exhibit 1, the snippet block is present but not verbatim formatted:
!image-2017-10-10-22-27-42-739.png|thumbnail!
Exhibit 2, an allegedly snippet of code is lost in chapter text:
!image-2017-10-10-22-29-11-525.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3041) Cannot add policy resource with no parameter
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3041?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3041:
-------------------------------------
Fix Version/s: 3.0.6.Final
(was: 3.0.5.Final)
> Cannot add policy resource with no parameter
> --------------------------------------------
>
> Key: WFCORE-3041
> URL: https://issues.jboss.org/browse/WFCORE-3041
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Claudio Miranda
> Assignee: Brian Stansberry
> Priority: Blocker
> Fix For: 3.0.6.Final
>
>
> subsystem=elytron/policy resources has no required attributes, but it fails to add a resource with no parameters.
> {code}
> /profile=full/subsystem=elytron/policy=policy_test:add
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => {"server-one" => "Could find policy provider with name [policy_test]"}}}}}},
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {"server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "Could find policy provider with name [policy_test]",
> "rolled-back" => true
> }}}}}}
> }
> {code}
> To add is necessary to inform either custom-policy or jacc-policy
> {code}
> /profile=full/subsystem=elytron/policy=policy2:add(jacc-policy=[{name=policy2}])
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {"server-one" => {"response" => {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }}}}}}
> }
> {code}
> There is also a problem related to "default-policy" being set to a non existent policy.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9431) Write a test to ensure a library in an EAR uses the correct log context
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-9431?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-9431:
-------------------------------------
A test will need to be written in WildFly as deployments are processed differently in WildFly Core.
> Write a test to ensure a library in an EAR uses the correct log context
> -----------------------------------------------------------------------
>
> Key: WFLY-9431
> URL: https://issues.jboss.org/browse/WFLY-9431
> Project: WildFly
> Issue Type: Task
> Components: Logging, Test Suite
> Reporter: James Perkins
> Assignee: James Perkins
> Attachments: 01933631-new.tar.gz, logging-profile.zip
>
>
> Two ear files are deployed on EAP instance and both are configured to use different logging profile through EAR/META-INF/MANIFEST.MF file.
> WAR file from EAR uses some libraries those are present in the "lib" folder of each ear file. Application1.ear which logs in app1.log and Application2.ear which logs in app2.log.
> when we access application we can see logging from EAR1 into EAR2 log file .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months