Possible component upgrades report - Wildfly Core
by thofman＠redhat.com
Generated at 16:49:29 SGT 2019-12-08
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.googlecode.javaewah:JavaEWAH:1.1.6 -> 1.1.7 (Central)
com.jcraft:jsch:0.1.54 -> 0.1.55 (Central)
com.jcraft:jzlib:1.1.1 -> 1.1.3 (Central)
org.apache.httpcomponents:httpclient:4.5.4 -> 4.5.10 (Central)
org.apache.httpcomponents:httpcore:4.4.5 -> 4.4.12 (Central)
org.eclipse.jgit:org.eclipse.jgit:5.0.2.201807311906-r -> 5.0.3.201809091024-r (Central)
org.jboss:jandex:2.1.1.Final -> 2.1.2.Final (Central)
org.jboss.slf4j:slf4j-jboss-logmanager:1.0.3.GA -> 1.0.4.GA (Central)
org.slf4j:jcl-over-slf4j:1.7.22.jbossorg-1 -> 1.7.29 (Central)
9 items
6 years
Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:48:16 SGT 2019-12-08
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.google.code.gson:gson:2.8.2 -> 2.8.6 (Central)
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.istack:istack-commons-runtime:3.0.7 -> 3.0.10 (Central)
com.sun.xml.bind.external:relaxng-datatype:2.3.1 -> 2.3.2 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.17 (Central)
io.netty:netty-all:4.1.42.Final -> 4.1.43.Final (Central)
io.opentracing.contrib:opentracing-interceptors:0.0.4 -> 0.0.5 (Central)
io.opentracing.contrib:opentracing-tracerresolver:0.1.5 -> 0.1.8 (Central)
io.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.15 (Central)
io.smallrye:smallrye-config:1.3.6 -> 1.3.11 (Central)
io.smallrye:smallrye-opentracing:1.3.0 -> 1.3.2 (Central)
io.undertow.js:undertow-js:1.0.2.Final -> 1.0.3.Final (Central)
joda-time:joda-time:2.9.7 -> 2.9.9 (Central)
net.bytebuddy:byte-buddy:1.9.11 -> 1.9.16 (Central)
org.apache.activemq:activemq-artemis-native:1.0.0 -> 1.0.1 (Central)
org.apache.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.james:apache-mime4j:0.6 -> 0.6.1 (Central)
org.apache.myfaces.core:myfaces-api:2.3.1 -> 2.3.6 (Central)
org.apache.openjpa:openjpa-kernel:2.4.2 -> 2.4.3 (Central)
org.apache.qpid:proton-j:0.33.2 -> 0.33.3 (Central)
org.cryptacular:cryptacular:1.2.0 -> 1.2.3 (Central)
org.eclipse.microprofile.metrics:microprofile-metrics-api:2.0.2 -> 2.0.3 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.3.2 -> 1.3.4 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.5 (Central)
org.glassfish.jaxb:codemodel:2.3.1 -> 2.3.2-1 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.8.Final (Central)
org.jasypt:jasypt:1.9.2 -> 1.9.3 (Central)
org.jboss.activemq.artemis.integration:artemis-wildfly-integration:1.0.2 -> 1.0.2-wildfly-1 (JBossPublic)
org.jboss.arquillian.container:arquillian-container-test-spi:1.4.0.Final -> 1.4.1.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec:3.0.0.SP01 -> 3.0.0.SP1 (Central)
org.jgroups:jgroups:4.1.6.Final -> 4.1.8.Final (Central)
org.jgroups.kubernetes:jgroups-kubernetes:1.0.13.Final -> 1.0.14.Final (Central)
org.opensaml:opensaml-core:3.3.0 -> 3.3.1 (Central)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
36 items
6 years
WFCORE-3296
by Philippe Marschall
Hello
We recently upgraded from WF 17 to WF 18 and stumbled over WFCORE-3296
which broke our application (we originally implemented WFLY-2345). Our
use case is the following: we set the port offset and then assign socket
bindings relative to the base port. Like this
<socket-binding-group port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="remoting" port="0"/>
<socket-binding name="management-http" port="1"/>
<socket-binding name="management-https" port="2" />
<socket-binding name="management-native" port="3"/>
In this scenario the meaning of 0 is add 0 to the port offset so the
final port is the base port. Currently we use the following work around
which breaks symmetry:
<socket-binding name="remoting"
port="${jboss.socket.binding.port-offset}" fixed-port="true"/>
We do not understand the motivation for the change. For us the meaning
of the port is relative to the port offset unless it is a fixed port. We
do not understand why 0 needs to be treated differently. It is our
understanding that if the wildcard port/indeterminate port/ephemeral
port 0 is desired then fixed-port should be set to true.
https://issues.jboss.org/browse/WFCORE-3296
https://issues.jboss.org/browse/WFLY-2345
Cheers
Philippe
6 years
Possible component upgrades report - Wildfly Core
by thofman＠redhat.com
Generated at 16:49:24 SGT 2019-12-01
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.googlecode.javaewah:JavaEWAH:1.1.6 -> 1.1.7 (Central)
com.jcraft:jsch:0.1.54 -> 0.1.55 (Central)
com.jcraft:jzlib:1.1.1 -> 1.1.3 (Central)
org.apache.httpcomponents:httpclient:4.5.4 -> 4.5.10 (Central)
org.apache.httpcomponents:httpcore:4.4.5 -> 4.4.12 (Central)
org.eclipse.jgit:org.eclipse.jgit:5.0.2.201807311906-r -> 5.0.3.201809091024-r (Central)
org.jboss:jandex:2.1.1.Final -> 2.1.2.Final (Central)
org.jboss.slf4j:slf4j-jboss-logmanager:1.0.3.GA -> 1.0.4.GA (Central)
org.slf4j:jcl-over-slf4j:1.7.22.jbossorg-1 -> 1.7.29 (Central)
9 items
6 years
