[JBoss JIRA] (JGRP-2315) ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message decryption failures
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/JGRP-2315?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reassigned JGRP-2315:
----------------------------------
Assignee: Paul Ferraro (was: Bela Ban)
> ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message decryption failures
> -----------------------------------------------------------------------------------------
>
> Key: JGRP-2315
> URL: https://issues.jboss.org/browse/JGRP-2315
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> If a message is received that needs to be decrypted, or if a message need to be encrypted, a cipher is taken from the queue. However, if a new coordinator concurrently sends a new secret key, it will clear and recreate the cipher queues. If the previous operation then puts its cipher back on the queue, the queue will now contain a cipher with the old secret key. This will result in random message decryption failures when a message encryption/decryption pulls the outdated cipher from the queue.
> While this is mitigated somewhat by the caching of old cipher versions, newly joined members do not have the ability to read messages encrypted by outdated ciphers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JGRP-2315) ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message decryption failures
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/JGRP-2315?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated JGRP-2315:
-------------------------------
Summary: ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message decryption failures (was: ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message descryption failures)
> ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message decryption failures
> -----------------------------------------------------------------------------------------
>
> Key: JGRP-2315
> URL: https://issues.jboss.org/browse/JGRP-2315
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: Paul Ferraro
> Assignee: Bela Ban
> Priority: Major
>
> If a message is received that needs to be decrypted, or if a message need to be encrypted, a cipher is taken from the queue. However, if a new coordinator concurrently sends a new secret key, it will clear and recreate the cipher queues. If the previous operation then puts its cipher back on the queue, the queue will now contain a cipher with the old secret key. This will result in random message decryption failures when a message encryption/decryption pulls the outdated cipher from the queue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-3358) Add possibility to choose between rule and DMN in scenario creation popup
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3358?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3358:
-------------------------------------
Description: Modify the "new Scenario" creation popup to allow choosing between DRL/DMN. In case of DMN, allow the user to select an already uploaded DMN file (was: As user I want to create a simulation to test rules or DMN model)
> Add possibility to choose between rule and DMN in scenario creation popup
> -------------------------------------------------------------------------
>
> Key: DROOLS-3358
> URL: https://issues.jboss.org/browse/DROOLS-3358
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: ScenarioSimulation
>
> Modify the "new Scenario" creation popup to allow choosing between DRL/DMN. In case of DMN, allow the user to select an already uploaded DMN file
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JGRP-2315) ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message descryption failures
by Paul Ferraro (Jira)
Paul Ferraro created JGRP-2315:
----------------------------------
Summary: ASYNC_ENCRYPT: Race condition in cipher queue usage can cause message descryption failures
Key: JGRP-2315
URL: https://issues.jboss.org/browse/JGRP-2315
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.15
Reporter: Paul Ferraro
Assignee: Bela Ban
If a message is received that needs to be decrypted, or if a message need to be encrypted, a cipher is taken from the queue. However, if a new coordinator concurrently sends a new secret key, it will clear and recreate the cipher queues. If the previous operation then puts its cipher back on the queue, the queue will now contain a cipher with the old secret key. This will result in random message decryption failures when a message encryption/decryption pulls the outdated cipher from the queue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBJCA-1380) XAManagedConnectionFactory screws up Datasource urls containing ;
by Yannick Einsweiler (Jira)
[ https://issues.jboss.org/browse/JBJCA-1380?page=com.atlassian.jira.plugin... ]
Yannick Einsweiler edited comment on JBJCA-1380 at 11/29/18 10:36 AM:
----------------------------------------------------------------------
[~chrispoulsen] same here.
Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in _org.h2.jdbcx.JdbcDataSource_, that is, User, Password and URL. Replace the offending line with:
{code:java}
xaDataSourceProperties = xaDataSourceProperties.replaceAll("(?i);(user|password|url)", "\n$1");
{code}
was (Author: einsweiy):
[~chrispoulsen] same here.
Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in _org.h2.jdbcx.JdbcDataSource_, that is, User, Password and URL. Replace the offending line with:
{code:java}
xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');
{code}
> XAManagedConnectionFactory screws up Datasource urls containing ;
> -----------------------------------------------------------------
>
> Key: JBJCA-1380
> URL: https://issues.jboss.org/browse/JBJCA-1380
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.4.9
> Environment: Unit testing using an embedded ironjacamar
> Reporter: Chris Poulsen
> Priority: Major
> Attachments: XAManagedConnectionFactory-h2-error.txt
>
>
> While trying to adjust settings on the H2 data source we use for a corner of our system during testing, I ran into problems.
> H2 accepts parameters appended to the url on the form ";<name>=<value>" for example:
> "jdbc:h2:mem:unit-test;MODE=Oracle"
> I was unable to deploy the datasource using:
> <xa-datasource-property name="url">jdbc:h2:mem:unit-test;MODE=Oracle</xa-datasource-property>
> Ironjacamar keeps complaining about:
> Caused by: java.lang.NoSuchMethodException: Method setMODE not found some setter not being found.
> My initial thought was that <url-delimiter> was the cause, but no dice.
> Following the trace into the sources, I guess the offending line is:
> {code:java}
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> {code}
> In XAManagedConnectionFactory around line: 174 (see following snippet)
> {code:java}
> public void setXADataSourceProperties(String xaDataSourceProperties) throws ResourceException
> {
> this.xaDataSourceProperties = xaDataSourceProperties;
> xaProps.clear();
> if (xaDataSourceProperties != null)
> {
> // Map any \ to \\
> xaDataSourceProperties = xaDataSourceProperties.replaceAll("\\\\", "\\\\\\\\");
> // Map any ; to \n
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> InputStream is = new ByteArrayInputStream(xaDataSourceProperties.getBytes());
> try
> {
> Properties p = new Properties();
> p.load(is);
> for (Map.Entry<Object, Object> entry : p.entrySet())
> {
> xaProps.put((String)entry.getKey(), (String)entry.getValue());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBJCA-1380) XAManagedConnectionFactory screws up Datasource urls containing ;
by Yannick Einsweiler (Jira)
[ https://issues.jboss.org/browse/JBJCA-1380?page=com.atlassian.jira.plugin... ]
Yannick Einsweiler edited comment on JBJCA-1380 at 11/29/18 10:23 AM:
----------------------------------------------------------------------
[~chrispoulsen] same here.
Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in _org.h2.jdbcx.JdbcDataSource_, that is, User, Password and URL. Replace the offending line with:
{code:java}
xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');
{code}
was (Author: einsweiy):
[~chrispoulsen] same here. Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in {quote}org.h2.jdbcx.JdbcDataSource{quote}, that is, User, Password and URL. Replace the offending line with:
{code:java}
xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');
{code}
> XAManagedConnectionFactory screws up Datasource urls containing ;
> -----------------------------------------------------------------
>
> Key: JBJCA-1380
> URL: https://issues.jboss.org/browse/JBJCA-1380
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.4.9
> Environment: Unit testing using an embedded ironjacamar
> Reporter: Chris Poulsen
> Priority: Major
> Attachments: XAManagedConnectionFactory-h2-error.txt
>
>
> While trying to adjust settings on the H2 data source we use for a corner of our system during testing, I ran into problems.
> H2 accepts parameters appended to the url on the form ";<name>=<value>" for example:
> "jdbc:h2:mem:unit-test;MODE=Oracle"
> I was unable to deploy the datasource using:
> <xa-datasource-property name="url">jdbc:h2:mem:unit-test;MODE=Oracle</xa-datasource-property>
> Ironjacamar keeps complaining about:
> Caused by: java.lang.NoSuchMethodException: Method setMODE not found some setter not being found.
> My initial thought was that <url-delimiter> was the cause, but no dice.
> Following the trace into the sources, I guess the offending line is:
> {code:java}
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> {code}
> In XAManagedConnectionFactory around line: 174 (see following snippet)
> {code:java}
> public void setXADataSourceProperties(String xaDataSourceProperties) throws ResourceException
> {
> this.xaDataSourceProperties = xaDataSourceProperties;
> xaProps.clear();
> if (xaDataSourceProperties != null)
> {
> // Map any \ to \\
> xaDataSourceProperties = xaDataSourceProperties.replaceAll("\\\\", "\\\\\\\\");
> // Map any ; to \n
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> InputStream is = new ByteArrayInputStream(xaDataSourceProperties.getBytes());
> try
> {
> Properties p = new Properties();
> p.load(is);
> for (Map.Entry<Object, Object> entry : p.entrySet())
> {
> xaProps.put((String)entry.getKey(), (String)entry.getValue());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBJCA-1380) XAManagedConnectionFactory screws up Datasource urls containing ;
by Yannick Einsweiler (Jira)
[ https://issues.jboss.org/browse/JBJCA-1380?page=com.atlassian.jira.plugin... ]
Yannick Einsweiler edited comment on JBJCA-1380 at 11/29/18 10:22 AM:
----------------------------------------------------------------------
[~chrispoulsen] same here. Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in {quote}org.h2.jdbcx.JdbcDataSource{quote}, that is, User, Password and URL. Replace the offending line with:
{code:java}
xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');
{code}
was (Author: einsweiy):
[~chrispoulsen] same here. Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in `org.h2.jdbcx.JdbcDataSource`, that is, User, Password and URL. Replace the offending line with:
`xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');`
> XAManagedConnectionFactory screws up Datasource urls containing ;
> -----------------------------------------------------------------
>
> Key: JBJCA-1380
> URL: https://issues.jboss.org/browse/JBJCA-1380
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.4.9
> Environment: Unit testing using an embedded ironjacamar
> Reporter: Chris Poulsen
> Priority: Major
> Attachments: XAManagedConnectionFactory-h2-error.txt
>
>
> While trying to adjust settings on the H2 data source we use for a corner of our system during testing, I ran into problems.
> H2 accepts parameters appended to the url on the form ";<name>=<value>" for example:
> "jdbc:h2:mem:unit-test;MODE=Oracle"
> I was unable to deploy the datasource using:
> <xa-datasource-property name="url">jdbc:h2:mem:unit-test;MODE=Oracle</xa-datasource-property>
> Ironjacamar keeps complaining about:
> Caused by: java.lang.NoSuchMethodException: Method setMODE not found some setter not being found.
> My initial thought was that <url-delimiter> was the cause, but no dice.
> Following the trace into the sources, I guess the offending line is:
> {code:java}
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> {code}
> In XAManagedConnectionFactory around line: 174 (see following snippet)
> {code:java}
> public void setXADataSourceProperties(String xaDataSourceProperties) throws ResourceException
> {
> this.xaDataSourceProperties = xaDataSourceProperties;
> xaProps.clear();
> if (xaDataSourceProperties != null)
> {
> // Map any \ to \\
> xaDataSourceProperties = xaDataSourceProperties.replaceAll("\\\\", "\\\\\\\\");
> // Map any ; to \n
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> InputStream is = new ByteArrayInputStream(xaDataSourceProperties.getBytes());
> try
> {
> Properties p = new Properties();
> p.load(is);
> for (Map.Entry<Object, Object> entry : p.entrySet())
> {
> xaProps.put((String)entry.getKey(), (String)entry.getValue());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBJCA-1380) XAManagedConnectionFactory screws up Datasource urls containing ;
by Yannick Einsweiler (Jira)
[ https://issues.jboss.org/browse/JBJCA-1380?page=com.atlassian.jira.plugin... ]
Yannick Einsweiler edited comment on JBJCA-1380 at 11/29/18 10:20 AM:
----------------------------------------------------------------------
[~chrispoulsen] same here. Not sure why semicolon was replaced in the first place but you cannot just comment out that line as the User and Password properties are concatenated to it using semicolon.
As such you must only replace for those properties which have a setter in `org.h2.jdbcx.JdbcDataSource`, that is, User, Password and URL. Replace the offending line with:
`xaDataSourceProperties = xaDataSourceProperties.replaceAll('(?i);(user|password|url)', '\n$1');`
was (Author: einsweiy):
[~chrispoulsen] same here. Not sure why semicolon was replaced in the first place. If someone wanted to have separate properties, that's what `xa-datasource-property` is there for.
No real workaround as `org.h2.jdbcx.JdbcDataSource` class as no other setters and uses hardcoded semicolon to parse/split the URL string. We ended up commenting out that replacement line in a custom class.
The fix in my mind would be to check if URL is h2-related and if it is, do not replace semicolons. There could be however other dbms.
> XAManagedConnectionFactory screws up Datasource urls containing ;
> -----------------------------------------------------------------
>
> Key: JBJCA-1380
> URL: https://issues.jboss.org/browse/JBJCA-1380
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.4.9
> Environment: Unit testing using an embedded ironjacamar
> Reporter: Chris Poulsen
> Priority: Major
> Attachments: XAManagedConnectionFactory-h2-error.txt
>
>
> While trying to adjust settings on the H2 data source we use for a corner of our system during testing, I ran into problems.
> H2 accepts parameters appended to the url on the form ";<name>=<value>" for example:
> "jdbc:h2:mem:unit-test;MODE=Oracle"
> I was unable to deploy the datasource using:
> <xa-datasource-property name="url">jdbc:h2:mem:unit-test;MODE=Oracle</xa-datasource-property>
> Ironjacamar keeps complaining about:
> Caused by: java.lang.NoSuchMethodException: Method setMODE not found some setter not being found.
> My initial thought was that <url-delimiter> was the cause, but no dice.
> Following the trace into the sources, I guess the offending line is:
> {code:java}
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> {code}
> In XAManagedConnectionFactory around line: 174 (see following snippet)
> {code:java}
> public void setXADataSourceProperties(String xaDataSourceProperties) throws ResourceException
> {
> this.xaDataSourceProperties = xaDataSourceProperties;
> xaProps.clear();
> if (xaDataSourceProperties != null)
> {
> // Map any \ to \\
> xaDataSourceProperties = xaDataSourceProperties.replaceAll("\\\\", "\\\\\\\\");
> // Map any ; to \n
> xaDataSourceProperties = xaDataSourceProperties.replace(';', '\n');
> InputStream is = new ByteArrayInputStream(xaDataSourceProperties.getBytes());
> try
> {
> Properties p = new Properties();
> p.load(is);
> for (Map.Entry<Object, Object> entry : p.entrySet())
> {
> xaProps.put((String)entry.getKey(), (String)entry.getValue());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-3386) [DMN Designer] Font settings available from Boxed Expression editor
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3386?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3386:
-----------------------------------
Story Points: 3
Sprint: 2018 Week 48-50
> [DMN Designer] Font settings available from Boxed Expression editor
> -------------------------------------------------------------------
>
> Key: DROOLS-3386
> URL: https://issues.jboss.org/browse/DROOLS-3386
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Trivial
> Labels: drools-tools
>
> The font settings are available in the properties panel when Boxed Expression editor is opened, however changed values are not reflected into DRD diagram neither boxed expression grid.
> One of solution in top of my head is not to show those font settings when boxed expression editor is opened.
> Spotted during DROOLS-3351 review, however I think it is not related.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years