[JBoss JIRA] (WFCORE-2712) Elytron - predefined-filter must have flag required in configurable-sasl-server-factory
by Josef Cacek (JIRA)
Josef Cacek created WFCORE-2712:
-----------------------------------
Summary: Elytron - predefined-filter must have flag required in configurable-sasl-server-factory
Key: WFCORE-2712
URL: https://issues.jboss.org/browse/WFCORE-2712
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Change the required flag to true for {{predefined-filter}} attribute in Elytron subsystem.
Elytron resource type {{configurable-sasl-server-factory}} has {{filters}} object-list attribute. Its attribute {{predefined-filter}} is an alternative for {{pattern-filter}} attribute. The {{pattern-filter}} has required flag set to true, but {{predefined-filter}} has it false. It results in possibility to add empty filter:
{code}
/subsystem=elytron/configurable-sasl-server-factory=t1:add(sasl-server-factory=elytron, filters=[{}])
{"outcome" => "success"}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
by rajendra rathore (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1534?page=com.atlassian.jira.plugi... ]
rajendra rathore updated DROOLS-1534:
-------------------------------------
Attachment: image001.png
Hi Mario,
I used tomcat 8.5.5 with ECJ 3.11.1.v20150902-1521 version and it working fine the drools 6.3.0 final.
Thanks and Regards,
Rajendra Rathore
9922701491
From: Mario Fusco (JIRA) [mailto:issues@jboss.org]
Sent: Friday, April 21, 2017 2:28 PM
To: Rathore, Rajendra <rarathore(a)ptc.com>
Subject: [JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
[https://static.jboss.org/developer/gravatar/9eafc29df96e6aaf4a3eb4c020908...]
Mario Fusco<https://issues.jboss.org/secure/ViewProfile.jspa?name=mfusco> commented on [Bug] DROOLS-1534<https://issues.jboss.org/browse/DROOLS-1534>
Re: Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)<https://issues.jboss.org/browse/DROOLS-1534>
I'm now afraid we're speaking about 2 different things. See here http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22ecj%22
Drools uses ecj artifact in group org.eclipse.jdt.core.compiler while I guess that Tomcat uses the one in org.eclipse.jdt. I'm no longer sure how the 2 things are related. Can you confirm this? Can you please check which version used the latest Tomcat that worked for you?
[Add Comment]<https://issues.jboss.org/browse/DROOLS-1534#add-comment>
Add Comment<https://issues.jboss.org/browse/DROOLS-1534#add-comment>
This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)
[Atlassian logo]
> Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1534
> URL: https://issues.jboss.org/browse/DROOLS-1534
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: rajendra rathore
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: drools exception.txt, image001.png, image001.png
>
>
> Hi Team,
> we upgrade our tomcat as daily update process, previously we are using tomcat 8.5.5 and now updated to 8.5.13, we found that after updating tomcat to 8.5.13 our drools rule are not working and attached the exception for your reference.
> We analyse the issue and found that *ecj.jar* is causing the issue, please let me know if there is any dependency with ECJ.jar, we are using 3.12.1.v20160829-0950 and it is bundled with tomcat 8.5.13.
> Please let me know if you have any workaround for this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1534?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1534:
-------------------------------------
I'm now afraid we're speaking about 2 different things. See here http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22ecj%22
Drools uses ecj artifact in group org.eclipse.jdt.core.compiler while I guess that Tomcat uses the one in org.eclipse.jdt. I'm no longer sure how the 2 things are related. Can you confirm this? Can you please check which version used the latest Tomcat that worked for you?
> Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1534
> URL: https://issues.jboss.org/browse/DROOLS-1534
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: rajendra rathore
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: drools exception.txt, image001.png
>
>
> Hi Team,
> we upgrade our tomcat as daily update process, previously we are using tomcat 8.5.5 and now updated to 8.5.13, we found that after updating tomcat to 8.5.13 our drools rule are not working and attached the exception for your reference.
> We analyse the issue and found that *ecj.jar* is causing the issue, please let me know if there is any dependency with ECJ.jar, we are using 3.12.1.v20160829-0950 and it is bundled with tomcat 8.5.13.
> Please let me know if you have any workaround for this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
by rajendra rathore (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1534?page=com.atlassian.jira.plugi... ]
rajendra rathore updated DROOLS-1534:
-------------------------------------
Attachment: image001.png
Hi Mario,
Can you please provide me the drool version which support ECJ 3.12.1?
Thanks and Regards,
Rajendra Rathore
9922701491
From: Mario Fusco (JIRA) [mailto:issues@jboss.org]
Sent: Friday, April 21, 2017 2:01 PM
To: Rathore, Rajendra <rarathore(a)ptc.com>
Subject: [JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
[https://static.jboss.org/developer/gravatar/9eafc29df96e6aaf4a3eb4c020908...]
Mario Fusco<https://issues.jboss.org/secure/ViewProfile.jspa?name=mfusco> resolved as Rejected
Drools 6.3 depends on ecj 4.3.1. More recent versions (6.5) require at least ecj 4.4.2 to fully support Java 8 syntax.
Ecj 3.12.1 that you claim is in use by your version of Tomcat seems to be pretty old. To be honest I don't know how and why oldest releases of Tomcat worked regardless of this problem. However this is not a drools issue and unfortunately I'm not aware of any workaround to fix this other than trying to force Tomcat to run with a different (more recent) ecj release.
Drools<https://issues.jboss.org/browse/DROOLS> / [Bug] <https://issues.jboss.org/browse/DROOLS-1534> DROOLS-1534<https://issues.jboss.org/browse/DROOLS-1534>
Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)<https://issues.jboss.org/browse/DROOLS-1534>
Change By:
Mario Fusco<https://issues.jboss.org/secure/ViewProfile.jspa?name=mfusco>
Status:
Open Resolved
Resolution:
Rejected
[Add Comment]<https://issues.jboss.org/browse/DROOLS-1534#add-comment>
Add Comment<https://issues.jboss.org/browse/DROOLS-1534#add-comment>
This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)
[Atlassian logo]
> Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1534
> URL: https://issues.jboss.org/browse/DROOLS-1534
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: rajendra rathore
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: drools exception.txt, image001.png
>
>
> Hi Team,
> we upgrade our tomcat as daily update process, previously we are using tomcat 8.5.5 and now updated to 8.5.13, we found that after updating tomcat to 8.5.13 our drools rule are not working and attached the exception for your reference.
> We analyse the issue and found that *ecj.jar* is causing the issue, please let me know if there is any dependency with ECJ.jar, we are using 3.12.1.v20160829-0950 and it is bundled with tomcat 8.5.13.
> Please let me know if you have any workaround for this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBJCA-1347) NullPointerException in SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1347?page=com.atlassian.jira.plugin... ]
Stefano Maestri reassigned JBJCA-1347:
--------------------------------------
Assignee: Stefano Maestri
> NullPointerException in SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441
> ------------------------------------------------------------------------------------
>
> Key: JBJCA-1347
> URL: https://issues.jboss.org/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: Stefano Maestri
>
> 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.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1534) Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1534?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1534.
---------------------------------
Resolution: Rejected
Drools 6.3 depends on ecj 4.3.1. More recent versions (6.5) require at least ecj 4.4.2 to fully support Java 8 syntax.
Ecj 3.12.1 that you claim is in use by your version of Tomcat seems to be pretty old. To be honest I don't know how and why oldest releases of Tomcat worked regardless of this problem. However this is not a drools issue and unfortunately I'm not aware of any workaround to fix this other than trying to force Tomcat to run with a different (more recent) ecj release.
> Facing issue with Drools 6.3.0 version while updating to tomcat(Specific to Window platform)
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1534
> URL: https://issues.jboss.org/browse/DROOLS-1534
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: rajendra rathore
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: drools exception.txt
>
>
> Hi Team,
> we upgrade our tomcat as daily update process, previously we are using tomcat 8.5.5 and now updated to 8.5.13, we found that after updating tomcat to 8.5.13 our drools rule are not working and attached the exception for your reference.
> We analyse the issue and found that *ecj.jar* is causing the issue, please let me know if there is any dependency with ECJ.jar, we are using 3.12.1.v20160829-0950 and it is bundled with tomcat 8.5.13.
> Please let me know if you have any workaround for this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years