[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-12592:
------------------------------------
Component/s: Security
> Usage of Elytron's SSL-Context in establishing SSL communication with DataBase
> ------------------------------------------------------------------------------
>
> Key: WFLY-12592
> URL: https://issues.jboss.org/browse/WFLY-12592
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 14.0.0.Final
> Reporter: Saurabh Shriramwar
> Assignee: Brian Stansberry
> Priority: Minor
>
> To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-12592:
------------------------------------
Priority: Major (was: Minor)
> Usage of Elytron's SSL-Context in establishing SSL communication with DataBase
> ------------------------------------------------------------------------------
>
> Key: WFLY-12592
> URL: https://issues.jboss.org/browse/WFLY-12592
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 14.0.0.Final
> Reporter: Saurabh Shriramwar
> Assignee: Brian Stansberry
> Priority: Major
>
> To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4681) Add Phase entries for Microprofile OpenAPI Extension
by Michael Edgar (Jira)
[ https://issues.jboss.org/browse/WFCORE-4681?page=com.atlassian.jira.plugi... ]
Michael Edgar updated WFCORE-4681:
----------------------------------
Summary: Add Phase entries for Microprofile OpenAPI Extension (was: Add Phase entries for Microprofile OenAPI Extension)
> Add Phase entries for Microprofile OpenAPI Extension
> ----------------------------------------------------
>
> Key: WFCORE-4681
> URL: https://issues.jboss.org/browse/WFCORE-4681
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 10.0.0.Final
> Reporter: Michael Edgar
> Assignee: Jeff Mesnil
> Priority: Major
>
> Add the following entries to {{Phase}} and bump Jandex version to 2.1.1.Final, required by SmallRye OpenAPI implementation.
> {code:java}public static final int DEPENDENCIES_MICROPROFILE_OPENAPI = 0x1890;
> public static final int POST_MODULE_MICROPROFILE_OPENAPI = 0x3790;{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4572) a fact with many properties causes a problem with "not" rule in executable-model
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-4572:
-----------------------------------------
Summary: a fact with many properties causes a problem with "not" rule in executable-model
Key: DROOLS-4572
URL: https://issues.jboss.org/browse/DROOLS-4572
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.27.0.Final
Environment: - executable-model
- Without property reactive
Reporter: Toshiya Kobayashi
Assignee: Luca Molteni
Under the conditions:
- executable-model
- "drools.propertySpecific" = "ALLOWED"
- A fact which has more than 128 properties
- A rule with "not" which joins facts
"not" doesn't match so the rule results in an unexpected firing (e.g. an infinite loop)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4565) MVELDialectRuntimeData is not thread safe
by Timo Gutjahr (Jira)
[ https://issues.jboss.org/browse/DROOLS-4565?page=com.atlassian.jira.plugi... ]
Timo Gutjahr commented on DROOLS-4565:
--------------------------------------
Hi, I'm afraid we don't have a reproducer. We found the problem in our integration tests. When analyzing the problem we compared a serialized broken KB with a working KB and found that the set in MVELDialectRuntimeData contains one less element. The missing element was a MVELObjectClassFieldReader. We could make this observation with 3 different KBs. Whereby the problem occurs only very rarely.
> MVELDialectRuntimeData is not thread safe
> -----------------------------------------
>
> Key: DROOLS-4565
> URL: https://issues.jboss.org/browse/DROOLS-4565
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Environment: Java 11.0.2
> Different OS
> Reporter: Timo Gutjahr
> Assignee: Mario Fusco
> Priority: Major
> Attachments: ForkJoinPool-1-worker-1.txt, NPE.txt, main.txt
>
>
> MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] and [^main.txt] )
> If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
> We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
> While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years