[JBoss JIRA] (WFLY-3147) spec-descriptor-property-replacement causes NPE while parsing exclude element in beans.xml
by Maxim Frolov (JIRA)
[ https://issues.jboss.org/browse/WFLY-3147?page=com.atlassian.jira.plugin.... ]
Maxim Frolov commented on WFLY-3147:
------------------------------------
Bug in _weld-core-impl_-2.1.2.Final?
The [BeansXmlHandler|https://github.com/weld/core/blob/2.1.2.Final/impl/src/ma...] always calls interpolate(), even if the argument is _null_.
At runtime Wildfly calls interpolate() method which is overridden by [PropertyReplacingBeansXmlHandler|https://github.com/wildfly/wildfly/blob/...], which delegates processing to [DefaultPropertyReplacer|https://github.com/jboss/metadata/blob/8.0.0.Fina...]. Nowehere the null-check is performed.
I think, that the BeansXmlHandler should not call interpolate() method at all if the value of attribute or XML element is absent.
> spec-descriptor-property-replacement causes NPE while parsing exclude element in beans.xml
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-3147
> URL: https://issues.jboss.org/browse/WFLY-3147
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, EE
> Affects Versions: 8.0.0.Final
> Reporter: Maxim Frolov
> Assignee: Stuart Douglas
>
> A CDI Bean Archive with a _beans.xml_ which contains {{beans/scan/*exclude*}} XML element causes {{NullPointerExcpetion}} during deployment on server with enabled {{<spec-descriptor-property-replacement>}} parameter in server's _standalone.xml_.
> The error stack trace is:
> {noformat}
> 2014-03-21 11:22:52,455 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC000001: Failed to start service jboss.deployment.subunit."example.ear"."example-ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."example.ear"."example-ejb.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "example-ejb.jar" of deployment "example.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
> at org.jboss.as.weld.deployment.processors.BeansXmlProcessor.parseBeansXml(BeansXmlProcessor.java:140)
> at org.jboss.as.weld.deployment.processors.BeansXmlProcessor.deploy(BeansXmlProcessor.java:117)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.metadata.property.DefaultPropertyReplacer.replaceProperties(DefaultPropertyReplacer.java:52)
> at org.jboss.as.weld.deployment.PropertyReplacingBeansXmlHandler.interpolate(PropertyReplacingBeansXmlHandler.java:64)
> at org.jboss.weld.xml.BeansXmlHandler$4.processStartChildElement(BeansXmlHandler.java:229)
> at org.jboss.weld.xml.BeansXmlHandler.startElement(BeansXmlHandler.java:297)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
> at org.jboss.weld.xml.BeansXmlParser.parse(BeansXmlParser.java:93)
> at org.jboss.as.weld.deployment.processors.BeansXmlProcessor.parseBeansXml(BeansXmlProcessor.java:136)
> ... 7 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-2713) ViewExpiredException in Chrome on WildFly 8.0.0.CR1
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-2713?page=com.atlassian.jira.plugin.... ]
Farah Juma closed WFLY-2713.
----------------------------
Resolution: Out of Date
> ViewExpiredException in Chrome on WildFly 8.0.0.CR1
> ---------------------------------------------------
>
> Key: WFLY-2713
> URL: https://issues.jboss.org/browse/WFLY-2713
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.CR1
> Environment: WildFly 8.0.0.CR1
> Chrome 31.0.1650.63 @ Fedora 20 x86_64
> Reporter: Pavol Pitonak
> Assignee: Farah Juma
> Attachments: reproducer.zip
>
>
> # unzip attached reproducer
> # mvn clean package
> # deploy reproducer.war to WildFly
> # open http://localhost:8080/reproducer/
> # type something to the input
> result:
> * in Chrome, a popup with error is displayed
> * server console contains stack trace:
> {code}
> 17:10:54,852 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (default task-7) javax.faces.application.ViewExpiredException: viewId:/index.xhtml - View /index.xhtml could not be restored.
> {code}
> * works fine in Firefox 26
> * works fine in WildFly 8.0.0.Beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-2713) ViewExpiredException in Chrome on WildFly 8.0.0.CR1
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/WFLY-2713?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak commented on WFLY-2713:
-------------------------------------
No, I cannot reproduce anymore with WildFly 8.0.0.Final.
> ViewExpiredException in Chrome on WildFly 8.0.0.CR1
> ---------------------------------------------------
>
> Key: WFLY-2713
> URL: https://issues.jboss.org/browse/WFLY-2713
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.CR1
> Environment: WildFly 8.0.0.CR1
> Chrome 31.0.1650.63 @ Fedora 20 x86_64
> Reporter: Pavol Pitonak
> Assignee: Farah Juma
> Attachments: reproducer.zip
>
>
> # unzip attached reproducer
> # mvn clean package
> # deploy reproducer.war to WildFly
> # open http://localhost:8080/reproducer/
> # type something to the input
> result:
> * in Chrome, a popup with error is displayed
> * server console contains stack trace:
> {code}
> 17:10:54,852 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (default task-7) javax.faces.application.ViewExpiredException: viewId:/index.xhtml - View /index.xhtml could not be restored.
> {code}
> * works fine in Firefox 26
> * works fine in WildFly 8.0.0.Beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1759:
--------------------------------
After running another 20 test suite runs, this test *never* failed. I did submit the PR to Byteman though and will use rendezvous with a timeout once this is folded into a new Byteman release. Pushing this to 4.0.
> BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
> ----------------------------------------------------------------
>
> Key: JGRP-1759
> URL: https://issues.jboss.org/browse/JGRP-1759
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows 2008, x86_64
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang.
> The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks.
> .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1759:
---------------------------
Fix Version/s: 4.0
(was: 3.5)
> BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
> ----------------------------------------------------------------
>
> Key: JGRP-1759
> URL: https://issues.jboss.org/browse/JGRP-1759
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows 2008, x86_64
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang.
> The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks.
> .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1775) Relay2Test.testQueueingAndForwarding fails randomly
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1775?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1775.
----------------------------
Resolution: Won't Fix
I'm afraid I won't fix this in 3.5 as that test doesn't exist anymore.
> Relay2Test.testQueueingAndForwarding fails randomly
> ---------------------------------------------------
>
> Key: JGRP-1775
> URL: https://issues.jboss.org/browse/JGRP-1775
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.3.5
> Reporter: Risto Oikarinen
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
> Attachments: relay2test_fails_randomly_log.txt
>
>
> Relay2Test.testQueueingAndForwarding seems to be failing randomly. I was able to reproduce this with the following test:
> {code:java}
> public void testQueueInLoop() throws Exception {
> for ( int i = 0; i < 1000; ++i) {
> testQueueingAndForwarding();
> destroy();
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1750) RELAY2 : Address formats are not relayed.
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1750?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1750.
----------------------------
Resolution: Done
[~ammous] Let me know if this works now, and reopen if it doesn't.
> RELAY2 : Address formats are not relayed.
> -----------------------------------------
>
> Key: JGRP-1750
> URL: https://issues.jboss.org/browse/JGRP-1750
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.4.1
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> When defining a relay channel, we haven't the ability to set an AddressGenrator. Indeed, the Relayer uses its own AddressGenerator providing addresses of type SiteUUID.
> This is particularly embarrassing in the following case: when we define a customized address format (like CanBeSiteMasterTopology or TopologyUUID) for members of two Sites A and B, address format is lost by crossing relay. Address type of messages sent by A to B are seen as SiteUUID at B side.
> Suggestions:
> - Making address format "relayable" ?
> - Using the same (or an extended format) AddressGenerator of site Channel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-2713) ViewExpiredException in Chrome on WildFly 8.0.0.CR1
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-2713?page=com.atlassian.jira.plugin.... ]
Farah Juma commented on WFLY-2713:
----------------------------------
[~ppitonak] Are you still able to reproduce this? I just tried with the latest WildFly 8.0.1.Final-SNAPSHOT version (i.e., rev 84638b1a4f4705875dfaaf72cd6decd9342394fc) and with Chrome 33.0.1750.152 but wasn't able to reproduce this issue.
> ViewExpiredException in Chrome on WildFly 8.0.0.CR1
> ---------------------------------------------------
>
> Key: WFLY-2713
> URL: https://issues.jboss.org/browse/WFLY-2713
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.CR1
> Environment: WildFly 8.0.0.CR1
> Chrome 31.0.1650.63 @ Fedora 20 x86_64
> Reporter: Pavol Pitonak
> Assignee: Farah Juma
> Attachments: reproducer.zip
>
>
> # unzip attached reproducer
> # mvn clean package
> # deploy reproducer.war to WildFly
> # open http://localhost:8080/reproducer/
> # type something to the input
> result:
> * in Chrome, a popup with error is displayed
> * server console contains stack trace:
> {code}
> 17:10:54,852 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (default task-7) javax.faces.application.ViewExpiredException: viewId:/index.xhtml - View /index.xhtml could not be restored.
> {code}
> * works fine in Firefox 26
> * works fine in WildFly 8.0.0.Beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months