[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Nuno Godinho de Matos edited comment on WFLY-8954 at 9/1/17 9:08 AM:
---------------------------------------------------------------------
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty "state" check to be run against a the wrong entity field.
However, the refresh action is being redundant. That is a very good indication.
I believe my impression above is nothing but a false negative.
We are still in the clear for now...
Changes are so far looking good.
I have taken the dirty code that was specific to wildfly onobsever bug from our code, and I will see if the CI system tests are fine all accross.
NOTE:
- I will be opening a new wildfly JIRA related to the unregister connection problem mentioned on a wildfly thread.
{panel}
java.lang.IllegalStateException: IJ000152: Trying to return an unknown connection: org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@40a9ad99
{panel}
This issue is not addressed by this fix.
Thanks.
was (Author: nuno.godinhomatos):
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty "state" check to be run against a the wrong entity field.
However, the refresh action is being redundant. That is a very good indication.
I believe my impression above is nothing but a false negative.
We are still in the clear for now...
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
> Assignee: Scott Marlow
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ELY-386) Unable to create HTTPS connection when some opnessl cipher suite with DHE are used
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-386?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina reassigned ELY-386:
------------------------------
Assignee: Jan Kalina
> Unable to create HTTPS connection when some opnessl cipher suite with DHE are used
> ----------------------------------------------------------------------------------
>
> Key: ELY-386
> URL: https://issues.jboss.org/browse/ELY-386
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.0.2.Final
> Environment: Oracle java 1.8.0_66
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> Can't configure OpenSSL cipher suites EXP-DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC3-SHA, EXP-DHE-DSS-DES-CBC-SHA, DHE-DSS-CBC-SHA, DHE-DSS-DES-CBC3-SHA [1] for HTTPS connection. Seems like everlasting problem DHE vs. EDH [2] - these cipher suites don't work neither in EAP6. IMHO problem is in MechanismDatabase.properties, where these DHE cipher suite are mapped to openssl EDH cipher suite what contradict openssl documentation [1]:
> {code}
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = alias:TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
> SSL_DHE_RSA_WITH_DES_CBC_SHA = alias:TLS_DHE_RSA_WITH_DES_CBC_SHA
> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA = alias:TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,true,EXP40,false,40,56
> TLS_DHE_RSA_WITH_DES_CBC_SHA = EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,false,LOW,false,56,56
> TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA = EDH-RSA-DES-CBC3-SHA,DHE,RSA,3DES,SHA1,SSLv3,false,HIGH,true,168,168
> SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,true,EXP40,false,40,56
> SSL_DHE_DSS_WITH_DES_CBC_SHA = EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56
> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA = EDH-DSS-DES-CBC3-SHA,DHE,DSS,3DES,SHA1,SSLv3,false,HIGH,true,168,168
> {code}
> Note that MechanismDatabase.properties is inconsistent in mapping DHE cipher suites to openssl cipher suites, as there also exist couple of them which map DHE to DHE, for example
> {code}
> TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 = DHE-RSA-AES128-SHA256,DHE,RSA,AES128,SHA256,TLSv1.2,false,HIGH,true,128,128
> TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 = DHE-RSA-AES256-SHA256,DHE,RSA,AES256,SHA256,TLSv1.2,false,HIGH,true,256,256
> TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 = DHE-RSA-AES128-GCM-SHA256,DHE,RSA,AES128GCM,AEAD,TLSv1.2,false,HIGH,true,128,128
> TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 = DHE-RSA-AES256-GCM-SHA384,DHE,RSA,AES256GCM,AEAD,TLSv1.2,false,HIGH,true,256,256
> {code}
> In MechanismDatabase.properties is also said that
> ??Note that all EDH ciphers automatically get a DHE OpenSSL-style alias (and vice-versa)??
> I think this JIRA contradict this comment.
> Last thing, based on [1] shouldn't be SSL_DHE_DSS_WITH_DES_CBC_SHA defined as
> SSL_DHE_DSS_WITH_DES_CBC_SHA = DHE-DSS-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56
> ?
> [1] https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-SUITE-NAMES
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1123304
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ELY-386) Unable to create HTTPS connection when some opnessl cipher suite with DHE are used
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-386?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina commented on ELY-386:
--------------------------------
All mentioned in last comment, except DHE-DSS-CBC-SHA, is mapped correctly in upstream. Only DHE-DSS-CBC-SHA needs to be fixed yet.
> Unable to create HTTPS connection when some opnessl cipher suite with DHE are used
> ----------------------------------------------------------------------------------
>
> Key: ELY-386
> URL: https://issues.jboss.org/browse/ELY-386
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.0.2.Final
> Environment: Oracle java 1.8.0_66
> Reporter: Martin Choma
>
> Can't configure OpenSSL cipher suites EXP-DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC3-SHA, EXP-DHE-DSS-DES-CBC-SHA, DHE-DSS-CBC-SHA, DHE-DSS-DES-CBC3-SHA [1] for HTTPS connection. Seems like everlasting problem DHE vs. EDH [2] - these cipher suites don't work neither in EAP6. IMHO problem is in MechanismDatabase.properties, where these DHE cipher suite are mapped to openssl EDH cipher suite what contradict openssl documentation [1]:
> {code}
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = alias:TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
> SSL_DHE_RSA_WITH_DES_CBC_SHA = alias:TLS_DHE_RSA_WITH_DES_CBC_SHA
> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA = alias:TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,true,EXP40,false,40,56
> TLS_DHE_RSA_WITH_DES_CBC_SHA = EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,false,LOW,false,56,56
> TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA = EDH-RSA-DES-CBC3-SHA,DHE,RSA,3DES,SHA1,SSLv3,false,HIGH,true,168,168
> SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,true,EXP40,false,40,56
> SSL_DHE_DSS_WITH_DES_CBC_SHA = EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56
> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA = EDH-DSS-DES-CBC3-SHA,DHE,DSS,3DES,SHA1,SSLv3,false,HIGH,true,168,168
> {code}
> Note that MechanismDatabase.properties is inconsistent in mapping DHE cipher suites to openssl cipher suites, as there also exist couple of them which map DHE to DHE, for example
> {code}
> TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 = DHE-RSA-AES128-SHA256,DHE,RSA,AES128,SHA256,TLSv1.2,false,HIGH,true,128,128
> TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 = DHE-RSA-AES256-SHA256,DHE,RSA,AES256,SHA256,TLSv1.2,false,HIGH,true,256,256
> TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 = DHE-RSA-AES128-GCM-SHA256,DHE,RSA,AES128GCM,AEAD,TLSv1.2,false,HIGH,true,128,128
> TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 = DHE-RSA-AES256-GCM-SHA384,DHE,RSA,AES256GCM,AEAD,TLSv1.2,false,HIGH,true,256,256
> {code}
> In MechanismDatabase.properties is also said that
> ??Note that all EDH ciphers automatically get a DHE OpenSSL-style alias (and vice-versa)??
> I think this JIRA contradict this comment.
> Last thing, based on [1] shouldn't be SSL_DHE_DSS_WITH_DES_CBC_SHA defined as
> SSL_DHE_DSS_WITH_DES_CBC_SHA = DHE-DSS-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56
> ?
> [1] https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-SUITE-NAMES
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1123304
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFCORE-3224) Rework batch related commands for better UX
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3224:
--------------------------------------------
Summary: Rework batch related commands for better UX
Key: WFCORE-3224
URL: https://issues.jboss.org/browse/WFCORE-3224
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
The batch command is difficult to use. The combination of options is not that obvious to use. Batch command is associated to a bunch of other commands (discard-batch, run-batch, …) that are somehow hidden. A new command should be introduce to clearly offer action for all batch related use cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFCORE-3223) Unify deployment operations
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3223?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise moved JBEAP-12945 to WFCORE-3223:
------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3223 (was: JBEAP-12945)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
(was: User Experience)
(was: Web Console)
Affects Version/s: (was: 7.1.0.DR8)
> Unify deployment operations
> ---------------------------
>
> Key: WFCORE-3223
> URL: https://issues.jboss.org/browse/WFCORE-3223
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Minor
>
> *Now*
> * Webconsole provides clear set of operations over deployment (disable, replace, remove, ...). It is clear always how to use them and where they are.
> * In CLI, the same operations can be called in different ways and some of them have different names in comparsion to webconsole.
> *Problem*
> * CLI deployment commands has lack of unified approach.
> Examples
> * Webconsole command: Disable
> ** undeploy --name=my-deployment --keep-content
> * Replace
> ** deploy --force /.../jboss-ejb-in-war.war --name=my-deployment.war --runtime-name=my-deployment.war
> * Remove
> ** undeploy --name=my-deployment
> * Explode
> ** /deployment=my-deployment.war:explode()
> * Browse content
> ** /deployment=my-deployment.war:browse-content()
>
> *Proposed solution*
> 1. Unify vocabulary, check following words at least:
> * disable vs. keep-content
> * replace vs. force
> 2. Provide CLI commands for explode and browse content as well, for example.
> * deployment-explode --name=my-deployment
> * deployment-browse-content --name=my-deployment
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFCORE-3222) CLI commands management
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3222:
--------------------------------------------
Summary: CLI commands management
Key: WFCORE-3222
URL: https://issues.jboss.org/browse/WFCORE-3222
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
With the evolution of CLI to support aesh 1.0 commands, we have new use cases that CLI needs to handle. For example, to take benefit of third-party aesh commands (eg: aesh-extensions), the CLI must be able to load commands dynamically.
Currently it is difficult or impossible to achieve the following use cases:
List all commands
List enabled commands
List disabled commands
List deprecated commands
List commands that are loaded from extensions
Display errors that occurred loading commands
List commands loaded from ServiceLoader
Load commands dynamically from a jar
Load commands dynamically from a module
A dedicated command should be designed to help achieve these use cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFCORE-3221) Support for | and >> operators
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3221:
--------------------------------------------
Summary: Support for | and >> operators
Key: WFCORE-3221
URL: https://issues.jboss.org/browse/WFCORE-3221
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Aesh 1.0 comes with a set of useful operators. 2 are of particular interest in CLI:
In order to extend the CLI ‘>’ support with the ability to append to a file, ‘>>’ support is required.
To make interesting combination of commands (eg: grep, cat, less), the ‘|’ operator is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Nuno Godinho de Matos edited comment on WFLY-8954 at 9/1/17 7:29 AM:
---------------------------------------------------------------------
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty "state" check to be run against a the wrong entity field.
However, the refresh action is being redundant. That is a very good indication.
I believe my impression above is nothing but a false negative.
We are still in the clear for now...
was (Author: nuno.godinhomatos):
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty Staless checks to be run against a the wrong entity field. I believe my impression above is nothing but a false negative.
We are still in the clear for now...
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
> Assignee: Scott Marlow
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Nuno Godinho de Matos edited comment on WFLY-8954 at 9/1/17 7:28 AM:
---------------------------------------------------------------------
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty Staless checks to be run against a the wrong entity field. I believe my impression above is nothing but a false negative.
We are still in the clear for now...
was (Author: nuno.godinhomatos):
No.
The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.
Not good...
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
> Assignee: Scott Marlow
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (WFCORE-3220) Enhanced help for CLI
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3220:
--------------------------------------------
Summary: Enhanced help for CLI
Key: WFCORE-3220
URL: https://issues.jboss.org/browse/WFCORE-3220
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Replace help text file by “on the fly” generation of help content. The source of input for this generation are the Command Annotations and Bundle files that contain descriptions.
Furthermore the help content currently doesn’t scale with the complexity of commands. The help has to be attached to command and command’s actions.
Low level operations usage is aligned with command documentation.
Both commands and operations help are available from the help command.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months