[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.
by Nikos Tsekouras (Jira)
[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ]
Nikos Tsekouras commented on DROOLS-4960:
-----------------------------------------
Hi [~manstis] / [~Rikkola],
Thanks but I configured MVN offline in BRMS.
So, maybe that's the reason I cannot use Michael's solution.
Is there any way to use the same in "MVN offline" version?
> Reference a data object from one project to another one.
> --------------------------------------------------------
>
> Key: DROOLS-4960
> URL: https://issues.redhat.com/browse/DROOLS-4960
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 7.31.0.Final
> Reporter: Nikos Tsekouras
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Currently, nothing can be referenced from one project to another one.
> Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful.
> Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package
by Nikos Tsekouras (Jira)
[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ]
Nikos Tsekouras commented on DROOLS-4959:
-----------------------------------------
Hi [~Rikkola],
Please find attached the process I used to reproduce this.
> Package name does not changes on copying of an existing package
> ---------------------------------------------------------------
>
> Key: DROOLS-4959
> URL: https://issues.redhat.com/browse/DROOLS-4959
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.31.0.Final
> Reporter: Nikos Tsekouras
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: step1.PNG, step2.PNG, step3.PNG, step4.PNG
>
>
> After copying a package to a new one, all copied resources will remain referencing the existing one.
> This becomes a bigger issue once you use guided rules, which their source cannot be edited.
> Due to that, duplication alerts will be raised.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JBJCA-1347) NullPointerException in SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441
by Piotr Krokowski (Jira)
[ https://issues.redhat.com/browse/JBJCA-1347?page=com.atlassian.jira.plugi... ]
Piotr Krokowski commented on JBJCA-1347:
----------------------------------------
Looks like a duplicate. It might be helpful to someone in the future to find this relation - took me a while :)
BTW. It's fixed in 1.3.3 (this piece of information is missing here).
> NullPointerException in SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441
> ------------------------------------------------------------------------------------
>
> Key: JBJCA-1347
> URL: https://issues.redhat.com/browse/JBJCA-1347
> Project: IronJacamar
> Issue Type: Bug
> Affects Versions: WildFly/IronJacamar 1.3.2.Final
> Environment: CentOS 6
> Wildfly 10.0.0.Final (Iron Jacamar 1.3.2.Final)
> PostgreSQL Server 9.5.5
> PostgreSQL JDBC driver 9.4.1208 and tried with 42.0.0
> Oracle Java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> Reporter: Brett Delle Grazie
> Assignee: Flavia Rainone
> Priority: Major
>
> Using a PostgreSQL XA datasource with statistics enabled we get a NullPointerException if the connection fails temporarily.
> With JDBC driver 9.4.1208 Wildfly never reconnects to the PostgreSQL server with the next request and Wildfly must be restarted. With JDBC driver 42.0.0 it does reconnect on next request.
> If statistics are disabled, the NPE does not occur and both drivers reconnect on the next request as expected.
> Specific location of NPE:
> https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.2.Final/c...
> Note there is similar code on line 461 of the same class (in the exception handler)
> Example configuration follows
> With a PostgreSQL datasource configured in Wildfly as:
> {code:xml}
> <xa-datasource jndi-name="java:/DS.people" pool-name="DS.people" enabled="true" spy="true" statistics-enabled="true" use-java-context="true" use-ccm="true">
> <driver>postgresql</driver>
> <xa-datasource-property name="ServerName">localhost</xa-datasource-property>
> <xa-datasource-property name="PortNumber">5432</xa-datasource-property>
> <xa-datasource-property name="DatabaseName">peopleviewstore</xa-datasource-property>
> <xa-datasource-property name="ApplicationName">people</xa-datasource-property>
> <xa-datasource-property name="assumeMinServerVersion">9.5</xa-datasource-property>
> <xa-datasource-property name="connectTimeout">10</xa-datasource-property>
> <xa-datasource-property name="currentSchema">public</xa-datasource-property>
> <xa-datasource-property name="hostRecheckSeconds">10</xa-datasource-property>
> <xa-datasource-property name="loginTimeout">10</xa-datasource-property>
> <xa-datasource-property name="logUnclosedConnections">true</xa-datasource-property>
> <xa-datasource-property name="socketTimeout">30</xa-datasource-property>
> <xa-datasource-property name="targetServerType">master</xa-datasource-property>
> <xa-datasource-property name="tcpKeepAlive">true</xa-datasource-property>
> <xa-pool>
> <min-pool-size>0</min-pool-size>
> <initial-pool-size>0</initial-pool-size>
> <max-pool-size>10</max-pool-size>
> <allow-multiple-users>false</allow-multiple-users>
> </xa-pool>
> <timeout>
> <xa-resource-timeout>0</xa-resource-timeout>
> </timeout>
> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
> <statement>
> <track-statements>true</track-statements>
> </statement>
> <security>
> <user-name></user-name>
> <password></password>
> </security>
> <validation>
> <validate-on-match>true</validate-on-match>
> <use-fast-fail>true</use-fast-fail>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> </validation>
> </xa-datasource>
> {code}
> And corresponding driver configuration:
> {code:xml}
> <driver name="postgresql" module="org.postgresql">
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> </driver>
> {code}
> we have deployed the JDBC driver as a module, module.xml looks like:
> {code:xml}
> <?xml version="1.0" ?>
> <module xmlns="urn:jboss:module:1.3" name="org.postgresql" slot="main">
> <resources>
> <resource-root path="postgresql-42.0.0.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> </dependencies>
> </module>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFWIP-300) Boot time of application built via S2I is much longer than in before-Galleon times
by Petr Kremensky (Jira)
Petr Kremensky created WFWIP-300:
------------------------------------
Summary: Boot time of application built via S2I is much longer than in before-Galleon times
Key: WFWIP-300
URL: https://issues.redhat.com/browse/WFWIP-300
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Petr Kremensky
Assignee: Jean Francois Denise
Attachments: test-app.zip
As a consequence of Galleon RFEs EAP7-891 and mainly EAP7-1216 there is big difference in pod with EAP application start up time which requires S2I configuration.
This is an overview of quick comparison of average boot times of the application pods of the attached test app (we are not interested in build/deploy pod times etc):
||17.0-6||pod time||EAP boot||config time
|#1 | 8283|6128|2155
|#2 | 9446|7548|1898
|#3 | 8767|6871| 1896
|#4 | 8568|6272| 2296
|#5 | 8000 |6362|1638
||average ||8613ms||6636ms||1977ms
||18.0-7||pod time||EAP boot||config time
|#1 |13769|5716|8053
|#2 |13362|5952|7410
|#3 |14261|6093|8168
|#4 |14322|6135|8187
|#5 |13921|6326|7595
||average||13927ms||6044ms||7883ms
pod time = time from the pod start until EAP is fully booted (log contains {{started in ..}})
EAP boot = time of boot EAP itself == {{started in ..}}
config time = the difference of previou timess = anything before EAP boot begins
Again we are talking here about the time needed for prepared application image to full start. We can clearly see the EAP boot times are comparable between 17 and 18 images but the configs times are almost 4 times longer with CD18 images.
This is very unfortunate as in my point of view the pod boot time is the most critical time for our users - they would typically prepare the app images only once in a time but their application can scale up and down many times during its uptime.
The cause of this that when S2I is needed with image 18.0+ the part of the configuration that was previously done during S2I build just once is now processed on *each* pod start.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected header cell
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4585?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-4585:
-------------------------------
Summary: Focus doesn't moves after the selected header cell (was: Focus doesn't moves after the selected cell)
> Focus doesn't moves after the selected header cell
> --------------------------------------------------
>
> Key: DROOLS-4585
> URL: https://issues.redhat.com/browse/DROOLS-4585
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.28.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus, drools-tools
>
> {color:red}*Failure*{color}
> If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
> *Expected*
> Viewed part of grid follows the selected cell
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute
by Masafumi Miura (Jira)
[ https://issues.redhat.com/browse/WFLY-13003?page=com.atlassian.jira.plugi... ]
Masafumi Miura edited comment on WFLY-13003 at 1/23/20 5:53 AM:
----------------------------------------------------------------
I've already raised UNDERTOW-1600 which is related to this feature.
I've just updated a PR for UNDERTOW-1600 https://github.com/undertow-io/undertow/pull/816 which contains the following changes:
- Add support for the SameSite=None attribute
- Add SameSiteCookieHandler that can set the SameSite attribute on all cookies
- Add a utility class SameSiteNoneIncompatibleClientChecker to detect user agents which are incompatible with the SameSite=None attribute. The regex is based on https://www.chromium.org/updates/same-site/incompatible-clients
The SameSiteCookieHandler can be enabled with the predicate name "samesite-cookie" through expression-filter in the undertow subsystem. For example:
{code:xml}
<subsystem xmlns="urn:jboss:domain:undertow:7.0" ...>
...
<server name="default-server">
...
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker security-realm="ApplicationRealm"/>
<!-- <filter-ref name="dump-request"/> -->
<filter-ref name="samesite-cookie"/> <!-- add this -->
</host>
</server>
...(snip)...
<filters>
<!-- <expression-filter name="dump-request" expression="dump-request"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=strict)"/> <!-- add this -->
<!-- or add the following for Lax or None attribute -->
<!-- <expression-filter name="samesite-cookie" expression="samesite-cookie(mode=lax)"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=none)"/>
</filters>
</subsystem>
{code}
was (Author: mmiura):
I've already raised UNDERTOW-1600 which is related to this feature.
I've just updated a PR for UNDERTOW-1600 https://github.com/undertow-io/undertow/pull/816 which contains the following changes:
- Add support for the SameSite=None attribute
- Add SameSiteCookieHandler that can set the SameSite attribute on all cookies
- Add a utility class SameSiteNoneIncompatibleClientChecker to detect user agents which are incompatible with the SameSite=None attribute
The SameSiteCookieHandler can be enabled with the predicate name "samesite-cookie" through expression-filter in the undertow subsystem. For example:
{code:xml}
<subsystem xmlns="urn:jboss:domain:undertow:7.0" ...>
...
<server name="default-server">
...
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker security-realm="ApplicationRealm"/>
<!-- <filter-ref name="dump-request"/> -->
<filter-ref name="samesite-cookie"/> <!-- add this -->
</host>
</server>
...(snip)...
<filters>
<!-- <expression-filter name="dump-request" expression="dump-request"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=strict)"/> <!-- add this -->
<!-- or add the following for Lax or None attribute -->
<!-- <expression-filter name="samesite-cookie" expression="samesite-cookie(mode=lax)"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=none)"/>
</filters>
</subsystem>
{code}
> Support the SameSite cookie attribute
> -------------------------------------
>
> Key: WFLY-13003
> URL: https://issues.redhat.com/browse/WFLY-13003
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Flavia Rainone
> Priority: Major
>
> Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2].
> At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code).
> I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set.
> This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis.
> [1] https://www.chromestatus.com/feature/5088147346030592
> [2] https://web.dev/samesite-cookies-explained/
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute
by Masafumi Miura (Jira)
[ https://issues.redhat.com/browse/WFLY-13003?page=com.atlassian.jira.plugi... ]
Masafumi Miura edited comment on WFLY-13003 at 1/23/20 5:38 AM:
----------------------------------------------------------------
I've already raised UNDERTOW-1600 which is related to this feature.
I've just updated a PR for UNDERTOW-1600 https://github.com/undertow-io/undertow/pull/816 which contains the following changes:
- Add support for the SameSite=None attribute
- Add SameSiteCookieHandler that can set the SameSite attribute on all cookies
- Add a utility class SameSiteNoneIncompatibleClientChecker to detect user agents which are incompatible with the SameSite=None attribute
The SameSiteCookieHandler can be enabled with the predicate name "samesite-cookie" through expression-filter in the undertow subsystem. For example:
{code:xml}
<subsystem xmlns="urn:jboss:domain:undertow:7.0" ...>
...
<server name="default-server">
...
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker security-realm="ApplicationRealm"/>
<!-- <filter-ref name="dump-request"/> -->
<filter-ref name="samesite-cookie"/> <!-- add this -->
</host>
</server>
...(snip)...
<filters>
<!-- <expression-filter name="dump-request" expression="dump-request"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=strict)"/> <!-- add this -->
<!-- or add the following for Lax or None attribute -->
<!-- <expression-filter name="samesite-cookie" expression="samesite-cookie(mode=lax)"/> -->
<expression-filter name="samesite-cookie" expression="samesite-cookie(mode=none)"/>
</filters>
</subsystem>
{code}
was (Author: mmiura):
I've already raised UNDERTOW-1600 which is related to this feature.
I've just updated a PR for UNDERTOW-1600 https://github.com/undertow-io/undertow/pull/816 which contains the following changes:
- Add support for the SameSite=None attribute
- Add SameSiteCookieHandler that can set the SameSite attribute on all cookies
- Add a utility class SameSiteNoneIncompatibleClientChecker to detect user agents which are incompatible with the SameSite=None attribute
> Support the SameSite cookie attribute
> -------------------------------------
>
> Key: WFLY-13003
> URL: https://issues.redhat.com/browse/WFLY-13003
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Flavia Rainone
> Priority: Major
>
> Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2].
> At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code).
> I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set.
> This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis.
> [1] https://www.chromestatus.com/feature/5088147346030592
> [2] https://web.dev/samesite-cookies-explained/
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months