You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Dave Colasurdo <da...@earthlink.net> on 2005/12/05 16:28:29 UTC
Startup Warning related to running Tomcat Examples on Jetty
GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
examples seem to install and run fine on both Tomcat and Jetty. There
is a warning message (see below) that is spit out during Jetty startup.
There is no such message for Tomcat. Can someone please help shed
some light on why the warning is being emitted. I've attached the
relevant portions of my geronimo.log.
Thanks
-Dave-
Starting Geronimo Application Server
[******************] 100% 27s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
1527 0.0.0.0 Derby Connector
4201 127.0.0.1 ActiveIO Connector EJB
4242 0.0.0.0 Remote Login Listener
8080 0.0.0.0 Jetty Connector HTTP
8443 0.0.0.0 Jetty Connector HTTPS
61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules:
WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
RAR: geronimo/system-database/1.0-SNAPSHOT/car
EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
RAR: geronimo/activemq/1.0-SNAPSHOT/car
WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
Web Applications:
http://linux-009037214145:8080/
http://linux-009037214145:8080/console
http://linux-009037214145:8080/console-standard
http://linux-009037214145:8080/jsp-examples
http://linux-009037214145:8080/juddi
http://linux-009037214145:8080/servlets-examples
WARNING: Some GBeans were not started successfully:
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
Geronimo Application Server started
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by anita kulshreshtha <a_...@yahoo.com>.
yes, tomcat does not have filtermappings and
servlets as Gbeans, hence this error does not occur.
Thanks
Anita
--- Jan Bartel <ja...@mortbay.com> wrote:
> It might be that Jetty has a lot more instrumented
> as gbeans
> (eg filtermappings, servletholders etc etc) than
> tomcat so
> we see this error message because the gbean
> relationship
> level is awry, whereas if tomcat is not so
> instrumented with
> the filtermappings etc as gbeans then this error
> can't occur.
>
> Jan
>
> Greg Wilkins wrote:
> > Also might be an idea to check the tomcat deployer
> - because either it
> > is suppressing a warning or it has the invoker
> servlet configured by default.
> > neither are optimal
> >
> > cheers
> >
> >
>
>
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Jan Bartel <ja...@mortbay.com>.
It might be that Jetty has a lot more instrumented as gbeans
(eg filtermappings, servletholders etc etc) than tomcat so
we see this error message because the gbean relationship
level is awry, whereas if tomcat is not so instrumented with
the filtermappings etc as gbeans then this error can't occur.
Jan
Greg Wilkins wrote:
> Also might be an idea to check the tomcat deployer - because either it
> is suppressing a warning or it has the invoker servlet configured by default.
> neither are optimal
>
> cheers
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
Yep..
Jan Bartel wrote:
> Dave,
>
> Did you also change the line on the jsp-examples to remove the
> "of course we recommend Tomcat"?
>
> cheers
> Jan
>
>
>
> Dave Colasurdo wrote:
>
>>Thanks for the tip! Have updated the wars and renamed them. Also have
>>created a patch to update the dependencies that reference the war files.
>> All have been attached to:
>>http://issues.apache.org/jira/browse/GERONIMO-1299
>>
>>Can someone please publish the wars to ibiblio
>>(http://www.ibiblio.org/maven/geronimo/wars/) and commit the patch?
>>
>>Thanks
>>-Dave-
>>
>>Dain Sundstrom wrote:
>>
>>
>>>You can't modify an archive once published. You will have to create
>>>a new one with a -build number on the end. I suggest something like:
>>>
>>>geronimo-servlet-examples-tomcat-5.5.12-1.war
>>>
>>>Anyway, you need to put a -something after the version number.
>>>
>>>-dain
>>>
>>>
>>
>
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Jan Bartel <ja...@mortbay.com>.
Dave,
Did you also change the line on the jsp-examples to remove the
"of course we recommend Tomcat"?
cheers
Jan
Dave Colasurdo wrote:
> Thanks for the tip! Have updated the wars and renamed them. Also have
> created a patch to update the dependencies that reference the war files.
> All have been attached to:
> http://issues.apache.org/jira/browse/GERONIMO-1299
>
> Can someone please publish the wars to ibiblio
> (http://www.ibiblio.org/maven/geronimo/wars/) and commit the patch?
>
> Thanks
> -Dave-
>
> Dain Sundstrom wrote:
>
>> You can't modify an archive once published. You will have to create
>> a new one with a -build number on the end. I suggest something like:
>>
>> geronimo-servlet-examples-tomcat-5.5.12-1.war
>>
>> Anyway, you need to put a -something after the version number.
>>
>> -dain
>>
>>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
Thanks for the tip! Have updated the wars and renamed them. Also have
created a patch to update the dependencies that reference the war files.
All have been attached to:
http://issues.apache.org/jira/browse/GERONIMO-1299
Can someone please publish the wars to ibiblio
(http://www.ibiblio.org/maven/geronimo/wars/) and commit the patch?
Thanks
-Dave-
Dain Sundstrom wrote:
> You can't modify an archive once published. You will have to create a
> new one with a -build number on the end. I suggest something like:
>
> geronimo-servlet-examples-tomcat-5.5.12-1.war
>
> Anyway, you need to put a -something after the version number.
>
> -dain
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dain Sundstrom <da...@iq80.com>.
On Dec 6, 2005, at 5:46 AM, Dave Colasurdo wrote:
> Well, looks like options 3 and 4 have been eliminated from the list
> below. I'd prefer option 1. While not the ideal resolution, it
> does allow for a quick resolution and provides the examples for
> both tomcat and jetty. Are there any major objections to this
> approach?
>
>
> 1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in
> ibiblio and remove the invoker reference.
> If we do this we should also remove the following reference from
> the jsp-examples main page: "These examples will only work when
> these pages are being served by a servlet engine; of course, we
> recommend Tomcat"
You can't modify an archive once published. You will have to create
a new one with a -build number on the end. I suggest something like:
geronimo-servlet-examples-tomcat-5.5.12-1.war
Anyway, you need to put a -something after the version number.
-dain
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
Ummmm... I've already cracked open the wars to remove the "we recommend
tomcat" comments as well as remove the invoker reference. The updated
wars were published to svn.apache.org/repository/geronimo/wars and there
is a patch in JIRA 1299 to pickup the new dependency.
David Jencks wrote:
> Thinking about this again, I think (4) is the best option. I think we
> can do this by adding a gbean to the plan for this app that deploys the
> invoker servlet "by hand", similarly to the default servlets in the
> jetty deployer plan. You need to include a reference to the web-app
> gbean so the servletholder gbean realizes it is really part of a web app
> and not a default. I think you need to specify the gbeanName completely
> also since the j2eeType should be Servlet (?) rather than DefaultServlet(?)
>
> thanks
> david jencks
>
> On Dec 6, 2005, at 5:46 AM, Dave Colasurdo wrote:
>
>> Well, looks like options 3 and 4 have been eliminated from the list
>> below. I'd prefer option 1. While not the ideal resolution, it does
>> allow for a quick resolution and provides the examples for both tomcat
>> and jetty. Are there any major objections to this approach?
>>
>>
>> 1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio
>> and remove the invoker reference.
>> If we do this we should also remove the following reference from the
>> jsp-examples main page: "These examples will only work when these
>> pages are being served by a servlet engine; of course, we recommend
>> Tomcat"
>>
>> We can do this ourselves or ask Tomcat to do it..
>>
>> 2) Only make the example(s) available on Tomcat distributions.
>>
>> 3) Install on Jetty and live with the "WARNING: Some GBeans were not
>> started successfully:" Or find a way to ignore and/or suppress the
>> WARNING.
>>
>> 4) Figure out a way to leverage the invoker servlet in Jetty. It
>> seems they do have one. Is the web.xml syntax different?
>>
>> Greg Wilkins wrote:
>>
>>> David Jencks wrote:
>>>
>>>> When I wrote the jetty deployer I studied the spec and could not
>>>> find any support for this kind of dynamic servlet that isn't listed
>>>> in web.xml, so I didn't try to put any in. If someone has a good
>>>> argument that it is consistent with the spec (I thought it was not),
>>>> we could try something. We might be able to use another default
>>>> servlet like the static content one. If we do this I think we need
>>>> a way to turn it on and off: this seems like it will lead us to
>>>> having the deployer know about all or many of the default servlets,
>>>> something I am not entirely thrilled with.
>>>> thanks
>>>> david jencks
>>>
>>> +1. The invoker is not a very secure mechanism - it allows any servlet
>>> on the classpath to be run - even if you have not configured it.
>>> It is hard to know exactly all the servlets that may lurk on a
>>> classpath or
>>> even to know what the full classpath is.
>>> Jetty and Tomcat by default have the invoker servlet turned off and
>>> nobody
>>> every complains (to Jetty anyway).
>>> So I would suggest either living with the warning or removing the
>>> invoker
>>> mapping from the demos.
>>> Also might be an idea to check the tomcat deployer - because either
>>> it is suppressing a warning or it has the invoker servlet configured
>>> by default.
>>> neither are optimal cheers
>>
>>
>
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by David Jencks <da...@yahoo.com>.
Thinking about this again, I think (4) is the best option. I think we
can do this by adding a gbean to the plan for this app that deploys the
invoker servlet "by hand", similarly to the default servlets in the
jetty deployer plan. You need to include a reference to the web-app
gbean so the servletholder gbean realizes it is really part of a web
app and not a default. I think you need to specify the gbeanName
completely also since the j2eeType should be Servlet (?) rather than
DefaultServlet(?)
thanks
david jencks
On Dec 6, 2005, at 5:46 AM, Dave Colasurdo wrote:
> Well, looks like options 3 and 4 have been eliminated from the list
> below. I'd prefer option 1. While not the ideal resolution, it does
> allow for a quick resolution and provides the examples for both tomcat
> and jetty. Are there any major objections to this approach?
>
>
> 1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio
> and remove the invoker reference.
> If we do this we should also remove the following reference from the
> jsp-examples main page: "These examples will only work when these
> pages are being served by a servlet engine; of course, we recommend
> Tomcat"
>
> We can do this ourselves or ask Tomcat to do it..
>
> 2) Only make the example(s) available on Tomcat distributions.
>
> 3) Install on Jetty and live with the "WARNING: Some GBeans were not
> started successfully:" Or find a way to ignore and/or suppress the
> WARNING.
>
> 4) Figure out a way to leverage the invoker servlet in Jetty. It
> seems they do have one. Is the web.xml syntax different?
>
> Greg Wilkins wrote:
>> David Jencks wrote:
>>> When I wrote the jetty deployer I studied the spec and could not
>>> find any support for this kind of dynamic servlet that isn't listed
>>> in web.xml, so I didn't try to put any in. If someone has a good
>>> argument that it is consistent with the spec (I thought it was not),
>>> we could try something. We might be able to use another default
>>> servlet like the static content one. If we do this I think we need
>>> a way to turn it on and off: this seems like it will lead us to
>>> having the deployer know about all or many of the default servlets,
>>> something I am not entirely thrilled with.
>>> thanks
>>> david jencks
>> +1. The invoker is not a very secure mechanism - it allows any
>> servlet
>> on the classpath to be run - even if you have not configured it.
>> It is hard to know exactly all the servlets that may lurk on a
>> classpath or
>> even to know what the full classpath is.
>> Jetty and Tomcat by default have the invoker servlet turned off and
>> nobody
>> every complains (to Jetty anyway).
>> So I would suggest either living with the warning or removing the
>> invoker
>> mapping from the demos.
>> Also might be an idea to check the tomcat deployer - because either
>> it is suppressing a warning or it has the invoker servlet configured
>> by default.
>> neither are optimal cheers
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
Well, looks like options 3 and 4 have been eliminated from the list
below. I'd prefer option 1. While not the ideal resolution, it does
allow for a quick resolution and provides the examples for both tomcat
and jetty. Are there any major objections to this approach?
1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio and
remove the invoker reference.
If we do this we should also remove the following reference from the
jsp-examples main page: "These examples will only work when these pages
are being served by a servlet engine; of course, we recommend Tomcat"
We can do this ourselves or ask Tomcat to do it..
2) Only make the example(s) available on Tomcat distributions.
3) Install on Jetty and live with the "WARNING: Some GBeans were not
started successfully:" Or find a way to ignore and/or suppress the WARNING.
4) Figure out a way to leverage the invoker servlet in Jetty. It seems
they do have one. Is the web.xml syntax different?
Greg Wilkins wrote:
>
> David Jencks wrote:
>
>
>>When I wrote the jetty deployer I studied the spec and could not find
>>any support for this kind of dynamic servlet that isn't listed in
>>web.xml, so I didn't try to put any in. If someone has a good argument
>>that it is consistent with the spec (I thought it was not), we could
>>try something. We might be able to use another default servlet like
>>the static content one. If we do this I think we need a way to turn it
>>on and off: this seems like it will lead us to having the deployer know
>>about all or many of the default servlets, something I am not entirely
>>thrilled with.
>>thanks
>>david jencks
>
>
>
> +1. The invoker is not a very secure mechanism - it allows any servlet
> on the classpath to be run - even if you have not configured it.
> It is hard to know exactly all the servlets that may lurk on a classpath or
> even to know what the full classpath is.
>
> Jetty and Tomcat by default have the invoker servlet turned off and nobody
> every complains (to Jetty anyway).
>
> So I would suggest either living with the warning or removing the invoker
> mapping from the demos.
>
> Also might be an idea to check the tomcat deployer - because either it
> is suppressing a warning or it has the invoker servlet configured by default.
> neither are optimal
>
> cheers
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Greg Wilkins <gr...@mortbay.com>.
David Jencks wrote:
> When I wrote the jetty deployer I studied the spec and could not find
> any support for this kind of dynamic servlet that isn't listed in
> web.xml, so I didn't try to put any in. If someone has a good argument
> that it is consistent with the spec (I thought it was not), we could
> try something. We might be able to use another default servlet like
> the static content one. If we do this I think we need a way to turn it
> on and off: this seems like it will lead us to having the deployer know
> about all or many of the default servlets, something I am not entirely
> thrilled with.
> thanks
> david jencks
+1. The invoker is not a very secure mechanism - it allows any servlet
on the classpath to be run - even if you have not configured it.
It is hard to know exactly all the servlets that may lurk on a classpath or
even to know what the full classpath is.
Jetty and Tomcat by default have the invoker servlet turned off and nobody
every complains (to Jetty anyway).
So I would suggest either living with the warning or removing the invoker
mapping from the demos.
Also might be an idea to check the tomcat deployer - because either it
is suppressing a warning or it has the invoker servlet configured by default.
neither are optimal
cheers
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Greg Wilkins <gr...@mortbay.com>.
David Jencks wrote:
> When I wrote the jetty deployer I studied the spec and could not find
> any support for this kind of dynamic servlet that isn't listed in
> web.xml, so I didn't try to put any in. If someone has a good argument
> that it is consistent with the spec (I thought it was not), we could
> try something. We might be able to use another default servlet like
> the static content one. If we do this I think we need a way to turn it
> on and off: this seems like it will lead us to having the deployer know
> about all or many of the default servlets, something I am not entirely
> thrilled with.
> thanks
> david jencks
+1. The invoker is not a very secure mechanism - it allows any servlet
on the classpath to be run - even if you have not configured it.
It is hard to know exactly all the servlets that may lurk on a classpath or
even to know what the full classpath is.
Jetty and Tomcat by default have the invoker servlet turned off and nobody
every complains (to Jetty anyway).
So I would suggest either living with the warning or removing the invoker
mapping from the demos.
Also might be an idea to check the tomcat deployer - because either it
is suppressing a warning or it has the invoker servlet configured by default.
neither are optimal
cheers
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by David Jencks <da...@yahoo.com>.
On Dec 5, 2005, at 2:08 PM, Dave Colasurdo wrote:
> The web.xml contains the following:
>
> <filter-mapping>
> <filter-name>Servlet Mapped Filter</filter-name>
> <servlet-name>invoker</servlet-name>
> </filter-mapping>
>
>
> Concerning invoker:
> "The invoker is a dynamic servlet which allows run-time loading of
> other servlets based on class name. This servlet is the one that
> allows http://localhost/servlet/com.foo.MyClass?more=cowbell, where
> com.foo.MyClass is some class which can be loaded as a servlet but was
> never explicitly declared in a config file."
>
> After removing the offending xml from web.xml it still seems to work
> fine for both Jetty and Tomcat.
>
> So there are a few options here:
>
> 1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio
> and remove the invoker reference.
> If we do this we should also remove the following reference from the
> jsp-examples main page: "These examples will only work when these
> pages are being served by a servlet engine; of course, we recommend
> Tomcat"
>
> We can do this ourselves or ask Tomcat to do it..
>
> 2) Only make the example(s) available on Tomcat distributions.
>
> 3) Install on Jetty and live with the "WARNING: Some GBeans were not
> started successfully:" Or find a way to ignore and/or suppress the
> WARNING.
Suppressing the warnings is a really bad idea. Usually you want to
stop when you see one.
>
> 4) Figure out a way to leverage the invoker servlet in Jetty. It
> seems they do have one. Is the web.xml syntax different?
When I wrote the jetty deployer I studied the spec and could not find
any support for this kind of dynamic servlet that isn't listed in
web.xml, so I didn't try to put any in. If someone has a good argument
that it is consistent with the spec (I thought it was not), we could
try something. We might be able to use another default servlet like
the static content one. If we do this I think we need a way to turn it
on and off: this seems like it will lead us to having the deployer know
about all or many of the default servlets, something I am not entirely
thrilled with.
thanks
david jencks
>
> Thanks
> -Dave-
>
> David Jencks wrote:
>> There's already a jira to point out that the jetty builder doesn't
>> check referential integrity of web.xml. Could you check that the
>> web.xml is actually consistent?
>> thanks
>> david jencks
>> On Dec 5, 2005, at 10:42 AM, Aaron Mulder wrote:
>>> If there is no servlet name=invoker in the debug tool, then it seems
>>> like during WAR deployment we've constructed a GBean that depends on
>>> another GBean that doesn't exist, and I think you should definitely
>>> create a JIRA for that!
>>>
>>> Aaron
>>>
>>> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>
>>>> Aaron Mulder wrote:
>>>>
>>>>> The problem appears to be caused by:
>>>>>
>>>>> 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=
>>>>> Se rvlet
>>>>> Mapped
>>>>> Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/
>>>>> car,j2eeType=WebFilterMapping
>>>>>
>>>>> because no targets are running for reference Servlet matching the
>>>>> patterns:
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/
>>>>> servlets-examples-jetty/1.0-SNAPSHOT/
>>>>> car,j2eeType=Servlet,name=invoker
>>>>>
>>>>> Can you look in the debug tool after it's running and check for
>>>>> "name=invoker" to see whether the GBean reference name is just a
>>>>> little off or something?
>>>>>
>>>>
>>>> I only see the following in the debug-tool..
>>>>
>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=S
>>>> er vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>>> SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>>
>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-
>>>> examples-
>>>> jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>>
>>>>
>>>> ObjectName:
>>>> geronimo.server:
>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=S
>>>> er vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>>> SNAPSHOT/car,j2eeType=WebFilterMapping
>>>>
>>>> ClassName: org.apache.geronimo.jetty.JettyFilterMapping
>>>> State: starting
>>>>
>>>> Attributes
>>>> Name Value
>>>> errorDispatch false
>>>> forwardDispatch false
>>>> includeDispatch false
>>>> requestDispatch true
>>>> urlPattern (null)
>>>>
>>>> This can be easily recreated on Jetty by applying GERONIMO-1258
>>>> (since
>>>> it predeploys the apps).. Or alternately by installing the war
>>>> directly
>>>> from the ibiblio repo (link provided in earlier post)..
>>>>
>>>> The same application runs fine on Tomcat. Do you suspect an error
>>>> in
>>>> the Geronimo code or in the application itself? Do I need to open
>>>> a JIRA?
>>>>
>>>>
>>>>
>>>>> In any case, this is a real error, as I think it means some of the
>>>>> servlet filters for the application were not started. I wonder
>>>>> why we
>>>>> didn't barf during deployment? And I guess I also whonder why we
>>>>> don't refuse to start the application as a whole when part of it
>>>>> won't
>>>>> start, but that's a larger question. :)
>>>>>
>>>>> Aaron
>>>>>
>>>>> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>>
>>>>>> BTW, the war file (and the web.xml) are available at:
>>>>>>
>>>>>> http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-
>>>>>> examples-tomcat-5.5.12.war
>>>>>>
>>>>>> Sorry that the original email spewed out the attachment in the
>>>>>> text window..
>>>>>>
>>>>>> Dave Colasurdo wrote:
>>>>>>
>>>>>>> GERONIMO-1258 will introduce the tomcat examples into Geronimo.
>>>>>>> The
>>>>>>> examples seem to install and run fine on both Tomcat and Jetty.
>>>>>>> There
>>>>>>> is a warning message (see below) that is spit out during Jetty
>>>>>>> startup.
>>>>>>> There is no such message for Tomcat. Can someone please help
>>>>>>> shed some
>>>>>>> light on why the warning is being emitted. I've attached the
>>>>>>> relevant
>>>>>>> portions of my geronimo.log.
>>>>>>>
>>>>>>> Thanks
>>>>>>> -Dave-
>>>>>>>
>>>>>>>
>>>>>>> Starting Geronimo Application Server
>>>>>>> [******************] 100% 27s Startup complete
>>>>>>> Listening on Ports:
>>>>>>> 1099 0.0.0.0 RMI Naming
>>>>>>> 1527 0.0.0.0 Derby Connector
>>>>>>> 4201 127.0.0.1 ActiveIO Connector EJB
>>>>>>> 4242 0.0.0.0 Remote Login Listener
>>>>>>> 8080 0.0.0.0 Jetty Connector HTTP
>>>>>>> 8443 0.0.0.0 Jetty Connector HTTPS
>>>>>>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>>>>>>>
>>>>>>> Started Application Modules:
>>>>>>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
>>>>>>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
>>>>>>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
>>>>>>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>>>>>>>
>>>>>>> Web Applications:
>>>>>>> http://linux-009037214145:8080/
>>>>>>> http://linux-009037214145:8080/console
>>>>>>> http://linux-009037214145:8080/console-standard
>>>>>>> http://linux-009037214145:8080/jsp-examples
>>>>>>> http://linux-009037214145:8080/juddi
>>>>>>> http://linux-009037214145:8080/servlets-examples
>>>>>>>
>>>>>>> WARNING: Some GBeans were not started successfully:
>>>>>>>
>>>>>>> geronimo.server:
>>>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilte
>>>>>>> r=
>>>>>>> ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/
>>>>>>> 1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>>>>>
>>>>>>>
>>>>>>> geronimo.server:
>>>>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-
>>>>>>> examples-jetty/1.0-SNAPSHOT/
>>>>>>> car,j2eeType=WebFilterMapping(starting)
>>>>>>>
>>>>>>>
>>>>>>> Geronimo Application Server started
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Jan Bartel <ja...@mortbay.com>.
Dave,
Strange, I tried the war in standalone Jetty and there are no
deployment errors and it seems to work fine. I can only assume
that we're not catching some error, I will have a further look
at that.
Anyway, I assume the "invoker" servlet being referred to would
be the invoker servlet that is normally configured in jetty's
webdefault.xml file (and is by default commented out):
<servlet>
<servlet-name>invoker</servlet-name>
<servlet-class>org.mortbay.jetty.servlet.Invoker</servlet-class>
<init-param>
<param-name>verbose</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>nonContextServlets</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>dynamicParam</param-name>
<param-value>anyValue</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping> <servlet-name>invoker</servlet-name> <url-pattern>/servlet/*</url-pattern> </servlet-mapping>
To run the tomcat servlet examples Geronimo needs to do the same kind of GBean
exposure for the JettyWebModuleDeployer as is done for the DefaultServlet. I
think that should just be a matter of adding the following lines to the
j2ee-jetty-runtime-deployer-plan.xml :
<gbean name="InvokerServlet" class="org.apache.geronimo.jetty.JettyServletHolder">
<attribute name="servletName">invoker</attribute>
<attribute name="servletClass">org.mortbay.jetty.servlet.Invoker</attribute>
<attribute name="loadOnStartup">0</attribute>
<attribute name="initParams">
verbose=false
nonContextServlets=false
dynamicParam=anyValue
</attribute>
<attribute name="servletMappings">/servlet/*</attribute>
</gbean>
regards
Jan
Dave Colasurdo wrote:
> The web.xml contains the following:
>
> <filter-mapping>
> <filter-name>Servlet Mapped Filter</filter-name>
> <servlet-name>invoker</servlet-name>
> </filter-mapping>
>
>
> Concerning invoker:
> "The invoker is a dynamic servlet which allows run-time loading of other
> servlets based on class name. This servlet is the one that allows
> http://localhost/servlet/com.foo.MyClass?more=cowbell, where
> com.foo.MyClass is some class which can be loaded as a servlet but was
> never explicitly declared in a config file."
>
> After removing the offending xml from web.xml it still seems to work
> fine for both Jetty and Tomcat.
>
> So there are a few options here:
>
> 1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio and
> remove the invoker reference.
> If we do this we should also remove the following reference from the
> jsp-examples main page: "These examples will only work when these pages
> are being served by a servlet engine; of course, we recommend Tomcat"
>
> We can do this ourselves or ask Tomcat to do it..
>
> 2) Only make the example(s) available on Tomcat distributions.
>
> 3) Install on Jetty and live with the "WARNING: Some GBeans were not
> started successfully:" Or find a way to ignore and/or suppress the WARNING.
>
> 4) Figure out a way to leverage the invoker servlet in Jetty. It seems
> they do have one. Is the web.xml syntax different?
>
> Thanks
> -Dave-
>
> David Jencks wrote:
>
>> There's already a jira to point out that the jetty builder doesn't
>> check referential integrity of web.xml. Could you check that the
>> web.xml is actually consistent?
>>
>> thanks
>> david jencks
>>
>> On Dec 5, 2005, at 10:42 AM, Aaron Mulder wrote:
>>
>>> If there is no servlet name=invoker in the debug tool, then it seems
>>> like during WAR deployment we've constructed a GBean that depends on
>>> another GBean that doesn't exist, and I think you should definitely
>>> create a JIRA for that!
>>>
>>> Aaron
>>>
>>> On 12/5/05, Dave Colasurdo
>>> <da...@public.gmane.org> wrote:
>>>
>>>> Aaron Mulder wrote:
>>>>
>>>>> The problem appears to be caused by:
>>>>>
>>>>> 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Se
>>>>> rvlet
>>>>> Mapped
>>>>> Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/
>>>>> car,j2eeType=WebFilterMapping
>>>>>
>>>>> because no targets are running for reference Servlet matching the
>>>>> patterns:
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/
>>>>> servlets-examples-jetty/1.0-SNAPSHOT/
>>>>> car,j2eeType=Servlet,name=invoker
>>>>>
>>>>> Can you look in the debug tool after it's running and check for
>>>>> "name=invoker" to see whether the GBean reference name is just a
>>>>> little off or something?
>>>>>
>>>>
>>>> I only see the following in the debug-tool..
>>>>
>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>>>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>>> SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>>
>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-
>>>> jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>>
>>>>
>>>> ObjectName:
>>>> geronimo.server:
>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>>>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>>> SNAPSHOT/car,j2eeType=WebFilterMapping
>>>>
>>>> ClassName: org.apache.geronimo.jetty.JettyFilterMapping
>>>> State: starting
>>>>
>>>> Attributes
>>>> Name Value
>>>> errorDispatch false
>>>> forwardDispatch false
>>>> includeDispatch false
>>>> requestDispatch true
>>>> urlPattern (null)
>>>>
>>>> This can be easily recreated on Jetty by applying GERONIMO-1258 (since
>>>> it predeploys the apps).. Or alternately by installing the war
>>>> directly
>>>> from the ibiblio repo (link provided in earlier post)..
>>>>
>>>> The same application runs fine on Tomcat. Do you suspect an error in
>>>> the Geronimo code or in the application itself? Do I need to open
>>>> a JIRA?
>>>>
>>>>
>>>>
>>>>> In any case, this is a real error, as I think it means some of the
>>>>> servlet filters for the application were not started. I wonder
>>>>> why we
>>>>> didn't barf during deployment? And I guess I also whonder why we
>>>>> don't refuse to start the application as a whole when part of it
>>>>> won't
>>>>> start, but that's a larger question. :)
>>>>>
>>>>> Aaron
>>>>>
>>>>> On 12/5/05, Dave Colasurdo
>>>>> <da...@public.gmane.org> wrote:
>>>>>
>>>>>> BTW, the war file (and the web.xml) are available at:
>>>>>>
>>>>>> http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-
>>>>>> examples-tomcat-5.5.12.war
>>>>>>
>>>>>> Sorry that the original email spewed out the attachment in the
>>>>>> text window..
>>>>>>
>>>>>> Dave Colasurdo wrote:
>>>>>>
>>>>>>> GERONIMO-1258 will introduce the tomcat examples into Geronimo.
>>>>>>> The
>>>>>>> examples seem to install and run fine on both Tomcat and Jetty.
>>>>>>> There
>>>>>>> is a warning message (see below) that is spit out during Jetty
>>>>>>> startup.
>>>>>>> There is no such message for Tomcat. Can someone please help
>>>>>>> shed some
>>>>>>> light on why the warning is being emitted. I've attached the
>>>>>>> relevant
>>>>>>> portions of my geronimo.log.
>>>>>>>
>>>>>>> Thanks
>>>>>>> -Dave-
>>>>>>>
>>>>>>>
>>>>>>> Starting Geronimo Application Server
>>>>>>> [******************] 100% 27s Startup complete
>>>>>>> Listening on Ports:
>>>>>>> 1099 0.0.0.0 RMI Naming
>>>>>>> 1527 0.0.0.0 Derby Connector
>>>>>>> 4201 127.0.0.1 ActiveIO Connector EJB
>>>>>>> 4242 0.0.0.0 Remote Login Listener
>>>>>>> 8080 0.0.0.0 Jetty Connector HTTP
>>>>>>> 8443 0.0.0.0 Jetty Connector HTTPS
>>>>>>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>>>>>>>
>>>>>>> Started Application Modules:
>>>>>>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
>>>>>>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
>>>>>>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
>>>>>>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
>>>>>>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>>>>>>>
>>>>>>> Web Applications:
>>>>>>> http://linux-009037214145:8080/
>>>>>>> http://linux-009037214145:8080/console
>>>>>>> http://linux-009037214145:8080/console-standard
>>>>>>> http://linux-009037214145:8080/jsp-examples
>>>>>>> http://linux-009037214145:8080/juddi
>>>>>>> http://linux-009037214145:8080/servlets-examples
>>>>>>>
>>>>>>> WARNING: Some GBeans were not started successfully:
>>>>>>>
>>>>>>> geronimo.server:
>>>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=
>>>>>>> ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/
>>>>>>> 1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>>>>>
>>>>>>>
>>>>>>> geronimo.server:
>>>>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-
>>>>>>> examples-jetty/1.0-SNAPSHOT/ car,j2eeType=WebFilterMapping(starting)
>>>>>>>
>>>>>>>
>>>>>>> Geronimo Application Server started
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by anita kulshreshtha <a_...@yahoo.com>.
--- Dave Colasurdo <da...@earthlink.net> wrote:
> The web.xml contains the following:
>
> <filter-mapping>
> <filter-name>Servlet Mapped
> Filter</filter-name>
> <servlet-name>invoker</servlet-name>
> </filter-mapping>
>
>
> Concerning invoker:
> "The invoker is a dynamic servlet which allows
> run-time loading of other
> servlets based on class name. This servlet is the
> one that allows
>
http://localhost/servlet/com.foo.MyClass?more=cowbell,
> where
> com.foo.MyClass is some class which can be loaded as
> a servlet but was
> never explicitly declared in a config file."
I do not know the behavior of Invoker Servlet in
Jetty, but in tomcat -
"The purpose of the Invoker Servlet is to allow a
web application to dynamically register new servlet
definitions that correspond with a <servlet> element
in the /WEB-INF/web.xml deployment descriptor, and
execute requests utilizing the new servlet
definitions."
More info can be found at
http://tomcat.apache.org/tomcat-5.5-doc/catalina/funcspecs/fs-invoker.html
Thanks
Anita
>
> After removing the offending xml from web.xml it
> still seems to work
> fine for both Jetty and Tomcat.
>
> So there are a few options here:
>
> 1) Crack open
> geronimo-servlet-examples-tomcat-5.5.12.war in
> ibiblio
> and remove the invoker reference.
> If we do this we should also remove the following
> reference from the
> jsp-examples main page: "These examples will only
> work when these pages
> are being served by a servlet engine; of course, we
> recommend Tomcat"
>
> We can do this ourselves or ask Tomcat to do it..
>
> 2) Only make the example(s) available on Tomcat
> distributions.
>
> 3) Install on Jetty and live with the "WARNING: Some
> GBeans were not
> started successfully:" Or find a way to ignore
> and/or suppress the
> WARNING.
>
> 4) Figure out a way to leverage the invoker servlet
> in Jetty. It seems
> they do have one. Is the web.xml syntax different?
>
> Thanks
> -Dave-
>
> David Jencks wrote:
> > There's already a jira to point out that the jetty
> builder doesn't
> > check referential integrity of web.xml. Could you
> check that the
> > web.xml is actually consistent?
> >
> > thanks
> > david jencks
> >
> > On Dec 5, 2005, at 10:42 AM, Aaron Mulder wrote:
> >
> >> If there is no servlet name=invoker in the debug
> tool, then it seems
> >> like during WAR deployment we've constructed a
> GBean that depends on
> >> another GBean that doesn't exist, and I think you
> should definitely
> >> create a JIRA for that!
> >>
> >> Aaron
> >>
> >> On 12/5/05, Dave Colasurdo
> <da...@earthlink.net> wrote:
> >>
> >>> Aaron Mulder wrote:
> >>>
> >>>> The problem appears to be caused by:
> >>>>
> >>>> 09:24:21,347 DEBUG [GBeanSingleReference]
> Waiting to start
> >>>> geronimo.server:
> >>>>
>
J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Se
>
> >>>> rvlet
> >>>> Mapped
> >>>>
>
Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/
>
> >>>> car,j2eeType=WebFilterMapping
> >>>>
> >>>> because no targets are running for reference
> Servlet matching the
> >>>> patterns:
> >>>> geronimo.server:
> >>>>
>
J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/
>
> >>>> servlets-examples-jetty/1.0-SNAPSHOT/
> car,j2eeType=Servlet,name=invoker
> >>>>
> >>>> Can you look in the debug tool after it's
> running and check for
> >>>> "name=invoker" to see whether the GBean
> reference name is just a
> >>>> little off or something?
> >>>>
> >>>
> >>> I only see the following in the debug-tool..
> >>>
> >>>
>
J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>
> >>>
>
vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>
> >>> SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
> >>>
> >>>
>
J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>
> >>>
>
\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-
>
> >>>
>
jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
> >>>
> >>>
> >>> ObjectName:
> >>> geronimo.server:
> >>>
>
J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>
> >>>
>
vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>
> >>> SNAPSHOT/car,j2eeType=WebFilterMapping
> >>>
> >>> ClassName:
> org.apache.geronimo.jetty.JettyFilterMapping
> >>> State: starting
> >>>
> >>> Attributes
> >>> Name Value
> >>> errorDispatch false
> >>> forwardDispatch false
> >>> includeDispatch false
> >>> requestDispatch true
> >>> urlPattern (null)
> >>>
> >>> This can be easily recreated on Jetty by
> applying GERONIMO-1258 (since
> >>> it predeploys the apps).. Or alternately by
> installing the war directly
> >>> from the ibiblio repo (link provided in earlier
> post)..
> >>>
> >>> The same application runs fine on Tomcat. Do
> you suspect an error in
> >>> the Geronimo code or in the application itself?
> Do I need to open a
> >>> JIRA?
> >>>
> >>>
> >>>
> >>>> In any case, this is a real error, as I think
> it means some of the
> >>>> servlet filters for the application were not
> started. I wonder why we
> >>>> didn't barf during deployment? And I guess I
> also whonder why we
> >>>> don't refuse to start the application as a
> whole when part of it won't
> >>>> start, but that's a larger question. :)
> >>>>
> >>>> Aaron
> >>>>
> >>>> On 12/5/05, Dave Colasurdo
> <da...@earthlink.net> wrote:
> >>>>
> >>>>> BTW, the war file (and the web.xml) are
> available at:
> >>>>>
> >>>>>
>
http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-
>
> >>>>> examples-tomcat-5.5.12.war
> >>>>>
> >>>>> Sorry that the original email spewed out the
> attachment in the
> >>>>> text window..
> >>>>>
> >>>>> Dave Colasurdo wrote:
> >>>>>
> >>>>>> GERONIMO-1258 will introduce the tomcat
> examples
=== message truncated ===
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
The web.xml contains the following:
<filter-mapping>
<filter-name>Servlet Mapped Filter</filter-name>
<servlet-name>invoker</servlet-name>
</filter-mapping>
Concerning invoker:
"The invoker is a dynamic servlet which allows run-time loading of other
servlets based on class name. This servlet is the one that allows
http://localhost/servlet/com.foo.MyClass?more=cowbell, where
com.foo.MyClass is some class which can be loaded as a servlet but was
never explicitly declared in a config file."
After removing the offending xml from web.xml it still seems to work
fine for both Jetty and Tomcat.
So there are a few options here:
1) Crack open geronimo-servlet-examples-tomcat-5.5.12.war in ibiblio
and remove the invoker reference.
If we do this we should also remove the following reference from the
jsp-examples main page: "These examples will only work when these pages
are being served by a servlet engine; of course, we recommend Tomcat"
We can do this ourselves or ask Tomcat to do it..
2) Only make the example(s) available on Tomcat distributions.
3) Install on Jetty and live with the "WARNING: Some GBeans were not
started successfully:" Or find a way to ignore and/or suppress the
WARNING.
4) Figure out a way to leverage the invoker servlet in Jetty. It seems
they do have one. Is the web.xml syntax different?
Thanks
-Dave-
David Jencks wrote:
> There's already a jira to point out that the jetty builder doesn't
> check referential integrity of web.xml. Could you check that the
> web.xml is actually consistent?
>
> thanks
> david jencks
>
> On Dec 5, 2005, at 10:42 AM, Aaron Mulder wrote:
>
>> If there is no servlet name=invoker in the debug tool, then it seems
>> like during WAR deployment we've constructed a GBean that depends on
>> another GBean that doesn't exist, and I think you should definitely
>> create a JIRA for that!
>>
>> Aaron
>>
>> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>
>>> Aaron Mulder wrote:
>>>
>>>> The problem appears to be caused by:
>>>>
>>>> 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
>>>> geronimo.server:
>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Se
>>>> rvlet
>>>> Mapped
>>>> Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/
>>>> car,j2eeType=WebFilterMapping
>>>>
>>>> because no targets are running for reference Servlet matching the
>>>> patterns:
>>>> geronimo.server:
>>>> J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/
>>>> servlets-examples-jetty/1.0-SNAPSHOT/ car,j2eeType=Servlet,name=invoker
>>>>
>>>> Can you look in the debug tool after it's running and check for
>>>> "name=invoker" to see whether the GBean reference name is just a
>>>> little off or something?
>>>>
>>>
>>> I only see the following in the debug-tool..
>>>
>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>> SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>
>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-
>>> jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>>
>>>
>>> ObjectName:
>>> geronimo.server:
>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>>> SNAPSHOT/car,j2eeType=WebFilterMapping
>>>
>>> ClassName: org.apache.geronimo.jetty.JettyFilterMapping
>>> State: starting
>>>
>>> Attributes
>>> Name Value
>>> errorDispatch false
>>> forwardDispatch false
>>> includeDispatch false
>>> requestDispatch true
>>> urlPattern (null)
>>>
>>> This can be easily recreated on Jetty by applying GERONIMO-1258 (since
>>> it predeploys the apps).. Or alternately by installing the war directly
>>> from the ibiblio repo (link provided in earlier post)..
>>>
>>> The same application runs fine on Tomcat. Do you suspect an error in
>>> the Geronimo code or in the application itself? Do I need to open a
>>> JIRA?
>>>
>>>
>>>
>>>> In any case, this is a real error, as I think it means some of the
>>>> servlet filters for the application were not started. I wonder why we
>>>> didn't barf during deployment? And I guess I also whonder why we
>>>> don't refuse to start the application as a whole when part of it won't
>>>> start, but that's a larger question. :)
>>>>
>>>> Aaron
>>>>
>>>> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>
>>>>> BTW, the war file (and the web.xml) are available at:
>>>>>
>>>>> http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-
>>>>> examples-tomcat-5.5.12.war
>>>>>
>>>>> Sorry that the original email spewed out the attachment in the
>>>>> text window..
>>>>>
>>>>> Dave Colasurdo wrote:
>>>>>
>>>>>> GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
>>>>>> examples seem to install and run fine on both Tomcat and Jetty.
>>>>>> There
>>>>>> is a warning message (see below) that is spit out during Jetty
>>>>>> startup.
>>>>>> There is no such message for Tomcat. Can someone please help
>>>>>> shed some
>>>>>> light on why the warning is being emitted. I've attached the
>>>>>> relevant
>>>>>> portions of my geronimo.log.
>>>>>>
>>>>>> Thanks
>>>>>> -Dave-
>>>>>>
>>>>>>
>>>>>> Starting Geronimo Application Server
>>>>>> [******************] 100% 27s Startup complete
>>>>>> Listening on Ports:
>>>>>> 1099 0.0.0.0 RMI Naming
>>>>>> 1527 0.0.0.0 Derby Connector
>>>>>> 4201 127.0.0.1 ActiveIO Connector EJB
>>>>>> 4242 0.0.0.0 Remote Login Listener
>>>>>> 8080 0.0.0.0 Jetty Connector HTTP
>>>>>> 8443 0.0.0.0 Jetty Connector HTTPS
>>>>>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>>>>>>
>>>>>> Started Application Modules:
>>>>>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
>>>>>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
>>>>>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
>>>>>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
>>>>>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
>>>>>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
>>>>>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>>>>>>
>>>>>> Web Applications:
>>>>>> http://linux-009037214145:8080/
>>>>>> http://linux-009037214145:8080/console
>>>>>> http://linux-009037214145:8080/console-standard
>>>>>> http://linux-009037214145:8080/jsp-examples
>>>>>> http://linux-009037214145:8080/juddi
>>>>>> http://linux-009037214145:8080/servlets-examples
>>>>>>
>>>>>> WARNING: Some GBeans were not started successfully:
>>>>>>
>>>>>> geronimo.server:
>>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=
>>>>>> ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/
>>>>>> 1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>>>>
>>>>>>
>>>>>> geronimo.server:
>>>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-
>>>>>> examples-jetty/1.0-SNAPSHOT/ car,j2eeType=WebFilterMapping(starting)
>>>>>>
>>>>>>
>>>>>> Geronimo Application Server started
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by David Jencks <da...@yahoo.com>.
There's already a jira to point out that the jetty builder doesn't
check referential integrity of web.xml. Could you check that the
web.xml is actually consistent?
thanks
david jencks
On Dec 5, 2005, at 10:42 AM, Aaron Mulder wrote:
> If there is no servlet name=invoker in the debug tool, then it seems
> like during WAR deployment we've constructed a GBean that depends on
> another GBean that doesn't exist, and I think you should definitely
> create a JIRA for that!
>
> Aaron
>
> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>> Aaron Mulder wrote:
>>> The problem appears to be caused by:
>>>
>>> 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
>>> geronimo.server:
>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Se
>>> rvlet
>>> Mapped
>>> Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/
>>> car,j2eeType=WebFilterMapping
>>>
>>> because no targets are running for reference Servlet matching the
>>> patterns:
>>> geronimo.server:
>>> J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/
>>> servlets-examples-jetty/1.0-SNAPSHOT/
>>> car,j2eeType=Servlet,name=invoker
>>>
>>> Can you look in the debug tool after it's running and check for
>>> "name=invoker" to see whether the GBean reference name is just a
>>> little off or something?
>>>
>>
>> I only see the following in the debug-tool..
>>
>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>> SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>
>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-
>> jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>>
>>
>> ObjectName:
>> geronimo.server:
>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Ser
>> vletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-
>> SNAPSHOT/car,j2eeType=WebFilterMapping
>>
>> ClassName: org.apache.geronimo.jetty.JettyFilterMapping
>> State: starting
>>
>> Attributes
>> Name Value
>> errorDispatch false
>> forwardDispatch false
>> includeDispatch false
>> requestDispatch true
>> urlPattern (null)
>>
>> This can be easily recreated on Jetty by applying GERONIMO-1258 (since
>> it predeploys the apps).. Or alternately by installing the war
>> directly
>> from the ibiblio repo (link provided in earlier post)..
>>
>> The same application runs fine on Tomcat. Do you suspect an error in
>> the Geronimo code or in the application itself? Do I need to open a
>> JIRA?
>>
>>
>>
>>> In any case, this is a real error, as I think it means some of the
>>> servlet filters for the application were not started. I wonder why
>>> we
>>> didn't barf during deployment? And I guess I also whonder why we
>>> don't refuse to start the application as a whole when part of it
>>> won't
>>> start, but that's a larger question. :)
>>>
>>> Aaron
>>>
>>> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>
>>>> BTW, the war file (and the web.xml) are available at:
>>>>
>>>> http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-
>>>> examples-tomcat-5.5.12.war
>>>>
>>>> Sorry that the original email spewed out the attachment in the text
>>>> window..
>>>>
>>>> Dave Colasurdo wrote:
>>>>
>>>>> GERONIMO-1258 will introduce the tomcat examples into Geronimo.
>>>>> The
>>>>> examples seem to install and run fine on both Tomcat and Jetty.
>>>>> There
>>>>> is a warning message (see below) that is spit out during Jetty
>>>>> startup.
>>>>> There is no such message for Tomcat. Can someone please help shed
>>>>> some
>>>>> light on why the warning is being emitted. I've attached the
>>>>> relevant
>>>>> portions of my geronimo.log.
>>>>>
>>>>> Thanks
>>>>> -Dave-
>>>>>
>>>>>
>>>>> Starting Geronimo Application Server
>>>>> [******************] 100% 27s Startup complete
>>>>> Listening on Ports:
>>>>> 1099 0.0.0.0 RMI Naming
>>>>> 1527 0.0.0.0 Derby Connector
>>>>> 4201 127.0.0.1 ActiveIO Connector EJB
>>>>> 4242 0.0.0.0 Remote Login Listener
>>>>> 8080 0.0.0.0 Jetty Connector HTTP
>>>>> 8443 0.0.0.0 Jetty Connector HTTPS
>>>>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>>>>>
>>>>> Started Application Modules:
>>>>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
>>>>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
>>>>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
>>>>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
>>>>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
>>>>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
>>>>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>>>>>
>>>>> Web Applications:
>>>>> http://linux-009037214145:8080/
>>>>> http://linux-009037214145:8080/console
>>>>> http://linux-009037214145:8080/console-standard
>>>>> http://linux-009037214145:8080/jsp-examples
>>>>> http://linux-009037214145:8080/juddi
>>>>> http://linux-009037214145:8080/servlets-examples
>>>>>
>>>>> WARNING: Some GBeans were not started successfully:
>>>>>
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=
>>>>> ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/
>>>>> 1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>>>
>>>>>
>>>>> geronimo.server:
>>>>> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/
>>>>> \*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-
>>>>> examples-jetty/1.0-SNAPSHOT/
>>>>> car,j2eeType=WebFilterMapping(starting)
>>>>>
>>>>>
>>>>> Geronimo Application Server started
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
If there is no servlet name=invoker in the debug tool, then it seems
like during WAR deployment we've constructed a GBean that depends on
another GBean that doesn't exist, and I think you should definitely
create a JIRA for that!
Aaron
On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
> Aaron Mulder wrote:
> > The problem appears to be caused by:
> >
> > 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
> > geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet
> > Mapped Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping
> >
> > because no targets are running for reference Servlet matching the patterns:
> > geronimo.server:J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=Servlet,name=invoker
> >
> > Can you look in the debug tool after it's running and check for
> > "name=invoker" to see whether the GBean reference name is just a
> > little off or something?
> >
>
> I only see the following in the debug-tool..
>
> J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>
> J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
>
>
> ObjectName:
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping
>
> ClassName: org.apache.geronimo.jetty.JettyFilterMapping
> State: starting
>
> Attributes
> Name Value
> errorDispatch false
> forwardDispatch false
> includeDispatch false
> requestDispatch true
> urlPattern (null)
>
> This can be easily recreated on Jetty by applying GERONIMO-1258 (since
> it predeploys the apps).. Or alternately by installing the war directly
> from the ibiblio repo (link provided in earlier post)..
>
> The same application runs fine on Tomcat. Do you suspect an error in
> the Geronimo code or in the application itself? Do I need to open a JIRA?
>
>
>
> > In any case, this is a real error, as I think it means some of the
> > servlet filters for the application were not started. I wonder why we
> > didn't barf during deployment? And I guess I also whonder why we
> > don't refuse to start the application as a whole when part of it won't
> > start, but that's a larger question. :)
> >
> > Aaron
> >
> > On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
> >
> >>BTW, the war file (and the web.xml) are available at:
> >>
> >>http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-examples-tomcat-5.5.12.war
> >>
> >>Sorry that the original email spewed out the attachment in the text window..
> >>
> >>Dave Colasurdo wrote:
> >>
> >>>GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
> >>>examples seem to install and run fine on both Tomcat and Jetty. There
> >>>is a warning message (see below) that is spit out during Jetty startup.
> >>> There is no such message for Tomcat. Can someone please help shed some
> >>>light on why the warning is being emitted. I've attached the relevant
> >>>portions of my geronimo.log.
> >>>
> >>>Thanks
> >>>-Dave-
> >>>
> >>>
> >>>Starting Geronimo Application Server
> >>>[******************] 100% 27s Startup complete
> >>> Listening on Ports:
> >>> 1099 0.0.0.0 RMI Naming
> >>> 1527 0.0.0.0 Derby Connector
> >>> 4201 127.0.0.1 ActiveIO Connector EJB
> >>> 4242 0.0.0.0 Remote Login Listener
> >>> 8080 0.0.0.0 Jetty Connector HTTP
> >>> 8443 0.0.0.0 Jetty Connector HTTPS
> >>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
> >>>
> >>> Started Application Modules:
> >>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
> >>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
> >>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
> >>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
> >>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
> >>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
> >>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
> >>>
> >>> Web Applications:
> >>> http://linux-009037214145:8080/
> >>> http://linux-009037214145:8080/console
> >>> http://linux-009037214145:8080/console-standard
> >>> http://linux-009037214145:8080/jsp-examples
> >>> http://linux-009037214145:8080/juddi
> >>> http://linux-009037214145:8080/servlets-examples
> >>>
> >>> WARNING: Some GBeans were not started successfully:
> >>>
> >>>geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
> >>>
> >>>
> >>>geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
> >>>
> >>>
> >>>Geronimo Application Server started
> >>>
> >>>
> >>>
> >>
> >
> >
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
Aaron Mulder wrote:
> The problem appears to be caused by:
>
> 09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet
> Mapped Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping
>
> because no targets are running for reference Servlet matching the patterns:
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=Servlet,name=invoker
>
> Can you look in the debug tool after it's running and check for
> "name=invoker" to see whether the GBean reference name is just a
> little off or something?
>
I only see the following in the debug-tool..
J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping[starting]
ObjectName:
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping
ClassName: org.apache.geronimo.jetty.JettyFilterMapping
State: starting
Attributes
Name Value
errorDispatch false
forwardDispatch false
includeDispatch false
requestDispatch true
urlPattern (null)
This can be easily recreated on Jetty by applying GERONIMO-1258 (since
it predeploys the apps).. Or alternately by installing the war directly
from the ibiblio repo (link provided in earlier post)..
The same application runs fine on Tomcat. Do you suspect an error in
the Geronimo code or in the application itself? Do I need to open a JIRA?
> In any case, this is a real error, as I think it means some of the
> servlet filters for the application were not started. I wonder why we
> didn't barf during deployment? And I guess I also whonder why we
> don't refuse to start the application as a whole when part of it won't
> start, but that's a larger question. :)
>
> Aaron
>
> On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
>
>>BTW, the war file (and the web.xml) are available at:
>>
>>http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-examples-tomcat-5.5.12.war
>>
>>Sorry that the original email spewed out the attachment in the text window..
>>
>>Dave Colasurdo wrote:
>>
>>>GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
>>>examples seem to install and run fine on both Tomcat and Jetty. There
>>>is a warning message (see below) that is spit out during Jetty startup.
>>> There is no such message for Tomcat. Can someone please help shed some
>>>light on why the warning is being emitted. I've attached the relevant
>>>portions of my geronimo.log.
>>>
>>>Thanks
>>>-Dave-
>>>
>>>
>>>Starting Geronimo Application Server
>>>[******************] 100% 27s Startup complete
>>> Listening on Ports:
>>> 1099 0.0.0.0 RMI Naming
>>> 1527 0.0.0.0 Derby Connector
>>> 4201 127.0.0.1 ActiveIO Connector EJB
>>> 4242 0.0.0.0 Remote Login Listener
>>> 8080 0.0.0.0 Jetty Connector HTTP
>>> 8443 0.0.0.0 Jetty Connector HTTPS
>>> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>>>
>>> Started Application Modules:
>>> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
>>> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
>>> RAR: geronimo/system-database/1.0-SNAPSHOT/car
>>> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
>>> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
>>> RAR: geronimo/activemq/1.0-SNAPSHOT/car
>>> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>>>
>>> Web Applications:
>>> http://linux-009037214145:8080/
>>> http://linux-009037214145:8080/console
>>> http://linux-009037214145:8080/console-standard
>>> http://linux-009037214145:8080/jsp-examples
>>> http://linux-009037214145:8080/juddi
>>> http://linux-009037214145:8080/servlets-examples
>>>
>>> WARNING: Some GBeans were not started successfully:
>>>
>>>geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>
>>>
>>>geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>>>
>>>
>>>Geronimo Application Server started
>>>
>>>
>>>
>>
>
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
The problem appears to be caused by:
09:24:21,347 DEBUG [GBeanSingleReference] Waiting to start
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet
Mapped Filter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping
because no targets are running for reference Servlet matching the patterns:
geronimo.server:J2EEApplication=null,J2EEServer=geronimo,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=Servlet,name=invoker
Can you look in the debug tool after it's running and check for
"name=invoker" to see whether the GBean reference name is just a
little off or something?
In any case, this is a real error, as I think it means some of the
servlet filters for the application were not started. I wonder why we
didn't barf during deployment? And I guess I also whonder why we
don't refuse to start the application as a whole when part of it won't
start, but that's a larger question. :)
Aaron
On 12/5/05, Dave Colasurdo <da...@earthlink.net> wrote:
> BTW, the war file (and the web.xml) are available at:
>
> http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-examples-tomcat-5.5.12.war
>
> Sorry that the original email spewed out the attachment in the text window..
>
> Dave Colasurdo wrote:
> > GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
> > examples seem to install and run fine on both Tomcat and Jetty. There
> > is a warning message (see below) that is spit out during Jetty startup.
> > There is no such message for Tomcat. Can someone please help shed some
> > light on why the warning is being emitted. I've attached the relevant
> > portions of my geronimo.log.
> >
> > Thanks
> > -Dave-
> >
> >
> > Starting Geronimo Application Server
> > [******************] 100% 27s Startup complete
> > Listening on Ports:
> > 1099 0.0.0.0 RMI Naming
> > 1527 0.0.0.0 Derby Connector
> > 4201 127.0.0.1 ActiveIO Connector EJB
> > 4242 0.0.0.0 Remote Login Listener
> > 8080 0.0.0.0 Jetty Connector HTTP
> > 8443 0.0.0.0 Jetty Connector HTTPS
> > 61616 0.0.0.0 ActiveMQ Message Broker Connector
> >
> > Started Application Modules:
> > WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
> > WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
> > RAR: geronimo/system-database/1.0-SNAPSHOT/car
> > EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
> > WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
> > RAR: geronimo/activemq/1.0-SNAPSHOT/car
> > WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
> >
> > Web Applications:
> > http://linux-009037214145:8080/
> > http://linux-009037214145:8080/console
> > http://linux-009037214145:8080/console-standard
> > http://linux-009037214145:8080/jsp-examples
> > http://linux-009037214145:8080/juddi
> > http://linux-009037214145:8080/servlets-examples
> >
> > WARNING: Some GBeans were not started successfully:
> >
> > geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
> >
> >
> > geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
> >
> >
> > Geronimo Application Server started
> >
> >
> >
>
Re: Startup Warning related to running Tomcat Examples on Jetty
Posted by Dave Colasurdo <da...@earthlink.net>.
BTW, the war file (and the web.xml) are available at:
http://www.ibiblio.org/maven/geronimo/wars/geronimo-servlet-examples-tomcat-5.5.12.war
Sorry that the original email spewed out the attachment in the text window..
Dave Colasurdo wrote:
> GERONIMO-1258 will introduce the tomcat examples into Geronimo. The
> examples seem to install and run fine on both Tomcat and Jetty. There
> is a warning message (see below) that is spit out during Jetty startup.
> There is no such message for Tomcat. Can someone please help shed some
> light on why the warning is being emitted. I've attached the relevant
> portions of my geronimo.log.
>
> Thanks
> -Dave-
>
>
> Starting Geronimo Application Server
> [******************] 100% 27s Startup complete
> Listening on Ports:
> 1099 0.0.0.0 RMI Naming
> 1527 0.0.0.0 Derby Connector
> 4201 127.0.0.1 ActiveIO Connector EJB
> 4242 0.0.0.0 Remote Login Listener
> 8080 0.0.0.0 Jetty Connector HTTP
> 8443 0.0.0.0 Jetty Connector HTTPS
> 61616 0.0.0.0 ActiveMQ Message Broker Connector
>
> Started Application Modules:
> WAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car
> WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car
> RAR: geronimo/system-database/1.0-SNAPSHOT/car
> EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car
> WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car
> RAR: geronimo/activemq/1.0-SNAPSHOT/car
> WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car
>
> Web Applications:
> http://linux-009037214145:8080/
> http://linux-009037214145:8080/console
> http://linux-009037214145:8080/console-standard
> http://linux-009037214145:8080/jsp-examples
> http://linux-009037214145:8080/juddi
> http://linux-009037214145:8080/servlets-examples
>
> WARNING: Some GBeans were not started successfully:
>
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=ServletMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>
>
> geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern="/servlet/\*",WebFilter=PathMappedFilter,WebModule=geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car,j2eeType=WebFilterMapping(starting)
>
>
> Geronimo Application Server started
>
>
>