Re: Any experience with Tuckey UrlRewrite servlet filter?
You can get the same effect using standard web.xml fragment and without a 3rd party dependency: /* CONFIDENTIAL On Thu, Apr 28, 2016 at 1:12 PM, Lyallex wrote: > apache-tomcat-7.0.42 > jdk1.8.0_77 > CentOS Linux 7.2.1511 > urlrewritefilter-4.0.3.jar > > I'm using the rewrite filter from http://tuckey.org/urlrewrite/ > > I have a rule, it's supposed to 301 perm-redirect from http to https > > >seo redirect >^www.example.com >^localhost >^/(.*) > last="true">https://www.example.com/$1 > > > The problem is despite setting the to-type to permanent-redirect I'm > actually getting a 302 temporary-redirect. > > I know this is probably off topic but if anyone has any experience of > this I'd be gratefull to hear how you solved it > > Thanks > > lyallex > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: systemd tomcat script for Linux EL7
Meh. It's short and sweet and working systemd unit file. [Unit] Description=Apache Tomcat Web Application Container [Service] User=tomcat Group=tomcat ExecStart=/usr/share/tomcat/bin/catalina.sh run [Install] WantedBy=multi-user.target On Wed, Mar 16, 2016 at 8:57 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > jieryn, > > On 3/16/16 1:36 PM, jieryn wrote: >> http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/systemd-house > - -of-horror/tomcat.html > > Wow, >> > lots of ranting about environment variables and little-used PID > files. > > If the author only understood the reasons behind the way catalina.sh > works, he might not have embarrassed himself. > > It must be hard being so smart and important that you have to quit the > Internet for good[1]. > > - -chris > > [1] > http://homepage.ntlworld.com/jonathan.deboynepollard/contacting-the-auth > or.html#SMTP > >> On Wed, Mar 16, 2016 at 1:01 PM, Lyallex >> wrote: >>> Apologies for dredging this up but I'm having some problems with >>> this. Any ideas much appreciated. >>> >>> Ii have been forced to move from a version of centOS the used the >>> old /etc/rc.d/init.d way of doing things to a new version of >>> CentOS that uses systemd. The hosts can't or won't help because >>> I'm using a 'non-standard setup' Basically I'm using tomcat >>> standalone on port 80 to serve up my site. I use jsvc with a >>> start/stop script in /etc/rc.d/init.d with symbolic links in >>> rc2.d, rc3.d. rc4.d and rc5.d This has been working faultlessly >>> for nearly 4 years. >>> >>> I have installed Tomcat, Java and all required resources on the >>> new server, I have dulpicated the configuration in /etc but >>> needless to say when I restart the server Tomcat doesn't start >>> >>> Starting from the command line as root with >>> /etc/rc.d/init.d/tomcat7 works as it has always done and starts >>> tomcat as root then switches to an unprivileged, no login user >>> (tomcat) >>> >>> I followed your instructions and came up with the following >>> >>> # touch /etc/systemd/system/tomcat.service # nano >>> /etc/systemd/system/tomcat.service >>> >>> tomcat.service looks like this >>> >>> [Unit] Description=The Jakarta Apache/Tomcat Server >>> After=network.target >>> >>> [Service] Type=forking ExecStart=/etc/rc.d/init.d/tomcat7 start >>> ExecStop=/etc/rc.d/init.d/tomcat7 stop >>> >>> [Install] WantedBy=multi-user.target >>> >>> # chmod 664 /etc/systemd/system/tomcat.service >>> >>> [root@vps init.d]# systemctl daemon-reload >>> >>> [root@vps init.d]# systemctl start tomcat.service Job for >>> tomcat.service failed because the control process exited with >>> error code. See "systemctl status tomcat.service" and "journalctl >>> -xe" for details. >>> >>> [root@vps init.d]# systemctl status tomcat.service tomcat.service >>> - The Jakarta Apache/Tomcat Server Loaded: loaded >>> (/etc/systemd/system/tomcat.service; disabled; vendor preset: >>> disabled) Active: failed (Result: exit-code) since Wed 2016-03-16 >>> 16:40:55 GMT; 18s ago Process: 4596 >>> ExecStart=/etc/rc.d/init.d/tomcat7 start (code=exited, >>> status=203/EXEC) >>> >>> Mar 16 16:40:55 vps.example.com systemd[1]: Starting The Jakarta >>> Apache/Tomcat Server... Mar 16 16:40:55 vps.example.com >>> systemd[1]: tomcat.service: control process exited, code=exited >>> status=203 Mar 16 16:40:55 vps.example.com systemd[1]: Failed to >>> start The Jakarta Apache/Tomcat Server. Mar 16 16:40:55 >>> vps.example.com systemd[1]: Unit tomcat.service entered failed >>> state. Mar 16 16:40:55 vps.example.com systemd[1]: tomcat.service >>> failed. >>> >>> tomcat7 fwiw >>> >>> >>> # chkconfig: - 71 19 # description: Start up the Tomcat servlet >>> engine. # this is the startup file for the new version # >>> 24/10/2013 by lyallex # use java 7 # >>> JAVA_HOME=/usr/local/java/jdk1.6.0_07 JAVA_HOME=/opt/jdk1.7.0_45 >>> CATALINA_HOME=/opt/apache-tomcat-7.0.42 export JAVA_HOME >>> CATALINA_HOME >>> CLASSPATH=$CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons > - -daemon.jar:$JAVA_HOME/lib/tools.jar:$CATALINA_HOME/bin/tomcat-juli.jar >>> >>> > TOMCAT_USER=tomcat >>> TMP
Re: systemd tomcat script for Linux EL7
ExecStartPre=/usr/sbin/setcap 'cap_net_bind_service=+ep' /usr/share/tomcat/bin/catalina.sh I see a lot of advice for start/stop instead of run within systemd unit files, both here and in the wild. The gem in the rant I linked is about start vs run. Sorry if you didn't see it. On Thu, Mar 17, 2016 at 1:42 AM, Lyallex wrote: > But that doesn't work for ports < 1024 > > > On 17 March 2016 at 01:47, jieryn wrote: >> Meh. It's short and sweet and working systemd unit file. >> >> [Unit] >> Description=Apache Tomcat Web Application Container >> [Service] >> User=tomcat >> Group=tomcat >> ExecStart=/usr/share/tomcat/bin/catalina.sh run >> [Install] >> WantedBy=multi-user.target >> >> >> On Wed, Mar 16, 2016 at 8:57 PM, Christopher Schultz >> wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> jieryn, >>> >>> On 3/16/16 1:36 PM, jieryn wrote: >>>> http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/systemd-house >>> - -of-horror/tomcat.html >>> >>> Wow, >>>> >>> lots of ranting about environment variables and little-used PID >>> files. >>> >>> If the author only understood the reasons behind the way catalina.sh >>> works, he might not have embarrassed himself. >>> >>> It must be hard being so smart and important that you have to quit the >>> Internet for good[1]. >>> >>> - -chris >>> >>> [1] >>> http://homepage.ntlworld.com/jonathan.deboynepollard/contacting-the-auth >>> or.html#SMTP >>> >>>> On Wed, Mar 16, 2016 at 1:01 PM, Lyallex >>>> wrote: >>>>> Apologies for dredging this up but I'm having some problems with >>>>> this. Any ideas much appreciated. >>>>> >>>>> Ii have been forced to move from a version of centOS the used the >>>>> old /etc/rc.d/init.d way of doing things to a new version of >>>>> CentOS that uses systemd. The hosts can't or won't help because >>>>> I'm using a 'non-standard setup' Basically I'm using tomcat >>>>> standalone on port 80 to serve up my site. I use jsvc with a >>>>> start/stop script in /etc/rc.d/init.d with symbolic links in >>>>> rc2.d, rc3.d. rc4.d and rc5.d This has been working faultlessly >>>>> for nearly 4 years. >>>>> >>>>> I have installed Tomcat, Java and all required resources on the >>>>> new server, I have dulpicated the configuration in /etc but >>>>> needless to say when I restart the server Tomcat doesn't start >>>>> >>>>> Starting from the command line as root with >>>>> /etc/rc.d/init.d/tomcat7 works as it has always done and starts >>>>> tomcat as root then switches to an unprivileged, no login user >>>>> (tomcat) >>>>> >>>>> I followed your instructions and came up with the following >>>>> >>>>> # touch /etc/systemd/system/tomcat.service # nano >>>>> /etc/systemd/system/tomcat.service >>>>> >>>>> tomcat.service looks like this >>>>> >>>>> [Unit] Description=The Jakarta Apache/Tomcat Server >>>>> After=network.target >>>>> >>>>> [Service] Type=forking ExecStart=/etc/rc.d/init.d/tomcat7 start >>>>> ExecStop=/etc/rc.d/init.d/tomcat7 stop >>>>> >>>>> [Install] WantedBy=multi-user.target >>>>> >>>>> # chmod 664 /etc/systemd/system/tomcat.service >>>>> >>>>> [root@vps init.d]# systemctl daemon-reload >>>>> >>>>> [root@vps init.d]# systemctl start tomcat.service Job for >>>>> tomcat.service failed because the control process exited with >>>>> error code. See "systemctl status tomcat.service" and "journalctl >>>>> -xe" for details. >>>>> >>>>> [root@vps init.d]# systemctl status tomcat.service tomcat.service >>>>> - The Jakarta Apache/Tomcat Server Loaded: loaded >>>>> (/etc/systemd/system/tomcat.service; disabled; vendor preset: >>>>> disabled) Active: failed (Result: exit-code) since Wed 2016-03-16 >>>>> 16:40:55 GMT; 18s ago Process: 4596 >>>>> ExecStart=/etc/rc.d/init.d/tomcat7 start (code=exited, >>>>> status=203/EXEC) >&
Re: systemd tomcat script for Linux EL7
http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/systemd-house-of-horror/tomcat.html
On Wed, Mar 16, 2016 at 1:01 PM, Lyallex wrote:
> Apologies for dredging this up but I'm having some problems with this.
> Any ideas much appreciated.
>
> Ii have been forced to move from a version of centOS the used the old
> /etc/rc.d/init.d
> way of doing things to a new version of CentOS that uses systemd. The
> hosts can't or won't help because I'm using a 'non-standard setup'
> Basically I'm using tomcat standalone on port 80 to serve up my site.
> I use jsvc with a start/stop script in /etc/rc.d/init.d with symbolic
> links in rc2.d, rc3.d. rc4.d and rc5.d This has been working
> faultlessly for nearly 4 years.
>
> I have installed Tomcat, Java and all required resources on the new
> server, I have dulpicated the configuration in /etc but needless to
> say when I restart the server Tomcat doesn't start
>
> Starting from the command line as root with /etc/rc.d/init.d/tomcat7
> works as it has always done and starts tomcat as root then switches to
> an unprivileged, no login user (tomcat)
>
> I followed your instructions and came up with the following
>
> # touch /etc/systemd/system/tomcat.service
> # nano /etc/systemd/system/tomcat.service
>
> tomcat.service looks like this
>
> [Unit]
> Description=The Jakarta Apache/Tomcat Server
> After=network.target
>
> [Service]
> Type=forking
> ExecStart=/etc/rc.d/init.d/tomcat7 start
> ExecStop=/etc/rc.d/init.d/tomcat7 stop
>
> [Install]
> WantedBy=multi-user.target
>
> # chmod 664 /etc/systemd/system/tomcat.service
>
> [root@vps init.d]# systemctl daemon-reload
>
> [root@vps init.d]# systemctl start tomcat.service
> Job for tomcat.service failed because the control process exited with
> error code. See "systemctl status tomcat.service" and "journalctl -xe"
> for details.
>
> [root@vps init.d]# systemctl status tomcat.service
> tomcat.service - The Jakarta Apache/Tomcat Server
>Loaded: loaded (/etc/systemd/system/tomcat.service; disabled;
> vendor preset: disabled)
>Active: failed (Result: exit-code) since Wed 2016-03-16 16:40:55 GMT; 18s
> ago
> Process: 4596 ExecStart=/etc/rc.d/init.d/tomcat7 start (code=exited,
> status=203/EXEC)
>
> Mar 16 16:40:55 vps.example.com systemd[1]: Starting The Jakarta
> Apache/Tomcat Server...
> Mar 16 16:40:55 vps.example.com systemd[1]: tomcat.service: control
> process exited, code=exited status=203
> Mar 16 16:40:55 vps.example.com systemd[1]: Failed to start The
> Jakarta Apache/Tomcat Server.
> Mar 16 16:40:55 vps.example.com systemd[1]: Unit tomcat.service
> entered failed state.
> Mar 16 16:40:55 vps.example.com systemd[1]: tomcat.service failed.
>
> tomcat7 fwiw
>
>
> # chkconfig: - 71 19
> # description: Start up the Tomcat servlet engine.
> # this is the startup file for the new version
> # 24/10/2013 by lyallex
> # use java 7
> # JAVA_HOME=/usr/local/java/jdk1.6.0_07
> JAVA_HOME=/opt/jdk1.7.0_45
> CATALINA_HOME=/opt/apache-tomcat-7.0.42
> export JAVA_HOME CATALINA_HOME
> CLASSPATH=$CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-daemon.jar:$JAVA_HOME/lib/tools.jar:$CATALINA_HOME/bin/tomcat-juli.jar
> TOMCAT_USER=tomcat
> TMPDIR=/var/tmp
> PIDFILE=/var/run/tc7/jsvc.pid
>
>
> RC=0
>
> case "$1" in
>
> start)
>
>$CATALINA_HOME/bin/jsvc -user $TOMCAT_USER -home $JAVA_HOME
> -Dcatalina.home=/opt/apache-tomcat-7.0.42
> -Dcatalina.base=$CATALINA_HOME -Djava.io.tmpdir=$TMPDIR
> -Djava.awt.headless=true \
> -Xms512m \
> -Xmx1024m \
> -outfile $CATALINA_HOME/logs/catalina.out \
> -errfile $CATALINA_HOME/logs/catalina.err \
> -pidfile '/var/run/tc7/jsvc.pid' \
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \
> -Djava.util.logging.config.file=$CATALINA_HOME/conf/logging.properties \
> -cp $CLASSPATH \
> org.apache.catalina.startup.Bootstrap
>
> RC=$?
>
> [ $RC = 0 ] && touch /var/tc7lock/subsys/tomcat
> echo "starting tomcat7 on darkstar with:"
> echo "JAVA_HOME=$JAVA_HOME"
> echo "CATALINA_HOME=$CATALINA_HOME"
> echo "CLASSPATH=$CLASSPATH"
> echo "tomcat started"
>
>echo "CLASSPATH=$CLASSPATH"
> echo "tomcat started"
> ;;
>
> stop)
>
> PID=`cat /var/run/tc7/jsvc.pid`
> kill $PID
>
>RC=$?
>
> [ $RC = 0 ] && rm -f /var/tc7lock/subsys/tomcat /var/run/tc7/jsvc.pid
> echo "stopping tomcat7 on darkstar with:"
> echo "JAVA_HOME=$JAVA_HOME"
> echo "CATALINA_HOME=$CATALINA_HOME"
> echo "CLASSPATH=$CLASSPATH"
>
> echo "tomcat stopped"
> ;;
>
> *)
> echo "Usage: $0 {start|stop}"
> exit 1
> esac
> exit $RC
>
>
>
> TIA
> Lyallex
>
>
> On 5 June 2015 at 13:37, Ray Holme wrote:
>> That looks OK, but I would suggest the following.
>> Put all the real stuff in a standard bash script with 3 parameters start,
>> stop, restart- pretty much like the OLD system 5 way fo doing things.This
>> has the advantage of allowing you to add other things you might wa
Re: porting jsvc startup script from init.d to systemd tomcat.service, resolved
Or remove the Type=Forking and just execute catalina.sh run, as I had suggested days ago. Then you can drop the ExecStop too. On Fri, Mar 18, 2016 at 7:35 PM, Daniel Savard wrote: > I believe all distros have over engineered the scripts to start > Tomcat. Forget all the scripts from your distro, learn the > signification of the environment variables from the catalina.sh script > shipped with the default Tomcat version. Define your variables in a > file, this file is not a script, so you cannot reuse a previously > defined variable, feed your systemd service definition file with this > file in the service section as EnvironmentFile=/path/name/to/your/file > ExecStart=/path/to/catalina.sh start > ExecStop=/path/to/catalina.sh stop > > and you are done. You control everything from the environment file, > you can easily manage the environment variables without editing the > systemd's service file. > > It is much simpler than the OpenRC set of scripts at my humble > opinion. I am running Gentoo at home and RHEL at work and both distros > wrapped Tomcat into too many layers of scripts in order to make it > working with OpenRC while none of these are required to run and manage > Tomcat with systemd. > > In particular with Gentoo, I no longer use the Tomcat distro packaged > with Gentoo because they separated the servlet api from Tomcat and you > need to wrap things into layers of scripts to define the classpath > properly taking this into account, the vanilla classpath.sh file > distributed with Tomcat doesn't work and so one. Really, they did a > very bad job at integrating Tomcat. > > Here is my service file: > > [Unit] > Description=Tomcat 8 (Dev) > After=syslog.target > After=network.target > > [Service] > EnvironmentFile=/tomcat/tomcat-8-dev/bin/tomcat-8-dev.env > Type=forking > User=tomcat > Group=tomcat > ExecStart=/opt/apache-tomcat/apache-tomcat-8.0.32_ds/bin/catalina.sh start > ExecStop=/opt/apache-tomcat/apache-tomcat-8.0.32_ds/bin/catalina.sh stop > > [Install] > WantedBy=multi-user.target > > > And here is the content of my EnvironmentFile: > > CATALINA_HOME="/opt/apache-tomcat/apache-tomcat-8.0.32_ds" > CATALINA_BASE="/tomcat/tomcat-8-dev" > CATALINA_OUT="/var/log/tomcat-8-dev/catalina.out" > JAVA_HOME="/opt/oracle-jdk-bin-1.8.0.74" > CATALINA_PID="/var/run/tomcat-8-dev.pid" > > > - > Daniel Savard > > > 2016-03-18 13:31 GMT-04:00 Lyallex : >> I thought you might be interested in the resolution to this. >> >> It turns out that we needed to reproduce the environment in tomcat.service >> >> For some reason >> >> ExecStart=/etc/rc.d/init.d/tomcat7 doesn't work >> (file shown at the end of this message) >> >> Instead, in /etc/systemd/system/tomcat.service >> we have had to reproduce the environment in longhand to get it to work. >> It appears that systemd doesn't expand variables so I really need to >> investigate the systemd Environment thing a bit more. >> Anyway, when I shutdown -r now the server comes back up and tomcat is >> running at the unprivileged tomcat user on port 80 so that's a result >> >> == /etc/systemd/system/tomcat.service >> [Unit] >> Description=Apache Tomcat Web Application Container >> After=network.target >> >> [Service] >> Type=forking >> User=root >> >> ExecStart=/opt/apache-tomcat-7.0.42/bin/jsvc \ >> -user tomcat \ >> -home /opt/jdk1.7.0_45 \ >> -Dcatalina.home=/opt/apache-tomcat-7.0.42 \ >> -Dcatalina.base=/opt/apache-tomcat-7.0.42 \ >> -Djava.io.tmpdir=/var/tmp \ >> -Djava.awt.headless=true \ >> -Xms512m \ >> -Xmx1024m \ >> -outfile /opt/apache-tomcat-7.0.42/logs/catalina.out \ >> -errfile /opt/apache-tomcat-7.0.42/logs/catalina.err \ >> -pidfile /var/run/tc7/jsvc.pid \ >> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \ >> -Djava.util.logging.config.file=/opt/apache-tomcat-7.0.42/conf/logging.properties >> \ >> -cp >> /opt/apache-tomcat-7.0.42/bin/bootstrap.jar:/opt/apache-tomcat-7.0.42/bin/commons-daemon.jar:/opt/jdk1.7.0_45/lib/tools.jar:/opt/apache-tomcat-7.0.42/bin/tomcat-juli.jar >> \ >> org.apache.catalina.startup.Bootstrap >> >> ExecStop=/bin/kill -9 /var/run/tc7/jsvc.pid >> ExecStopPost=/bin/rm -f /var/tc7lock/subsys/tomcat /var/run/tc7/jsvc.pid >> >> [Install] >> WantedBy=multi-user.target >> >> >> Oh happy day >> Thanks again to all responders >> >> Lyallex >> >> = /etc/rc.d/init.d/tomcat7 = >> >> JAVA_HOME=/opt/jdk1.7.0_45 >> CATALINA_HOME=/opt/apache-tomcat-7.0.42 >> export JAVA_HOME CATALINA_HOME >> CLASSPATH=$CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-daemon.jar:$JAVA_HOME/lib/tools.jar:$CATALINA_HOME/bin/tomcat-juli.jar >> TOMCAT_USER=tomcat >> TMPDIR=/var/tmp >> PIDFILE=/var/run/tc7/jsvc.pid >> >> >> RC=0 >> >> case "$1" in >> >> start) >> >>$CATALINA_HOME/bin/jsvc -user $TOMCAT_USER -home $JAVA_HOME >> -Dcatalina.home=/opt/apache-tomcat-7.0.42 >> -Dcatalina.base=$CATALINA_HOME -Djava.io.tmpdir=$TMPDIR >> -Djava.awt.headless=true \ >> -Xms512m \ >>
Re: Zero downtime deployments
Use http://flywaydb.org/ to perform database migrations. You will need at least 3 versions in order to perform an incompatible database change. v1 is existing behavior, v2 is a shim that bridges v1 and v3, and then v3 cleans up the shim and removes all the unnecessary hacks. When you have v1 rolled out against N images, then you can start rolling out compat shim v2 which adds some temporary work for the db and coexists, then when all instances are at v2 you can move to v3 which uses all the new stuff. I haven't found anything better or more efficient than the 2-step deployment with live code. On Thu, Dec 3, 2015 at 2:21 PM, Kevin Hale Boyes wrote: > Thanks for this link to the presentation. > How do you all deal with some of the other dependencies that the web > application has? > > For example, if v2 of my application needs new database columns or worse, a > change to an existing column how can I have v1 and v2 running at the same > time? We use Oracle as our database though the problem exists for many > database servers. > > Thanks, > Kevin. > > On 3 December 2015 at 01:31, Neill Lima wrote: > >> Hello Jason, >> >> This approach of using httpd in front of 2+ Tomcats via AJP works well in >> my company. There is a bit of config necessary at httpd level so httpd is >> aware of all the Tomcats and also Tomcat config needs to be set to listen >> to AJP port instead of default port but it is not rocket science. >> >> This facilitates the deployment of nodes sequentially with no downtime. Of >> course, there is a shared session server to take care the sessions are not >> lost when Tomcats flip up and down. >> >> Reply in pvt if you need help setting up this. >> >> Thanks, >> >> Neill >> >> On Thu, Dec 3, 2015 at 12:08 AM, Jason Britton >> wrote: >> >> > Thank you Christopher, reading now and we'll see if I can swing the >> > conference :) >> > >> > On Wed, Dec 2, 2015 at 4:00 PM, Christopher Schultz < >> > ch...@christopherschultz.net> wrote: >> > >> > > Jason, >> > > >> > > On 12/2/15 4:07 PM, Jason Britton wrote: >> > > > I was looking for information for how those on the list achieve zero >> > > > downtime deployments of their tomcat hosted web applications. I >> > imagine >> > > > this can be achieved in a variety of ways, but would love to hear >> what >> > > > works for you. In our current environment we front multiple tomcat >> > > > instances with apache httpd, each tomcat instance hosting one or more >> > > > unique web apps. In order to support this effort we do have the >> > > resources >> > > > where we could spin up multiple tomcat instances to serve requests >> for >> > a >> > > > single application. I know there is mod_proxy_balancer available for >> > > > httpd, and I understand starting with tomcat 7 there is support for >> > > > parallel deployment of versioned wars, and tomcat also supports >> > > > clustering. I'm just unsure of what approach I should start digging >> > into >> > > > and would very much appreciate any of your experiences. The servers >> > > we'll >> > > > be rolling out will be using the latest versions of tomcat 8 and >> apache >> > > > httpd 2.4. Thanks for any insights! >> > > >> > > Check this out: >> > > >> > > >> > >> http://people.apache.org/~schultz/ApacheCon%20NA%202015/Load-balancing%20Tomcat%20with%20mod_jk.pdf >> > > >> > > Start on slide/page 41. >> > > >> > > Then come to ApacheCon NA 2016 and discuss it! >> > > >> > > -chris >> > > >> > > - >> > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> > > For additional commands, e-mail: users-h...@tomcat.apache.org >> > > >> > > >> > >> - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Container Provided ServletFilters
Hello Apache Tomcat, Is there any hope to have Tomcat package the very useful ServletFilter's it has created ( src=java/org/apache/catalina/filters, web=https://tomcat.apache.org/tomcat-8.0-doc/config/filter.html ) into its own Apache Maven module? I see we have a lot of deployed modules already, but these filters are quite useful even if the final container is not Apache Tomcat! It would be nice to decouple them, and I think valuable to users at large. Thank you! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Deployment Woe with Cargo
Greetings, I'm using Apache Tomcat 7.0.55 via Apache TomEE 1.7.1, on a RHEL machine with IBM Java.7. My team has a deployment procedure which uses Jenkins CI to check out, build, test, and then leverage Codehaus Cargo to deploy the final generated WAR artifact. The procedure is long but fairly straightforward, and I believe it is a general best practice to have the full CI environment validate the build and then do the deployment via push button. The problem that we have is that Cargo / Tomcat, I'm not sure who to blame, as part of the redeploy task, first performs an undeploy and then performs a deploy. This means that for the entire time(transfer the war file), which is often 60-90 seconds, the application is down and unavailable. It would be a lot better if we could transfer the war file first and then do the undeploy and deploy. (We do not leverage parallel deployment#00x for single-thread/brain concurrency sanity.) To whom should I address my concerns, please? Thank you! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Release calendar of Apache Tomcat versions
I guess it depends on how you view what a "release" is.. it's not like the tags are changed after the fact, a new version is just cut for Apache Tomcat. The artifacts are still uploaded to a staging maven repository.. they are available for testing. Finally, the dates actually do match up pretty closely, any variance is probably just the voting period. bash$ svn cat http://svn.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml | grep 'section name=\"Tomcat ' On Thu, Nov 20, 2014 at 12:07 PM, Mark Thomas wrote: > On 20/11/2014 17:52, jieryn wrote: >> Wow, all I've seen are examples that are likely the least efficient >> way to do things. Just use the version control system itself: > > Tag date != release date. > > Mark > > >> >> bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/ >> 1562629 markt Jan 29 2014 TOMCAT_8_0_0/ >> 1562630 markt Jan 29 2014 TOMCAT_8_0_1/ >> 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/ >> 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/ >> 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/ >> 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/ >> 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/ >> 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/ >> 1565426 markt Feb 06 2014 TOMCAT_8_0_2/ >> 1565729 markt Feb 07 2014 TOMCAT_8_0_3/ >> 1579364 markt Mar 19 2014 TOMCAT_8_0_4/ >> 1580930 markt Mar 24 2014 TOMCAT_8_0_5/ >> 1594516 markt May 14 2014 TOMCAT_8_0_6/ >> 1594945 markt May 15 2014 TOMCAT_8_0_7/ >> 1595294 markt May 16 2014 TOMCAT_8_0_8/ >> 1603862 markt Jun 19 08:42 TOMCAT_8_0_9/ >> >> >> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso wrote: >>> I want to know where I can find the release calendar of the Apache Tomcat >>> versions in order to do an analysis of the project. I have been searching >>> in the Wiki, Google, etc but I don't found anything by the moment. >>> >>> Thanks. >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Release calendar of Apache Tomcat versions
Wow, all I've seen are examples that are likely the least efficient way to do things. Just use the version control system itself: bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/ 1562629 markt Jan 29 2014 TOMCAT_8_0_0/ 1562630 markt Jan 29 2014 TOMCAT_8_0_1/ 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/ 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/ 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/ 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/ 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/ 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/ 1565426 markt Feb 06 2014 TOMCAT_8_0_2/ 1565729 markt Feb 07 2014 TOMCAT_8_0_3/ 1579364 markt Mar 19 2014 TOMCAT_8_0_4/ 1580930 markt Mar 24 2014 TOMCAT_8_0_5/ 1594516 markt May 14 2014 TOMCAT_8_0_6/ 1594945 markt May 15 2014 TOMCAT_8_0_7/ 1595294 markt May 16 2014 TOMCAT_8_0_8/ 1603862 markt Jun 19 08:42 TOMCAT_8_0_9/ On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso wrote: > I want to know where I can find the release calendar of the Apache Tomcat > versions in order to do an analysis of the project. I have been searching in > the Wiki, Google, etc but I don't found anything by the moment. > > Thanks. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat && SPDY
PING? And can someone please update http://tomcat.apache.org/tomcat-8.0-doc/changelog.html to use the SPDY instead of SDPY which would help with search engines and Ctrl-F finding? Thanks. On Wed, Nov 6, 2013 at 9:31 AM, jieryn wrote: > I have various applications deployed to a mix of Apache Tomcat 7.x and > 8.x. I'd like to try out the SPDY protocol for some of these > applications. I see that there has been some semblance of SPDY support > in Tomcat, but I can not find any documentation at all.. > > Would someone speak up if they are using SPDY with Tomcat? Can you > share your configuration? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat && SPDY
Greetings, I have various applications deployed to a mix of Apache Tomcat 7.x and 8.x. I'd like to try out the SPDY protocol for some of these applications. I see that there has been some semblance of SPDY support in Tomcat, but I can not find any documentation at all.. Would someone speak up if they are using SPDY with Tomcat? Can you share your configuration? Thanks. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache Tomcat 8.0.0-RC2
I'm trying out the new Apache Tomcat 8.0.0-RC2 with some existing web
applications that work fine under Apache Tomcat 8.0.0-RC1.
I am now seeing literally thousands of warning messages at start up time:
17-Sep-2013 20:19:40.346 WARNING [hostname-startStop-1]
org.apache.catalina.webresources.Cache.getResource Unable to add the
resource at [{0}] to the cache because there was insufficient free
space available after evicting expired cache entries - consider
increasing the maximum size of the cache
(Note that the [{0}] is the actual text, which suggests a secondary problem.)
Are these messages the result of the Context configuration elements
cacheMaxSize, cacheObjectsMaxSize, cacheTTL, and cachingAllowed? Would
it be better to not omit these messages at catalina start up if they
are for static resources which have been requested by clients?
Thanks!
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 7.x: Host+Alias and HTTP 301
Greetings, On Sat, Jul 20, 2013 at 12:36 AM, jieryn wrote: > I have multiple host names which resolve to the same > application context, e.g. app.host1.com (host) and app.host2.com > (alias). I have implemented this within conf/server.xml via Host and > Alias definitions. Just to close the loop here, I eventually did solve this with URLRewrite filter. The documentation I was looking at was inaccurate or maybe just mismatched against the version of the library being used.. Alas, here is the working URLRewrite rule: Domain name change from $OLDHOST1, with $OLDHOST2 Alias, to $NEWHOST. $OLDHOST1 $OLDHOST2 ^(.*)$ http://$NEWHOST/$1 Thanks! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
Greetings, On Wed, Aug 7, 2013 at 9:58 AM, Caldarale, Charles R wrote: > To allow Tomcat to work. If we changed the name to conf/do_not_delete.xml, > would that satisfy you? I think you've quite severely missed the point of the entire discussion which I've raised. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE
Greetings, On Wed, Aug 7, 2013 at 9:54 AM, Martin Grigorov wrote: > Which you will delete too, I suppose ? :-) I have not modified the shipped Apache Tomcat applications themselves. I suspect that most users are very accustomed to modifying contents under conf/* but leave the shipped applications alone. The humour is wearing off. -Jesse - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE
Greetings, On Wed, Aug 7, 2013 at 9:41 AM, Caldarale, Charles R wrote: > Sorry, that's just wrong. There is no requirement for an individual webapp > to have a WEB-INF/web.xml, but if you want to run Tomcat with the required > servlet spec capabilities, you must leave Tomcat's conf/web.xml in place. There's no requirement for having those required servlet spec capabilities defined as a web.xml. They can be automatically loaded via web-fragment.xml or the metadata discovery mechanism. -Jesse - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
On Tue, Aug 6, 2013 at 11:34 PM, Christopher Schultz wrote: > The servlet specification requires that certain services be provided > by the container. Among them are a) a default servlet to serve content > for which no other servlet mapping exists (e.g. static files, etc.) > and b) a servlet called "jsp" that is, by default, mapped to "*.jsp". I was not aware of that requirement, thank you for the information. > Tomcat chooses to provide the above services by using conf/web.xml as > a default. If you break that mechanism, you are going to lose some > functionality. The webapp should be able to rely on the default and > JSP servlets being available even without specifically configuring > them in the webapp's own web.xml. There's actually no requirement for a web.xml for now two releases of the Servlet specification. How does the Apache Tomcat community feel about coding these core servlets with @WebServlet and let them be automatically discovered through the normal metadata-complete=false processing? > Why are you deleting conf/web.xml in the first place? As I recall, it was because some web.xml fields were inherited in an additive manner, e.g. mime type mapping, and it included extra items I didn't want. And for other pieces of configuration data that were present in the conf/web.xml (DefaultServlet, and JspServlet), I had already overridden, so what is the point of keeping the global conf/web.xml.. -Jesse - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE
Greetings, On Tue, Aug 6, 2013 at 11:30 PM, Christopher Schultz wrote: > Tomcat also has a serious bug in that if you delete conf/server.xml, > it won't start up properly. I sense I'm being mocked.. :-) I'll answer more completely in the other no-web.xml NPE thread, but quickly: there's no actual requirement for web.xml, and while I got a chuckle out of your comment, I'd say that this is a false comparison of webapp vs tomcat configuration data. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
Greetings, On Tue, Aug 6, 2013 at 4:53 PM, Mark Thomas wrote: > The Tomcat 7.0.x behaviour is identical to Tomcat 8.0.x. > The root cause of the stack trace in both versions is the missing > configuration for the JSP servlet. Ok, since the manager application already provides a web.xml file, shouldn't it fully specify all of its requirements? If it requires a JSP renderer servlet, it should probably state so in its deployment descriptor; for completeness and correctness. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager 404; NPE
Greetings,
On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas wrote:
> On 06/08/2013 20:46, jieryn wrote:
>> When I try to hit the /manager application from a browser without
>> specifying /html, the following NPE ends up in the log, but the
>> browser sees what appears to be a typical tomcat 404 error page
>> without exposing the full trace:
>
> I can't repeat this with a clean installation. Please provide the steps
> to reproduce from a clean 8.0.0-RC1 install.
Remove the ${catalina.home}/conf/web.xml file and restart the server.
With Apache Tomcat 7.x there was no need for this conf/web.xml to be
present for the manager to work properly.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE
Greetings,
On Tue, Aug 6, 2013 at 2:56 PM, Mark Thomas wrote:
> On 06/08/2013 20:31, jieryn wrote:
>> When clicking the 'SSL connector configuration diagnostics'
>> 'Connection ciphers' button, the following NPE ends up in the log and
>> a similar stack trace is sent to the browser:
>
> I can't repeat this with a clean installation. Please provide the steps
> to reproduce from a clean 8.0.0-RC1 install.
Remove the ${catalina.home}/conf/web.xml file and restart the server.
With Apache Tomcat 7.x there was no need for this conf/web.xml to be
present for the manager to work properly.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
apache tomcat 8.0.0-rc1; /manager 404; NPE
When I try to hit the /manager application from a browser without specifying /html, the following NPE ends up in the log, but the browser sees what appears to be a typical tomcat 404 error page without exposing the full trace: ==> logs/access_log.2013-08-06 <== a.b.c.d - - [06/Aug/2013:14:37:52 -0400] "GET /manager HTTP/1.1" 302 - a.b.c.d - tomcatadmin [06/Aug/2013:14:37:52 -0400] "GET /manager/ HTTP/1.1" 404 955 ==> logs/catalina.2013-08-06.log <== 06-Aug-2013 14:37:52.862 SEVERE [http-apr-9.12.19.180-8443-exec-3] org.apache.catalina.core.StandardHostValve.custom Exception Processing ErrorPage[errorCode=404, location=/WEB-INF/jsp/404.jsp] java.lang.NullPointerException at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:456) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:324) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:75) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:934) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:90) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:494) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:632) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:281) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2248) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614) at java.lang.Thread.run(Thread.java:779) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
apache tomcat 8.0.0-rc1; /manager connection ciphers; NPE
When clicking the 'SSL connector configuration diagnostics' 'Connection ciphers' button, the following NPE ends up in the log and a similar stack trace is sent to the browser: SEVERE [http-apr-9.12.19.180-8443-exec-4] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [HTMLManager] in context with path [/manager] threw exception java.lang.NullPointerException at org.apache.catalina.manager.HTMLManagerServlet.sslConnectorCiphers(HTMLManagerServlet.java:754) at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:153) at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:230) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:212) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:223) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:107) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:616) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:75) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:934) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:90) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:494) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:632) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:281) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2248) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614) at java.lang.Thread.run(Thread.java:779) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache Tomcat 7.x: Host+Alias and HTTP 301
Greetings, I'm using Apache Tomcat 7.0.42, with IBM Java 1.7.0-SR2, on SuSE SLED 11 Linux. I have multiple host names which resolve to the same application context, e.g. app.host1.com (host) and app.host2.com (alias). I have implemented this within conf/server.xml via Host and Alias definitions. Moving forward, I would like Apache Tomcat to send a permanent redirect, HTTP 301, for any incoming request on app.host2.com to app.host1.com. How can I achieve this? I no longer want both app.host1.com and app.host2.com to work "invisibly" to the user; I want the user to see the host1.com address in his/her browser and to teach the user, perhaps very subtly, to use that host1.com hostname. I have tried Tuckey's URLRewrite filter, with a condition on type="hostname", but I can not seem to get it right--lots of strange infinite loop redirection for SSO. Regardless, this seems like something that Apache Tomcat should be able to handle pretty easily.. Any help is appreciated, thanks, -Jesse - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: checkThreadLocalMapForLeaks: com.sun.xml.bind.v2.runtime.Coordinator
Greetings,
On Mon, May 20, 2013 at 9:45 AM, Konstantin Kolinko
wrote:
> 2013/5/19 jieryn :
>> $ grep com.sun.xml.bind.v2.runtime.Coordinator *
>> Binary file jaxb-impl-2.2.1.1.jar matches
>> Apache Maven dependency:tree shows that this is coming from Apache
>> Wink (wink-common -> wink-client).
>
> Where the jar is located?
> IIRC the JRE provides a JAXB implementation, so if you replace one,
> shouldn't the jar go into ${catalina.home}/endorsed ?
Apache Wink's POM lists it as a dependency, and so it goes right into
the application's WEB-INF/lib. I believe you are right, with Java 6 SE
and up, there is a JAX-B 2.0 implementation bundled. I hadn't tried to
operate without it, even though it seems like I should be able to do
so..
Do you think that this is related to Apache Wink creating a
ThreadLocal, though? The core problem I am trying to address now is
that there may be a memory leak by using a ThreadLocal by Apache Wink.
I contacted them, hopefully they will respond.
-Jesse
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: checkThreadLocalMapForLeaks: com.sun.xml.bind.v2.runtime.Coordinator
Greetings,
On Mon, May 20, 2013 at 4:17 AM, Mark Thomas wrote:
> Tomcat is not responsible for any ThreadLocals your application creates.
> If your application creates them (or causes them to be created), your
> application needs to clean them up.
Ok, I understand.
> Depending on exactly what triggers the creation of this ThreadLocal and
> how it is used, there may be something we can add to Tomcat's
> JreMemoryLeakProtectionListener to avoid this memory leak.
I asked on the Apache Wink user list for assistance explaining the use
of this com.sun.xml.bind.v2.runtime.Coordinator and how I can protect
against a memory leak with application loop { deploy/redeploy/undeploy
} common for web applications.
If I hear back with any leads for Apache Tomcat to explore I will post here.
Thanks,
-Jesse
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
checkThreadLocalMapForLeaks: com.sun.xml.bind.v2.runtime.Coordinator
Greetings, I am using Apache Tomcat 7.0.40, via IBM Java 7 SR2. I am seeing the following on Tomcat shutdown: org.apache.catalina.loader.WebappClassLoader.checkThreadLocalMapForLeaks The web application [] created a ThreadLocal with key of type [com.sun.xml.bind.v2.runtime.Coordinator$1] (value [com.sun.xml.bind.v2.runtime.Coordinator$1@f9b00906]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@3d8d9b93]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. When I inspect the libraries within the application I find: $ grep com.sun.xml.bind.v2.runtime.Coordinator * Binary file jaxb-impl-2.2.1.1.jar matches Apache Maven dependency:tree shows that this is coming from Apache Wink (wink-common -> wink-client). Is this JAXB ThreadLocal something that Apache Tomcat ought to protect me from? Thank you, -Jesse - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
