[JBoss JIRA] (WFLY-6849) Duplicate messages in replicated HA topology when backup is shutdowned
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6849?page=com.atlassian.jira.plugin.... ]
Kabir Khan resolved WFLY-6849.
------------------------------
Fix Version/s: 11.0.0.Final
Resolution: Done
> Duplicate messages in replicated HA topology when backup is shutdowned
> ----------------------------------------------------------------------
>
> Key: WFLY-6849
> URL: https://issues.jboss.org/browse/WFLY-6849
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Baranowski
> Assignee: Clebert Suconic
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 11.0.0.Final
>
>
> Scenario
> # Configure 2 nodes in replicated dedicated topology
> # Start live (node-1) and backup (node-2)
> # Start producer
> # Shut down node-2
> # Stop producer
> # Check if there are some duplicates on node-1 using CLI operation list-messages
> Expectation: there is no duplications
> Actual state: there are 10 messages with the same _AMQ_DUPL_ID twice
> After that Backup is shut downed, the Live is not able to replicate its data to Backup. It waits 30 seconds until timeouts expire. Meanwhile producer does not get response from Live and it gets TimeoutException on commit. It retries to send the same batch of messages and then commit them again. I think that problem is at this point. The Live does not detect duplicate messages.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-6263) Apostrophe in an attribute with multiple EL parts breaks function lookup
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6263?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-6263:
-----------------------------
Fix Version/s: 12.0.0.Final
> Apostrophe in an attribute with multiple EL parts breaks function lookup
> ------------------------------------------------------------------------
>
> Key: WFLY-6263
> URL: https://issues.jboss.org/browse/WFLY-6263
> Project: WildFly
> Issue Type: Bug
> Components: EE, Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Paul Pogonyshev
> Assignee: Tomaz Cerar
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 12.0.0.Final
>
> Attachments: jastow-bug.war.zip, jastow.diff
>
>
> Certain EL pieces result in unexplained org.apache.jasper.JasperException "contains invalid expression(s)" (the exception _does not_ explain what is invalid). After lots of tries, I have narrowed it down: 1) there must be several EL pieces in one string; 2) there must be an apostrophe in between.
> This looks very similar to bug WFLY-4455. It breaks several pages in our application, blocking upgrade to WildFly 10.
> Example is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4096.
----------------------------
Resolution: Out of Date
> Datasource Defined in web.xml Does Not Work with JPA Entity Manager
> -------------------------------------------------------------------
>
> Key: WFLY-4096
> URL: https://issues.jboss.org/browse/WFLY-4096
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Environment: Windows 7
> Java 8u25
> WildFly 8.1.0.Final
> Reporter: shinzey shinzey
> Assignee: Scott Marlow
> Priority: Critical
> Labels: datasource, deployment, jpa, persistence.xml, persistenceUnit
>
> The datasource defined in web.xml:
> {quote}
> <data-source>
> <name>java:/datasources/test</name>
> <class-name>org.apache.derby.jdbc.ClientDataSource</class-name>
> <database-name>test</database-name>
> <url>jdbc:derby://localhost:1527/test</url>
> <user>test</user>
> <password>test</password>
> </data-source>
> {quote}
> The persistence unit:
> {quote}
> <persistence-unit name="wtpu" transaction-type="JTA">
> <jta-data-source>java:/datasources/test</jta-data-source>
> </persistence-unit>
> {quote}
> The deployment error:
> {quote}
> 17:57:10,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "WebTest.war" (runtime-name: "WebTest.war")
> 17:57:11,078 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for wtpu
> 17:57:11,172 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "WebTest.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"WebTest.war#wtpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.datasources.test]"])
> 17:57:11,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "WebTest.war" (runtime-name : "WebTest.war")
> 17:57:11,187 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.naming.context.java.datasources.test (missing) dependents: [service jboss.persistenceunit."WebTest.war#wtpu".__FIRST_PHASE__]
> {quote}
> If I remove the persistence unit, the datasource can be successfully bound:
> {quote}
> 17:55:47,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/datasources/test]
> {quote}
> The same code works as expected in GlassFish 4.1, and the @DataSourceDefinition annotation has the same issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-4212) REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4212?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4212.
----------------------------
Resolution: Out of Date
> REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
> -------------------------------------------------------------
>
> Key: WFLY-4212
> URL: https://issues.jboss.org/browse/WFLY-4212
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Jason Greene
> Priority: Critical
> Attachments: 8.1.0-cluster_logs.2014-12-31T04-01-53.tar.gz, 8.2.0-cluster_logs.2014-12-31T04-19-06.tar.gz
>
>
> While testing an upgrade to 8.2.0 a multi-component integration test that worked on 8.1.0 failed to deploy.
> A distilled clean-room test case reproducing the problem is located here: https://github.com/arcivanov/misc/tree/WFCORE-488/WFCORE-488
> This bug is also accompanied by the failure to undeploy partial deployment in WFCORE-488, although at present the above test case not yet reproduces the behavior.
> The deployment error on 8.2.0 is as follows:
> {noformat}
> 2014-12-31 04:17:11,877 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."bf40aa60-1792-473b-bc2c-344adf89790c.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_25]
> ... 3 more
> 2014-12-31 04:17:11,886 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "bf40aa60-1792-473b-bc2c-344adf89790c.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> 2014-12-31 04:17:11,889 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 66) JBAS015870: Deploy of deployment "bf40aa60-1792-473b-bc2c-344adf89790c.ear" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"bf40aa60-1792-473b-bc2c-344adf89790c.ear\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DateGenerator with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private wfcore488.ejb.ExampleEjb.dateGen
> at wfcore488.ejb.ExampleEjb.dateGen(ExampleEjb.java:0)
> "}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-4096:
----------------------------------
[~smarlow] [~shinzey] I am closing this because it is so old and I don't think it is being looked at
> Datasource Defined in web.xml Does Not Work with JPA Entity Manager
> -------------------------------------------------------------------
>
> Key: WFLY-4096
> URL: https://issues.jboss.org/browse/WFLY-4096
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Environment: Windows 7
> Java 8u25
> WildFly 8.1.0.Final
> Reporter: shinzey shinzey
> Assignee: Scott Marlow
> Priority: Critical
> Labels: datasource, deployment, jpa, persistence.xml, persistenceUnit
>
> The datasource defined in web.xml:
> {quote}
> <data-source>
> <name>java:/datasources/test</name>
> <class-name>org.apache.derby.jdbc.ClientDataSource</class-name>
> <database-name>test</database-name>
> <url>jdbc:derby://localhost:1527/test</url>
> <user>test</user>
> <password>test</password>
> </data-source>
> {quote}
> The persistence unit:
> {quote}
> <persistence-unit name="wtpu" transaction-type="JTA">
> <jta-data-source>java:/datasources/test</jta-data-source>
> </persistence-unit>
> {quote}
> The deployment error:
> {quote}
> 17:57:10,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "WebTest.war" (runtime-name: "WebTest.war")
> 17:57:11,078 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for wtpu
> 17:57:11,172 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "WebTest.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"WebTest.war#wtpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.datasources.test]"])
> 17:57:11,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "WebTest.war" (runtime-name : "WebTest.war")
> 17:57:11,187 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.naming.context.java.datasources.test (missing) dependents: [service jboss.persistenceunit."WebTest.war#wtpu".__FIRST_PHASE__]
> {quote}
> If I remove the persistence unit, the datasource can be successfully bound:
> {quote}
> 17:55:47,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/datasources/test]
> {quote}
> The same code works as expected in GlassFish 4.1, and the @DataSourceDefinition annotation has the same issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-3335) JAXB transformer initiation
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3335?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-3335.
----------------------------
> JAXB transformer initiation
> ---------------------------
>
> Key: WFLY-3335
> URL: https://issues.jboss.org/browse/WFLY-3335
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.0.0.Final, 8.1.0.CR1
> Environment: Ubuntu 14.04 with java 7 openjdk
> Reporter: Ghet Ghetolay
> Assignee: David Lloyd
> Priority: Critical
>
> I'm not directly using JAXB and SaxTransformer, it's part of a the [dcm4chee-arc project|https://github.com/dcm4che/dcm4chee-arc] which I tried to use on Wildfly. It's a rather big and complicated project so I've create a test application to illustrate the bug. I've used a JAR-RS application to illustrate the bug (like the original case) but this should not be related to it.
> {code:title=TestRS.java}
> @Path("test")
> public class TestRS {
>
> private static SAXTransformerFactory factory =
> (SAXTransformerFactory) TransformerFactory.newInstance();
>
> @GET
> public Response test(){
> try {
> Templates template = factory.newTemplates(new StreamSource(
> TestRS.class.getResource("json_compact.xsl").toString()));
>
> factory.newTransformerHandler(template);
>
> } catch (TransformerConfigurationException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> return Response.ok().build();
> }
> }
> {code}
> {code:title=json_compact.xsl}
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
> <xsl:output method="text"/>
> <xsl:template match="/">
> <xsl:text>Test</xsl:text>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {quote}
> 15:24:48,564 ERROR [stderr] (default task-1) javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> 15:24:48,564 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformerHandler(TransformerFactoryImpl.java:1062)
> 15:24:48,565 ERROR [stderr] (default task-1) at __redirected.__TransformerFactory.newTransformerHandler(__TransformerFactory.java:193)
> 15:24:48,566 ERROR [stderr] (default task-1) at test.TestRS.test(TestRS.java:25)
> {quote}
> I've discovered that the initial exception is :
> {quote}
> java.lang.NoClassDefFoundError: com/sun/org/apache/xalan/internal/xsltc/runtime/AbstractTranslet
> {quote}
> Both my test case and dcm4che-arc project works fine on JBoss 7.1.1.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3569?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-3569.
------------------------------
> NPE is shown in server shutdown
> -------------------------------
>
> Key: WFCORE-3569
> URL: https://issues.jboss.org/browse/WFCORE-3569
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, IO, Server
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: David Lloyd
> Priority: Critical
>
> NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
> Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
> {noformat}
> 13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
> at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
> at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
> at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Kabir Khan resolved WFCORE-3321.
--------------------------------
Fix Version/s: 3.0.10.Final
Resolution: Done
Just hazarding a guess at the fix version from the info on this issue
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Fix For: 3.0.10.Final
>
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-3321.
------------------------------
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Fix For: 3.0.10.Final
>
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month