Bug#685516: libtcnative-1: Tomcat 7 requires newer libtcnative (at least version 1.1.24)

tony mancill tmancill at debian.org
Fri Aug 24 05:42:36 UTC 2012


Hello Damien,

On 08/23/2012 06:09 PM, Damien Raude-Morvan wrote:
> Hi Tony,
> 
> On 22/08/2012 07:23, tony mancill wrote:
>> On 08/21/2012 07:31 AM, Peter De Wachter wrote:
>>> Package: libtcnative-1
>>> Version: 1.1.23-1
>>> Severity: important
>>>
>>> Dear Maintainer,
>>>
>>> When starting Tomcat 7 (Debian version 7.0.28-2) with this version of
>>> libtcnative, the following error message is logged:
>>>
>>> SEVERE: An incompatible version 1.1.23 of the APR based Apache Tomcat
>>> Native library is installed, while Tomcat requires version 1.1.24
>>
>> Hello Peter,
>>
>> Thank you for taking the time to report this bug.  We can certainly do a
>> better job of coordinating uploads of new upstream versions of
>> tomcat-native and tomcat in the future.  In this case, it didn't take
>> long for tomcat7 to require the latest version of tomcat-native (tcn
>> 1.1.24 was released on 2012/06/13 and tomcat 7.0.28 just 6 days later).
>>
>> I have built a copy of upstream 1.1.24 to get a look at the differences
>> between the upstream source versions.  The upstream source differences
>> are fairly minimal - about 95% of the diff consists of the configure
>> script and documentation changes - but we'll have to see if we can get a
>> freeze exception to allow the newer version of tomcat-native into wheezy
>> and I want to coordinate with Damien before uploading to unstable.
> 
> I've checked diff between 1.1.23 / 1.1.24 and it seems, as you say,
> pretty small. But one modification seems dangerous : in
> jni/native/include/tcn.h, tcn_socket_t got two new fields last_active
> and timeout. Are you sure this change is backward compatible ? at least
> with tomcat 6.x package...
> All others modifications are just new handling of timeout on pooler
> connection...

Good idea.  The tcnative release notes didn't mention any
incompatibility, but it's better to verify that the change is backwards
compatible.

I tested with tomcat6 currently in wheezy/sid and ran some requests
through the server and it appears to be working fine:

> Aug 24, 2012 5:25:23 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: Loaded APR based Apache Tomcat Native library 1.1.24.
> Aug 24, 2012 5:25:23 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
> Aug 24, 2012 5:25:24 AM org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> Aug 24, 2012 5:25:24 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 459 ms
> Aug 24, 2012 5:25:24 AM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Aug 24, 2012 5:25:24 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.35

The library is also working with the packaged version of tomcat7 7.0.28.

Shall I push the packaging updates to SVN?  (And prepare an upload for
unstable too?)

Thank you,
tony



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20120823/49a02009/attachment-0001.pgp>


More information about the pkg-java-maintainers mailing list