On 16/12/2018 16:02, Christopher Schultz wrote:

<snip/>

> I've got a signature problem with the Windows installer (see below).
> Everything else seems okay. I'll hold my +1 until we sort that out.

Ah. That is probably my fault. I managed to kill the release build after
it had completed the Windows installer signing so, rather than
incrementing the version number and starting again (you can't sign the
same version twice), I opted to call each of the remaining targets
manually. I'm guessing I missed the part of the script that re-generates
the GPG sig and hashes for the window installer after the installer had
been signed for Windows.

I keep the build directory structure for a release until I do the next
release in case of issues like this so I'll take a look.

> Works with a standard servlet application.
> 
> Details:
> 
> * Environment
> *  Java (build):     java version "1.8.0_181" Java(TM) SE Runtime
> Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM
> (build 25.181-b13, mixed mode)
> *  Java (test):     java version "1.8.0_181" Java(TM) SE Runtime
> Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM
> (build 25.181-b13, mixed mode)
> *  OS:       Linux 2.6.32-312-ec2 x86_64
> *  cc:       cc (Debian 4.7.2-5) 4.7.2
> *  make:     GNU Make 3.81
> *  OpenSSL:  OpenSSL 1.1.1 11 Sep 2018
> *  APR:      1.4.6
> * Valid SHA-2512 signature for apache-tomcat-8.5.37.zip
> * Valid GPG signature for apache-tomcat-8.5.37.zip
> * Valid SHA-512 signature for apache-tomcat-8.5.37.tar.gz
> * Valid GPG signature for apache-tomcat-8.5.37.tar.gz
> * !! Invalid SHA-256 signature for apache-tomcat-8.5.37.exe
> 
> Hmm. The SHA512 sig I get is:
> 
> 0d0ed883f57e85d334450a27c5104b17f4a99156eeba9ebf81ea8a0b3a56d021b990b00b
> 7c289163c9b3478e00d54935f0b65d6df9de04d05ba9b3f0ce2437cc
> 
> The sig file says:
> 
> 2ef46708f1d04561481ba23dca78a13eaf32cfe0e5c681e58353cc08f446f627da29ef18
> 97bbbb94df2b38e9190886300e7a8dca69c604ad4f29d9d0871fc553
> 
> * !! Invalid GPG signature for apache-tomcat-8.5.37.exe
> 
> $ gpg --verbose --keyring ./apache-keys --no-default-keyring --verify
> apache-tomcat-8.5.37.exe.asc apache-tomcat-8.5.37.exe
> gpg: Signature made Wed 12 Dec 2018 07:08:29 AM EST using RSA key ID
> 2F6059E7
> gpg: using PGP trust model
> gpg: BAD signature from "Mark E D Thomas <ma...@apache.org>"
> gpg: binary signature, digest algorithm SHA256
> 
> 
> I got a fresh copy from
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.37/bin/
> and I'm getting the same errors on that file.

Looking at the timestamps, I failed to update that hash and sig. Should
be fixed now.

<snip/>

> * Junit Tests: FAILED
> * Tests that failed:
> * org.apache.catalina.session.TestStandardSessionIntegration.NIO.txt
> 
> I get this error in the above test:
> 
> 14-Dec-2018 17:06:54.042 SEVERE [main]
> org.apache.catalina.tribes.transport.nio.NioReceiver.start Unable to
> start cluster receiver
>  java.net.BindException: Cannot assign requested address
>       at sun.nio.ch.Net.bind0(Native Method)
>       at sun.nio.ch.Net.bind(Net.java:433)
>       at sun.nio.ch.Net.bind(Net.java:425)
>       at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223
> )
>       at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>       at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
>       at
> org.apache.catalina.tribes.transport.ReceiverBase.bind(ReceiverBase.java
> :205)
> 
> 
> I'm not sure what address is being attempted there, but this could be
> an environmental issue. Historically, I've had issues with Tribes
> integration tests, though I have far fewer of them these days. I used
> to think it was because of lack of multicast, but it appears that
> multicast is indeed enabled.
> 
> Re-running the test again also fails. Any ideas for what to look for?

There should be a log message that includes the address - I think before
the exception you quote above. That might provide some clues.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to