Title: Message Title
|
|
Hello, is it possible that this issue was a regression in tomcat 7.0.28 and did not exist before? Should I try and use tomcat 7.0.26 in my production environment? My reason to ponder about it: The provider of my production server offers Ubuntu 12.04 LTS as operating system. 1.) I have good reason to stay with this provider, they are a member of our non for profit organisation. They do a really good job in long term data preservation, they provide hosting for all university libraries in northern germany. Even more then financial reasons, it is a political decision to go with them. 2.) This provider has chosen a long term support version of Ubuntu for good reason. Skipping the latest Ubuntu LTS version 14.04 just makes sense, when running a large scale environment. I will have a hard time to convince them to have us run something different wich does not fit their eco system. 3.) Ubuntu 12.04 provides no different version of tomcat7 then just 7.0.26 in either main, security, updates and backports. My own development server is a debian wheezy which offers me a more current version. But what means testing if the productive environment is just not the same? My options seem to be: a) to plead with the Ubuntu package maintainers for updating a package in a LTS version. b) to find out that tomcat 7.0.26 is just fine and I dont screw up my productive environment when installing it. c) to install a current tomcat aside the package system on a production machine - I am definitely not in favor of this. d) beg my provider to offer me special treatment without charge, hoping it wont beat back on them later. e) rent a third machine with ubuntu 12.04 and do my testing there. f) downgrade my Debian, though it is not sure that even if a 7.0.26 package exists it behaves the same as on Ubuntu. How I came up with the idea that it could be a regression: Reading the Tomcat 7 Changelog, it seems obvious to me, that Bug 53535 was the one in question, because 53081 was fixed before Tomcat 7.0.30. Reading Bug 53535 shows that it was marked as duplicate of Bug 53615. Bug 53615 was filed against Version 7.0.29. I have to admit that this finding is contradictory to the experience of helix84, but at least it gives reason to believe that this issue was introduced after the initial release of Tomcat 7. It is not very likely that such a grave issue was there for two years since initial release without getting noticed. I am not proficient enough in reading code to judge when exactly it was introduced. On the other hand, I know exactly which version I am interested in to know about - version 7.0.26, because this is the one in my distribution. I am open for advice, an option g) to my list above, who knows. Thanks, Christian
|
|
|
|
|
|
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel