On 01/28/2015 11:26 PM, Tomaž Cerar wrote:
1) no, latest 8.x jars will handle all previous versions just fine
2) not really just one thing that could cause this, but we did fix few
remoting & xnio things in 8.1
on general principal we test all code under ipv6 which is used also by
our PR CI jobs.
also i would recommend you to go with 8.2.0.Final artifacts
Will do, thanks!
On Wed, Jan 28, 2015 at 2:11 PM, Rob Stryker <rstryker(a)redhat.com
JBT is considering updating the following client jar versions for
communication with all wildfly streams 8.x over management api:
marshalling from 1.4.3 to 1.4.9
remoting from 4.0.0 to 4.0.9
xnio from 3.2.0 to 3.3.0
protocol from 8.0.0 to 8.2.0.CR1
controller-client from 8.0.0 to 8.2.0.CR1
The cause for this is that when using the current jars, executing
management tasks with ip6 hosts fails against all wf8.x servers. So
far, updating the jars has passed our smoke tests.
1) Are there any known incompatibilities for those new jar
any wf8.0 or higher? ie, should this new set of jars be able to
communicate flawlessly with wf8.0 through 8.2?
2) This one's more of a curiousity, but does anyone know what
8.0 jars to fail against all servers for management over ip6? I've
combed through jira and git logs a bit but nothing really jumped
out at me.
Answers to these two questions would increase our confidence in
the jars more than simple smoke tests.
- Rob Stryker
wildfly-dev mailing list