You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Daniel Wittenberg <dw...@gmail.com> on 2009/09/30 01:31:07 UTC
errors after install
I'm setting up spacewalk, all default settings, and I'm getting this in
the catalina.out. Any ideas ?
Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing pending
acquires. While trying to acquire a needed new resource, we failed to
succeed more than the maximum number of allowed acquisition attempts
(30).
Thanks,
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by André Warnier <aw...@ice-sa.com>.
Daniel Wittenberg wrote:
> I'm setting up spacewalk, all default settings, and I'm getting this in
> the catalina.out. Any ideas ?
>
> Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask run
> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing pending
> acquires. While trying to acquire a needed new resource, we failed to
> succeed more than the maximum number of allowed acquisition attempts
> (30).
>
http://markmail.org/message/tqrw65zjaqsgsokc#query:+page:1+mid:2ygqrc36ppkwatfa+state:results
See #5
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Peter Crowther <pe...@melandra.com>.
2009/10/1 Daniel Wittenberg <dw...@gmail.com>:
> Actually it does configure it
Good to read, though I'm surprised.
> Actually this time it worked. Not sure what happened last time, but it's
> about 99% working right now.
Great. I wonder what changed?
> Not sure I agree here. You can easily put httpd configs out there that tell
> how certain apps work. Just dump your configs in /etc/httpd/conf.d and
> good-to-go. Obviously if you just happen to dfefine another alias on your
> server for /rhn/ you're gonna have issues, but otherwise there's no
> problems, and it pretty common to see web-apps that install configs on how
> to make it work.
I was more thinking from the Tomcat end, as you may end up having to
make mods to the default Tomcat connectors.
> BTW 12 years ago would have been like Red Hat Linux 5.0, way before fedora
Yep. I have a boxed RedHat 4.0, somewhere. And an Yggdrasil Linux CD
that was based around kernel version 1.0.0 :-). They're probably in
the old office, along with the two BBC Micros, Acorn A3000, Amiga 1000
and the bits of the Sun-2 I didn't pass on to the local museum...
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Daniel Wittenberg <dw...@gmail.com>.
On Oct 1, 2009, at 10:21 AM, Peter Crowther wrote:
> 2009/10/1 Daniel Wittenberg <dw...@gmail.com>:
>> I know spacewalk doesn't have it's own tomcat, the install pulls
>> everything
>> it needs
>
> Yes, but it probably doesn't *configure* it. The spacewalk RPM
> probably expresses a dependency on Apache httpd and a dependency on
> Tomcat. So you'll get a bare httpd from its rpm (which will not be
> configured to talk to Tomcat) and a bare Tomcat from its RPM (which
> will not be configured to talk to httpd, might be of a different
> version to the one Spacewalk is expecting if it expresses a >=
> dependency, and which appears to have at least a docbase/appbase
> issue). I presume you'll then have to configure them to talk to each
> other, via mod_jk, mod_proxy or mod_proxy_ajp.
Actually it does configure it
>> I'm thinking what might work best is just to wipe the VM with a
>> fresh OS
>> install and try the install again and see what happens.
>
> I suspect you'll get to exactly the same place
Actually this time it worked. Not sure what happened last time, but
it's about 99% working right now.
>> I got no errors
>> during the install, so it all appeared to be working until I went
>> to login
>
> You wouldn't - the bits are installed, the files are in the right
> place, I just suspect that the Spacewalk RPM is not set up to tell
> httpd how to talk to Tomcat. Nor should it - otherwise it has the
> potential to break a working system.
Not sure I agree here. You can easily put httpd configs out there
that tell how certain apps work. Just dump your configs in /etc/httpd/
conf.d and good-to-go. Obviously if you just happen to dfefine
another alias on your server for /rhn/ you're gonna have issues, but
otherwise there's no problems, and it pretty common to see web-apps
that install configs on how to make it work.
> Looking at the wiki, I also cannot see how spacewalk-setup connects
> httpd with Tomcat.
>
>> RHN is the management console that on the commercial side Red Hat
>> uses to
>> manage the Red Hat Enterprise licenses and clients, this is just the
>> opensource version of that.
>
> Ah. <rant> And it appears to have DeadRat's now-traditional poor
> quality - you'd think they would at least check for warnings before
> releasing. I used to like that distro 12 years ago, but the quality
> went downhill sharply once they split Fedora off. </rant>
>
> - Peter
Yeah, sometimes I wonder about some of the apps when they get moved to
opensource, like RHN, they get better but makes you wonder how this is
working internally for them.
BTW 12 years ago would have been like Red Hat Linux 5.0, way before
fedora :)
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Peter Crowther <pe...@melandra.com>.
2009/10/1 Daniel Wittenberg <dw...@gmail.com>:
> I know spacewalk doesn't have it's own tomcat, the install pulls everything
> it needs
Yes, but it probably doesn't *configure* it. The spacewalk RPM
probably expresses a dependency on Apache httpd and a dependency on
Tomcat. So you'll get a bare httpd from its rpm (which will not be
configured to talk to Tomcat) and a bare Tomcat from its RPM (which
will not be configured to talk to httpd, might be of a different
version to the one Spacewalk is expecting if it expresses a >=
dependency, and which appears to have at least a docbase/appbase
issue). I presume you'll then have to configure them to talk to each
other, via mod_jk, mod_proxy or mod_proxy_ajp.
> I'm thinking what might work best is just to wipe the VM with a fresh OS
> install and try the install again and see what happens.
I suspect you'll get to exactly the same place.
> I got no errors
> during the install, so it all appeared to be working until I went to login
You wouldn't - the bits are installed, the files are in the right
place, I just suspect that the Spacewalk RPM is not set up to tell
httpd how to talk to Tomcat. Nor should it - otherwise it has the
potential to break a working system.
Looking at the wiki, I also cannot see how spacewalk-setup connects
httpd with Tomcat.
> RHN is the management console that on the commercial side Red Hat uses to
> manage the Red Hat Enterprise licenses and clients, this is just the
> opensource version of that.
Ah. <rant> And it appears to have DeadRat's now-traditional poor
quality - you'd think they would at least check for warnings before
releasing. I used to like that distro 12 years ago, but the quality
went downhill sharply once they split Fedora off. </rant>
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Daniel Wittenberg <dw...@gmail.com>.
I know spacewalk doesn't have it's own tomcat, the install pulls
everything it needs it, so I started with a base stripped down CentOS,
followed their instructions and this is where I got from using the
standard installer. There is also a yum repo for the packages so it's
at the latest version. I'm thinking what might work best is just to
wipe the VM with a fresh OS install and try the install again and see
what happens. I got no errors during the install, so it all appeared
to be working until I went to login :)
I'll probably poke at this a little more, because despite the
potentially broken/outdated package that won't change if I re-install,
it seems like something might be missing from the config that if I
could get that it'd be working.
RHN is the management console that on the commercial side Red Hat uses
to manage the Red Hat Enterprise licenses and clients, this is just
the opensource version of that.
Dan
On Oct 1, 2009, at 3:11 AM, André Warnier wrote:
> To agree and augment on everything Peter wrote, the whole thing
> stinks of a very broken installation and configuration package, or
> packages.
> Not for lack of desire to help, but I believe you should really go
> back to the spacewalker (or CentOS) help forum, and enquire there
> about working packages for your specific platform.
> We have no idea what is needed by this application. It seems that
> you have indeed some kind of Tomcat installed now, with some /rhn
> webapp half-installed in it. On the other hand, some other bits and
> pieces needed by that /rhn webapp appear to be missing, and some
> standard parts of Tomcat also (like the version.sh script).
> Even the standard Tomcat 8005 shutdown port doesn't seem to be
> there, which as Peter wrote is very strange.
> I am starting to wonder if this CentOS spacewalker package is not
> installing its own embedded Tomcat, which conflicts with another one
> already installed.
>
> Alternatively, you could try to de-install what you have installed
> so far, then install *only* the latest CentOS pure-Tomcat package
> you can find, and test if that one, on its own, works.
> Test it by simply calling the URL http://your-hostname:8080 in your
> browser. You should then get some Tomcat page, with an easily
> recognisable cat on it.
> Most standard Tomcat packages I have seen so far, have Tomcat
> configured so that it will, by default, listen on 3 ports :
> - port 8005 : that's Tomcat's "shutdown port"; you see it in the
> server.xml file as an attribute to the <Server> tag.
> - port 8080 : that's Tomcat's standard HTTP connector, which allows
> you to use it as a standard webserver (that one, you will find in a
> <Connector ... protocol="HTTP"> tag in server.xml
> - port 8009 : that is Tomcat's standard listening port for the AJP
> connector, another <Connector> tag in server.xml. This one may or
> may not be activated, depending on how the CentOS packagers
> structured their stuff. It may only get installed/activated if you
> install another complementary package containing mod_jk or
> mod_proxy_ajp, and this complementary package may in turn depend on
> the Apache httpd package being installed.
> And so on...
> Variations are endless, and depend on the whims and competence of
> whoever creates these packages for each platform.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by André Warnier <aw...@ice-sa.com>.
To agree and augment on everything Peter wrote, the whole thing stinks
of a very broken installation and configuration package, or packages.
Not for lack of desire to help, but I believe you should really go back
to the spacewalker (or CentOS) help forum, and enquire there about
working packages for your specific platform.
We have no idea what is needed by this application. It seems that you
have indeed some kind of Tomcat installed now, with some /rhn webapp
half-installed in it. On the other hand, some other bits and pieces
needed by that /rhn webapp appear to be missing, and some standard parts
of Tomcat also (like the version.sh script).
Even the standard Tomcat 8005 shutdown port doesn't seem to be there,
which as Peter wrote is very strange.
I am starting to wonder if this CentOS spacewalker package is not
installing its own embedded Tomcat, which conflicts with another one
already installed.
Alternatively, you could try to de-install what you have installed so
far, then install *only* the latest CentOS pure-Tomcat package you can
find, and test if that one, on its own, works.
Test it by simply calling the URL http://your-hostname:8080 in your
browser. You should then get some Tomcat page, with an easily
recognisable cat on it.
Most standard Tomcat packages I have seen so far, have Tomcat configured
so that it will, by default, listen on 3 ports :
- port 8005 : that's Tomcat's "shutdown port"; you see it in the
server.xml file as an attribute to the <Server> tag.
- port 8080 : that's Tomcat's standard HTTP connector, which allows you
to use it as a standard webserver (that one, you will find in a
<Connector ... protocol="HTTP"> tag in server.xml
- port 8009 : that is Tomcat's standard listening port for the AJP
connector, another <Connector> tag in server.xml. This one may or may
not be activated, depending on how the CentOS packagers structured their
stuff. It may only get installed/activated if you install another
complementary package containing mod_jk or mod_proxy_ajp, and this
complementary package may in turn depend on the Apache httpd package
being installed.
And so on...
Variations are endless, and depend on the whims and competence of
whoever creates these packages for each platform.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Peter Crowther <pe...@melandra.com>.
Yes, that helps considerably.
2009/10/1 Daniel Wittenberg <dw...@gmail.com>:
>>> Daniel Wittenberg wrote:
> tomcat5-5.5.23-0jpp.7.el5_3.2
Great. Not the most up-to-date, but at least 5.5.23 isn't *too* ancient :-).
> INFO: The Apache Tomcat Native library which allows optimal performance
> in production environments was not found on the
> java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/opt/oracle/lib:/usr/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Not a problem, Tomcat will run fine without it.
> WARNING: A docBase /var/lib/tomcat5/webapps/rhn inside the host appBase
> has been specified, and will be ignored
That's some very poor configuration somewhere in your conf/server.xml
- if that's the CentOS default, then some packager needs their wrists
slapping. Hard.
> Sep 30, 2009 8:13:08 PM org.apache.catalina.loader.WebappClassLoader
> validateJarFile
> INFO:
> validateJarFile(/usr/share/tomcat5/webapps/rhn/WEB-INF/lib/jspapi.jar) -
> jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> javax/servlet/jsp/JspPage.class
Same again - if rhn is a RedHat-supplied app, including the API jars
is Very Poor Practise. Tomcat's smart enough to ignore them, but it's
a good indication that whoever wrote this didn't know what they were
doing.
> Sep 30, 2009 8:13:44 PM com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask run
> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask@60ab835a -- Acquisition Attempt Failed!!! Clearing pending
> acquires. While trying to acquire a needed new resource, we failed to
> succeed more than the maximum number of allowed acquisition attempts
> (30).
Looks like the app's using c3p0 connection pooling. I think that's a
consequence of...
> 2009-09-30 20:13:44,630 [main] WARN org.hibernate.cfg.SettingsFactory -
> Could not obtain connection metadata
> java.sql.SQLException: Connections could not be acquired from the
> underlying database!
> at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:104)
[...]
> at com.redhat.rhn.common.hibernate.ConnectionManager.createSessionFactory(ConnectionManager.java:173)
That's the rhn app being unable to get hold of a database connection,
probably because you haven't configured one. Do you need this app or
can you bin it?
> Looks like the only ports it's opening is 8080:
> # netstat -nap |grep -i listen
> tcp 0 0 :::8080 :::*
> LISTEN 2651/java
Then I'm very worried, as you should at least have a shutdown port
(usually 8005).
Could you post your conf/server.xml here, preferably with comments
stripped and any sensitive hostnames, usernames and passwords blanked?
That would tell us a lot more. You might have to hunt for it, but it
should be a file called server.xml *somewhere* on your system!
It looks like Spacewalk is trying to talk from Apache httpd to Tomcat
via AJP (which uses port 8009), but Tomcat's not configured with an
AJP connector to listen on 8009. That would certainly give the
symptoms you're observing.
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Daniel Wittenberg <dw...@gmail.com>.
>> Daniel Wittenberg wrote:
> >>> I'm setting up spacewalk, all default settings, and I'm getting this in
> >>> the catalina.out. Any ideas ?
> >>> Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
> >>> $AcquireTask run
> >>> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
> >>> $AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing pending
> >>> acquires. While trying to acquire a needed new resource, we failed to
> >>> succeed more than the maximum number of allowed acquisition attempts
> >>> (30).
I don't see that the RPM's include version.sh, so the closest I know how
to get:
tomcat5-5.5.23-0jpp.7.el5_3.2
I stopped tomcat, cleared the log and started again and got this:
Sep 30, 2009 8:13:08 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the
java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/opt/oracle/lib:/usr/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
..
Sep 30, 2009 8:13:08 PM org.apache.catalina.startup.HostConfig
deployDescriptor
WARNING: A docBase /var/lib/tomcat5/webapps/rhn inside the host appBase
has been specified, and will be ignored
Sep 30, 2009 8:13:08 PM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/usr/share/tomcat5/webapps/rhn/WEB-INF/lib/jspapi.jar) -
jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/jsp/JspPage.class
Sep 30, 2009 8:13:44 PM com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask@60ab835a -- Acquisition Attempt Failed!!! Clearing pending
acquires. While trying to acquire a needed new resource, we failed to
succeed more than the maximum number of allowed acquisition attempts
(30).
Sep 30, 2009 8:13:44 PM com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask@1c3cbb4b -- Acquisition Attempt Failed!!! Clearing pending
acquires. While trying to acquire a needed new resource, we failed to
succeed more than the maximum number of allowed acquisition attempts
(30).
2009-09-30 20:13:44,630 [main] WARN org.hibernate.cfg.SettingsFactory -
Could not obtain connection metadata
java.sql.SQLException: Connections could not be acquired from the
underlying database!
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:104)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:236)
at
com.mchange.v2.c3p0.PoolBackedDataSource.getConnection(PoolBackedDataSource.java:94)
at
org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:56)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
at
com.redhat.rhn.common.hibernate.ConnectionManager.createSessionFactory(ConnectionManager.java:173)
at
com.redhat.rhn.common.hibernate.ConnectionManager.initialize(ConnectionManager.java:119)
at
com.redhat.rhn.common.hibernate.HibernateFactory.createSessionFactory(HibernateFactory.java:91)
at
com.redhat.rhn.webapp.RhnServletListener.startHibernate(RhnServletListener.java:89)
at
com.redhat.rhn.webapp.RhnServletListener.contextInitialized(RhnServletListener.java:111)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4212)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:448)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A
ResourcePool could not acquire a resource from its primary factory or
source.
at
com.mchange.v2.resourcepool.BasicResourcePool.awaitAcquire(BasicResourcePool.java:970)
at
com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:208)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:232)
... 34 more
Looks like the only ports it's opening is 8080:
# netstat -nap |grep -i listen
tcp 0 0 :::8080 :::*
LISTEN 2651/java
# ps -ef |grep 2651
tomcat 2651 1 32 20:40 ?
00:00:08 /usr/lib/jvm/java/bin/java -ea -Xms256m -Xmx256m
-Djava.awt.headless=true
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
-XX:MaxNewSize=256 -XX:-UseConcMarkSweepGC
-Dcatalina.ext.dirs=/usr/share/tomcat5/shared/lib:/usr/share/tomcat5/common/lib -Djava.endorsed.dirs=/usr/share/tomcat5/common/endorsed -classpath /usr/lib/jvm/java/lib/tools.jar:/usr/share/tomcat5/bin/bootstrap.jar:/usr/share/tomcat5/bin/commons-logging-api.jar:/usr/share/java/mx4j/mx4j-impl.jar:/usr/share/java/mx4j/mx4j-jmx.jar -Dcatalina.base=/usr/share/tomcat5 -Dcatalina.home=/usr/share/tomcat5 -Djava.io.tmpdir=/usr/share/tomcat5/temp org.apache.catalina.startup.Bootstrap start
Does that help more ?
Thanks,
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: errors after install
Posted by Daniel Wittenberg <dw...@gmail.com>.
I've done this and responses I got were "it appears to be a tomcat issue
so maybe try there"....so....but I will gather the data requested and
get back...
Dan
On Wed, 2009-09-30 at 14:31 -0500, Caldarale, Charles R wrote:
> > From: André Warnier [mailto:aw@ice-sa.com]
> > Subject: Re: errors after install
> >
> > So if you don't willingly start providing the information requested,
> > I'm gonna wash my hands off it all, and leave you in the hands of
> > Chuck or Pid here. Then, you'll see what "abrupt" means.
> > ;-)
>
> Or, the OP could just take the problem to the spacewalk mailing list - where it belongs.
> http://www.redhat.com/mailman/listinfo/spacewalk-list
>
> Just hope you don't get the following:
> http://www.redhat.com/spacewalk/
>
> Content Encoding Error
> The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
> * Please contact the website owners to inform them of this problem.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: errors after install
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: André Warnier [mailto:aw@ice-sa.com]
> Subject: Re: errors after install
>
> So if you don't willingly start providing the information requested,
> I'm gonna wash my hands off it all, and leave you in the hands of
> Chuck or Pid here. Then, you'll see what "abrupt" means.
> ;-)
Or, the OP could just take the problem to the spacewalk mailing list - where it belongs.
http://www.redhat.com/mailman/listinfo/spacewalk-list
Just hope you don't get the following:
http://www.redhat.com/spacewalk/
Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
* Please contact the website owners to inform them of this problem.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by André Warnier <aw...@ice-sa.com>.
Daniel Wittenberg wrote:
> Very true, sorry for so vague. So selinux is turned off, I don't enable
> unless I have to most of the time.
> - Spacewalk = RHN = Linux server management tool
> - It is running on CentOS 5 and uses latest tomcat5 RPM's
>
> The problem is I know little to nothing about tomcat, I only figured
> those were tomcat errors since they were in the catalina.out, but from
> what you are saying other webapps that run under tomcat can log there too?
>
Yes. Not the purest recommended practice, but yes.
> I mainly posted here because spacewalk isn't working, complains that it
> can't talk to tomcat on port 8009 (ajp?),
well, that something else you never mentioned before. At least not here..
and notice these errors and
> figured tomcat was having issues.
>
> That help?
>
A bit, but it's still vague.
For instance, there are umpteen versions of tomcat 5.0.x and tomcat
5.5.x around, and they are quite different, and we have no idea what
CentOS 5 might, in their wisdom, consider "the latest rpms".
Running the "version.sh" script in tomcat/bin, as previously requested,
and pasting the result here would go a long way to provide accurate
information to help you.
Also, providing the beginning of catalina.out, after a cleanup and a
fresh tomcat start, also as previously requested, would probably tell us
right away if there is a problem with port 8009, and what it might be.
It's like pulling teeth here..
See, I have no wish to start learning spacewalking unless I have to, and
so far it is not very clear why or how that thing would want to talk to
Tomcat on its AJP Connector, nor if Tomcat is even trying to provide one.
So if you don't willingly start providing the information requested, I'm
gonna wash my hands off it all, and leave you in the hands of Chuck or
Pid here. Then, you'll see what "abrupt" means.
;-)
To gain some time, also look around for a tomcat "server.xml" file, and
paste here parts of its content : specifically, any uncommented XML
<Connector ... > tags you find in there. That server.xml file may be
either in (tomcat_install_dir)/conf, or maybe in /etc/tomcat5???
(That would tell us which server ports Tomcat is *supposed* to listen on).
Oh, and something else : usually when Tomcat does not, by default, open
an AJPconnector on port 8009, it is either because it is not configured
to do so, or because it is, but something else is already using that
port. catalina.out would tell us, but if you feel adventurous you may
want to try the command :
netstat -pan | grep 8009
at a moment when Tomcat is NOT running. Just to see if you're fishing
something.
Then you can start Tomcat and do it again, and tell us about the result
of both.
> Thanks,
> Dan
>
> On Sep 29, 2009, at 7:17 PM, André Warnier wrote:
>
>> Daniel Wittenberg wrote:
>>> I'm setting up spacewalk, all default settings, and I'm getting this in
>>> the catalina.out. Any ideas ?
>>> Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
>>> $AcquireTask run
>>> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
>>> $AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing pending
>>> acquires. While trying to acquire a needed new resource, we failed to
>>> succeed more than the maximum number of allowed acquisition attempts
>>> (30).
>> Hi.
>> We'd be really good if we solved it on the base of the info above,
>> wouldn't we ?
>> So I'll try : selinux ?
>>
>> Other than that, if you really want help about this, you'll have to do
>> a bit better.
>> Admittedly, the mention of "catalina.out" up there is a clue that
>> there might, maybe, be a Tomcat installed on your system.
>> The error message above however is no such clue. It does not seem to
>> come from any Tomcat code.
>> So you might start by telling us a bit more about
>> - what "spacewalk" is supposed to be
>> - if it is supposed to contain a Tomcat
>> - if yes, which version
>> - on what platform (OS) this is happening
>> - since the above does not seem to be really a Tomcat problem, make a
>> little effort at convincing us that it is, by :
>> - stopping this spacewalk and the perhaps associated Tomcat
>> - delete all logfiles of either that you can find
>> - restart the application, or preferably, only Tomcat
>> - then send us a new copy of the catalina.out, showing any messages
>> that look like errors or warnings, but from the moment when Tomcat
>> starts up
>> - if you find the base Tomcat installation directory, and find a
>> "bin" sub-directory in it, and in there you find a "version.sh" or
>> "version.bat" script, run it in a console window, and paste the output
>> in your next message.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by Daniel Wittenberg <dw...@gmail.com>.
Very true, sorry for so vague. So selinux is turned off, I don't
enable unless I have to most of the time.
- Spacewalk = RHN = Linux server management tool
- It is running on CentOS 5 and uses latest tomcat5 RPM's
The problem is I know little to nothing about tomcat, I only figured
those were tomcat errors since they were in the catalina.out, but from
what you are saying other webapps that run under tomcat can log there
too?
I mainly posted here because spacewalk isn't working, complains that
it can't talk to tomcat on port 8009 (ajp?), and notice these errors
and figured tomcat was having issues.
That help?
Thanks,
Dan
On Sep 29, 2009, at 7:17 PM, André Warnier wrote:
> Daniel Wittenberg wrote:
>> I'm setting up spacewalk, all default settings, and I'm getting
>> this in
>> the catalina.out. Any ideas ?
>> Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
>> $AcquireTask run
>> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
>> $AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing
>> pending
>> acquires. While trying to acquire a needed new resource, we failed to
>> succeed more than the maximum number of allowed acquisition attempts
>> (30).
> Hi.
> We'd be really good if we solved it on the base of the info above,
> wouldn't we ?
> So I'll try : selinux ?
>
> Other than that, if you really want help about this, you'll have to
> do a bit better.
> Admittedly, the mention of "catalina.out" up there is a clue that
> there might, maybe, be a Tomcat installed on your system.
> The error message above however is no such clue. It does not seem
> to come from any Tomcat code.
> So you might start by telling us a bit more about
> - what "spacewalk" is supposed to be
> - if it is supposed to contain a Tomcat
> - if yes, which version
> - on what platform (OS) this is happening
> - since the above does not seem to be really a Tomcat problem, make
> a little effort at convincing us that it is, by :
> - stopping this spacewalk and the perhaps associated Tomcat
> - delete all logfiles of either that you can find
> - restart the application, or preferably, only Tomcat
> - then send us a new copy of the catalina.out, showing any messages
> that look like errors or warnings, but from the moment when Tomcat
> starts up
> - if you find the base Tomcat installation directory, and find a
> "bin" sub-directory in it, and in there you find a "version.sh" or
> "version.bat" script, run it in a console window, and paste the
> output in your next message.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: errors after install
Posted by André Warnier <aw...@ice-sa.com>.
Daniel Wittenberg wrote:
> I'm setting up spacewalk, all default settings, and I'm getting this in
> the catalina.out. Any ideas ?
>
> Sep 29, 2009 7:19:34 PM com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask run
> WARNING: com.mchange.v2.resourcepool.BasicResourcePool
> $AcquireTask@7da79447 -- Acquisition Attempt Failed!!! Clearing pending
> acquires. While trying to acquire a needed new resource, we failed to
> succeed more than the maximum number of allowed acquisition attempts
> (30).
>
Hi.
We'd be really good if we solved it on the base of the info above,
wouldn't we ?
So I'll try : selinux ?
Other than that, if you really want help about this, you'll have to do a
bit better.
Admittedly, the mention of "catalina.out" up there is a clue that there
might, maybe, be a Tomcat installed on your system.
The error message above however is no such clue. It does not seem to
come from any Tomcat code.
So you might start by telling us a bit more about
- what "spacewalk" is supposed to be
- if it is supposed to contain a Tomcat
- if yes, which version
- on what platform (OS) this is happening
- since the above does not seem to be really a Tomcat problem, make a
little effort at convincing us that it is, by :
- stopping this spacewalk and the perhaps associated Tomcat
- delete all logfiles of either that you can find
- restart the application, or preferably, only Tomcat
- then send us a new copy of the catalina.out, showing any messages
that look like errors or warnings, but from the moment when Tomcat starts up
- if you find the base Tomcat installation directory, and find a
"bin" sub-directory in it, and in there you find a "version.sh" or
"version.bat" script, run it in a console window, and paste the output
in your next message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org