[JBoss JIRA] (WFLY-12953) Delete any existing licenses.html before transforming to create a new one
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12953:
---------------------------------------
Summary: Delete any existing licenses.html before transforming to create a new one
Key: WFLY-12953
URL: https://issues.redhat.com/browse/WFLY-12953
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Brian Stansberry
Assignee: Brian Stansberry
If the transform task in the tasks.xml from the docs.licenses.merge galleon package from more than one f-p gets executed it will fail because the first task to run will create a licenses.html and 'transform' will fail if the target file already exists. So as a safety measure have the tasks delete any such file before doing the transform.
AIUI a fix for GAL-305 will remove the need for this by preventing more than one docs.licenses.merge package being provisioned, but having this in there will do no harm and makes things a bit more robust.
Also, remove the crufty 'alternative-tasks.xml' files from these docs.licenses.merge packages.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBMETA-418) Validation error with "jboss-web_14_0.xsd"
by Wolfgang Knauf (Jira)
[ https://issues.redhat.com/browse/JBMETA-418?page=com.atlassian.jira.plugi... ]
Wolfgang Knauf updated JBMETA-418:
----------------------------------
Description:
I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
version="14.0">
<context-root>MyWebProject</context-root>
</jboss-web>
{noformat}
Eclipse shows validation errors deep in jboss_web_14_0.xsd.
Unfortunately, I can not copy from nested validation errors.
So I will attach a screenshot and type one of the error lines:
{noformat}
sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
{noformat}
The reason seems to be that "jboss-web_14_0.xsd" imports two files:
* "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
* "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
was:
I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
version="14.0">
<context-root>MyWebProject</context-root>
</jboss-web>
{noformat}
Eclipse shows validation errors deep in jboss_web_14_0.xsd.
Unfortunately, I can not copy from nested validation errors.
So I will attach a screenshot and type one of the error lines:
sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
The reason seems to be that "jboss-web_14_0.xsd" imports two files:
* "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
* "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
> Validation error with "jboss-web_14_0.xsd"
> ------------------------------------------
>
> Key: JBMETA-418
> URL: https://issues.redhat.com/browse/JBMETA-418
> Project: JBoss Metadata
> Issue Type: Bug
> Components: web
> Affects Versions: 12.0.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Jean-Frederic Clere
> Priority: Major
> Attachments: validationerror.png
>
>
> I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
> version="14.0">
> <context-root>MyWebProject</context-root>
> </jboss-web>
> {noformat}
> Eclipse shows validation errors deep in jboss_web_14_0.xsd.
> Unfortunately, I can not copy from nested validation errors.
> So I will attach a screenshot and type one of the error lines:
> {noformat}
> sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
> {noformat}
> The reason seems to be that "jboss-web_14_0.xsd" imports two files:
> * "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
> * "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
> This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
> It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBMETA-418) Validation error with "jboss-web_14_0.xsd"
by Wolfgang Knauf (Jira)
[ https://issues.redhat.com/browse/JBMETA-418?page=com.atlassian.jira.plugi... ]
Wolfgang Knauf updated JBMETA-418:
----------------------------------
Description:
I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
version="14.0">
<context-root>MyWebProject</context-root>
</jboss-web>
{noformat}
Eclipse shows validation errors deep in jboss_web_14_0.xsd.
Unfortunately, I can not copy from nested validation errors.
So I will attach a screenshot and type one of the error lines:
sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
The reason seems to be that "jboss-web_14_0.xsd" imports two files:
* "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
* "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
was:
I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
{noformat}
{{<?xml version="1.0" encoding="UTF-8"?>
<jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
version="14.0">
<context-root>MyWebProject</context-root>
</jboss-web>}}
{noformat}
Eclipse shows validation errors deep in jboss_web_14_0.xsd.
Unfortunately, I can not copy from nested validation errors.
So I will attach a screenshot and type one of the error lines:
sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
The reason seems to be that "jboss-web_14_0.xsd" imports two files:
* "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
* "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
> Validation error with "jboss-web_14_0.xsd"
> ------------------------------------------
>
> Key: JBMETA-418
> URL: https://issues.redhat.com/browse/JBMETA-418
> Project: JBoss Metadata
> Issue Type: Bug
> Components: web
> Affects Versions: 12.0.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Jean-Frederic Clere
> Priority: Major
> Attachments: validationerror.png
>
>
> I build a "jboss-web.xml" file referencing jboss-web_14_0.xsd (bundled with WildFly 18), using Eclipse IDE:
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-web_14_0.xsd"
> version="14.0">
> <context-root>MyWebProject</context-root>
> </jboss-web>
> {noformat}
> Eclipse shows validation errors deep in jboss_web_14_0.xsd.
> Unfortunately, I can not copy from nested validation errors.
> So I will attach a screenshot and type one of the error lines:
> sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://xmlns.jcp.org/xml/ns/javaee,descriptionGroup'
> The reason seems to be that "jboss-web_14_0.xsd" imports two files:
> * "web-app_4_0.xsd" which imports "web-common_4_0.xsd" which imports "javaee_7.xsd".
> * "jboss-common_8_0.xsd" which imports "javaee_8.xsd"
> This is quite confusing, as the JavaEE8 standard has a lot of XSD files which import "javaee_7.xsd": [JavaEE schemas|https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/in...]
> It should work if "jboss-web_14_0.xsd" imports "jboss-common_7_1.xsd" and thus "javaee_7.xsd". I don't see any relevant differences beetween "jboss-common_7_1.xsd" and "jboss-common_8_0.xsd", so this should be possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 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:
----------------------------------------
Hello. I'm getting a bit desperate, because I can't find this info anywhere, so adding this comment here is my last hope.
Main question is: *In which version was that fix included?*
Background:
We started to get into this issue massively after datacenter changes (so the root cause is unrelated - probably connections are closed too eagerly on the DB side).
Some notable fragments from exceptions (issue happens while INVALIDATING a connection):
{{Caused by: java.lang.NullPointerException at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:461)}}
Depending on desired behavior (which us unknown to me), it either seems to be an issue in:
SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:461 and line 441.
or it could be the fact, that pool.getInternalStatistics() should not be nullified by another thread, while another thread is trying to do the same.
It's hard to tell not knowing the concept.
Please help...
> 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, 6 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:
----------------------------------------
And sorry for double comment :'(
> 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, 6 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:
----------------------------------------
Hello. I'm getting a bit desperate, because I can't find this info anywhere, so adding this comment here is my last hope.
Main question is: *In which version was that fix included?*
Background:
We started to get into this issue massively after datacenter changes (so the root cause is unrelated - probably connections are closed too eagerly on the DB side).
Some notable fragments from exceptions (issue happens while INVALIDATING a connection):
{{Caused by: java.lang.NullPointerException at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:461)}}
Depending on desired behavior (which us unknown to me), it either seems to be an issue in:
SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:461 and line 441.
or it could be the fact, that pool.getInternalStatistics() should not be nullified by another thread, while another thread is trying to do the same.
It's hard to tell not knowing the concept.
Please help...
> 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, 6 months
[JBoss JIRA] (WFLY-12941) Microprofile count metrics does not increase in wildfly17
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12941?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-12941:
---------------------------------------
Component/s: MP Metrics
Assignee: Jeff Mesnil (was: Brian Stansberry)
Thanks [~alireza.alallah] -- so I've set the component on this and assigned over the [~jmesnil] the component lead for MP Metrics.
My comment about 'statistics-enabled' isn't relevant to this one. :)
> Microprofile count metrics does not increase in wildfly17
> ----------------------------------------------------------
>
> Key: WFLY-12941
> URL: https://issues.redhat.com/browse/WFLY-12941
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: alireza alallah
> Assignee: Jeff Mesnil
> Priority: Major
>
> for example
> @Path("/")
> public class RESTEndpoints {
>
> @GET
> @Path("/hello")
> @Counted(name"total_count",absolute = true)
> public String hello(@DefaultValue("my friend!") @QueryParam("name") String name) {
> return "Hello "+name;
>
> }
>
> }
> Now in http://localhost:9990/metrics *total_count* metric does not increase after invoke endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months