[JBoss JIRA] (WFLY-6946) Upgrade Infinispan to 8.2.4.Final
by Jason Greene (JIRA)
Jason Greene created WFLY-6946:
----------------------------------
Summary: Upgrade Infinispan to 8.2.4.Final
Key: WFLY-6946
URL: https://issues.jboss.org/browse/WFLY-6946
Project: WildFly
Issue Type: Component Upgrade
Components: Clustering
Affects Versions: 10.1.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Blocker
Fix For: 10.1.0.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6945) Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work
by James Perkins (JIRA)
James Perkins created WFLY-6945:
-----------------------------------
Summary: Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work
Key: WFLY-6945
URL: https://issues.jboss.org/browse/WFLY-6945
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.Final, 10.1.0.CR1
Reporter: jaikiran pai
Assignee: jaikiran pai
Java EE7 (which supports EL 3.0 spec) allows JSPs to use EL expressions like:
{code}
<html>
<body>
foo: --- ${Boolean.TRUE} ---<br>
bar: --- ${Integer.MAX_VALUE} ---<br>
</body>
</html>
{code}
However, the {code}${Boolean.TRUE}{code} and {code}${Integer.MAX_VALUE}{code} in the above example aren't evaluated correctly and instead a blank string is rendered for them.
More details in the linked forum thread https://developer.jboss.org/thread/271825
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1712) CLIScriptSupportTestCase fails on pure-IPv6 machines
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1712?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-5611 to WFCORE-1712:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1712 (was: JBEAP-5611)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Affects Version/s: (was: 7.1.0.DR1)
> CLIScriptSupportTestCase fails on pure-IPv6 machines
> ----------------------------------------------------
>
> Key: WFCORE-1712
> URL: https://issues.jboss.org/browse/WFCORE-1712
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> org.jboss.as.test.manualmode.management.cli.CLIScriptSupportTestCase#testConnectStatus fails on pure-IPv6 machines
> *How reproducible:*
> 100%
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # mvn install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dipv6 $PROXY_PARAMS -Dtest=CLIScriptSupportTestCase -Dts.manualmode -DfailIfNoTests=false
> *Actual results:*
> Stacktrace:
> {noformat}java.lang.IllegalStateException: Unable to connect to controller.
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:294)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:276)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:393)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:381)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:83)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:114)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:218)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:179)
> at org.jboss.as.cli.impl.CLIModelControllerClient$3.getChannel(CLIModelControllerClient.java:138)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1157)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1003)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:980)
> at org.jboss.as.cli.scriptsupport.CLI.doConnect(CLI.java:278)
> at org.jboss.as.cli.scriptsupport.CLI.connect(CLI.java:82)
> at org.jboss.as.test.manualmode.management.cli.CLIScriptSupportTestCase.testConnectStatus(CLIScriptSupportTestCase.java:87)
> Standard Output
> Standard Error
> 5.6 sec
> {noformat}
> Test output:
> {noformat}&#27;[0m09:15:56,815 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final-redhat-1
> &#27;[0m&#27;[0m09:15:57,137 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
> &#27;[0m&#27;[0m09:15:57,331 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" starting
> &#27;[0m&#27;[33m09:16:00,230 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /mnt/hudson_workspace/eap-7x-as-testsuite-test-core-rhel-ipv6-CLIScriptSupport/49bf0d07/testsuite/manualmode/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> &#27;[0m&#27;[0m09:16:00,413 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" started in 3532ms - Started 37 of 46 services (17 services are lazy, passive or on-demand)
> &#27;[0m09:16:00,477 INFO [org.jboss.as.cli.CommandContext] (main) Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> &#27;[0m09:16:00,699 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" stopped in 86ms
> &#27;[0m&#27;[0m09:16:00,715 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" starting
> &#27;[0m&#27;[0m09:16:00,943 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> &#27;[0m&#27;[0m09:16:01,083 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
> &#27;[0m&#27;[0m09:16:01,143 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
> &#27;[0m&#27;[33m09:16:01,438 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /mnt/hudson_workspace/eap-7x-as-testsuite-test-core-rhel-ipv6-CLIScriptSupport/49bf0d07/testsuite/manualmode/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> &#27;[0m&#27;[0m09:16:01,505 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.21.Final-redhat-1
> &#27;[0m&#27;[33m09:16:01,753 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-1) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
> &#27;[0m&#27;[0m09:16:01,944 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> &#27;[0m&#27;[0m09:16:01,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> &#27;[0m&#27;[0m09:16:01,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" started in 1221ms - Started 59 of 62 services (20 services are lazy, passive or on-demand)
> &#27;[0m&#27;[0m09:16:02,188 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" stopped in 55ms
> {noformat}
> *Expected results:*
> No errors
> *Additional info:*
> Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6871) Server fails to boot using locales not using arabic numerals for representation of numbers
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6871?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed WFLY-6871.
--------------------------------
> Server fails to boot using locales not using arabic numerals for representation of numbers
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-6871
> URL: https://issues.jboss.org/browse/WFLY-6871
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 10.1.0.CR1
>
>
> e.g. Hindu (hi_IN)
> {noformat}
> [rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ ./bin/standalone.sh -c standalone-ha.xml -Djboss.node.name=node1
> JAVA_OPTS already set in environment; overriding default settings with values: -Duser.country=IN -Duser.language=hi
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rhusar/wildfly/build/target/wildfly-10.1.0.Final-SNAPSHOT
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Duser.country=IN -Duser.language=hi
> =========================================================================
> १९:४७:२२,२४४ INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> १९:४७:२२,३९० INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> १९:४७:२२,४४९ INFO [org.jboss.as] (MSC service thread १-७) WFLYSRV0049: WildFly Core 2.2.0.CR8 "Kenny" starting
> १९:४७:२३,०४२ ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:357)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[388,9]
> Message: Unexpected element '{urn:jboss:domain:singleton:1.0}subsystem'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546)
> at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242)
> at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> १९:४७:२३,०४३ FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> १९:४७:२३,०५३ INFO [org.jboss.as] (MSC service thread १-४) WFLYSRV0050: WildFly Core 2.2.0.CR8 "Kenny" stopped in ६ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6944) Encode session affinity using multiple routes, if supported by the load balancer
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-6944:
----------------------------------
Summary: Encode session affinity using multiple routes, if supported by the load balancer
Key: WFLY-6944
URL: https://issues.jboss.org/browse/WFLY-6944
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, session affinity is specified as a single route, usually the primary owner of a session. However, if this node is not active (from the load balancer's perspective), then the load balancer will select another node of its choosing. This is less than ideal, since some nodes are more optimal than others. Better is to expression session affinity as an ordered list of nodes. The load balancer can then choose the 1st node in the list that is active, and cascade on failures accordingly. From the server's perspective, the affinity list should have the following order:
1. The primary owner
2. Any backup owners
3. The local node (if the local node is not an owner)
There are a couple of ways a load balancer can indicate that it supports multiple routes.
1. Static configuration
2. Adding an HTTP header to a proxied request, which can be detected by the server handling the request
#1 has the advantage of simplicity - but requires that users manually apply this configuration to gain optimal performance. This would also let us allow users (for even the single node affinity case) to toggle between local affinity or primary owner affinity, or even no routing.
#2 has the advantage of applying this optimization automatically, but incurs the cost of an additional header to every request
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months