geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AlskiOnTheWeb <>
Subject Re: Connector / Application Construction Order...
Date Fri, 08 Feb 2008 15:46:11 GMT

...Thanks for the advice. I've gone to the other tactic...submit the bug
against Axis. Hopefully they can fix their end of the problem (or I'll dig
into it at some point). This is probably a better way rather than trying to
arm wrestle the container into avoiding the problem. I can see where trying
to generically manage the lifecycles on the components and applications can
be a problem.


Alski :-)

djencks wrote:
> well, IIUC you aren't trying to run apps on different ports so the  
> solution is much simpler.
> The important part here is to turn off the original web connector we  
> supply and add another one that will start after your application.
> I don't remember if geronimo 1.0 supports gbean depenedencies (that  
> aren't references) -- I think it doesn't.  This means that, like in  
> the example, you have to include your new connector in a separate  
> app.  It's actually easier to include it in an additional geronimo  
> service module  than a web app, just make sure it depends on your web  
> app.
> Don't include the web-container element in your web app plan, you  
> will be using the original web-container and I don't think g. 1.0  
> supports the element anyway.
> hope this helps
> david jencks
> On Feb 7, 2008, at 12:26 PM, AlskiOnTheWeb wrote:
>> ...Thanks, I saw that one before but since we're using Geronimo 1.0  
>> with
>> Jetty, I'm hung out to dry there unless someone took up the authors  
>> advice
>> and went and tried some equivalent thing in Jetty.
>> Any other ideas on it?
>> Thanks.
>> Alski :-)
>> djencks wrote:
>>> I'm not sure if the technique will work on geronimo 1.0 but there's
>>> an example of setting up a connector that starts after a particular
>>> application  is running described at
>>> distinct-ports.html
>>> The descriptors are definitely wrong for 1.0.
>>> You only need to turn off the existing connector gbean and include a
>>> replacement that you deploy yourself.  This example is considerably
>>> more complicated than you need.
>>> We've thought about how to wait to start the connectors until all the
>>> web apps are started but no one AFAIK has figured out how to
>>> determine what "all the web apps" might mean.
>>> thanks
>>> david jencks
>>> On Feb 7, 2008, at 11:49 AM, AlskiOnTheWeb wrote:
>>>> Hi All,
>>>> Sorry if this is posted here somewhere but I couldn't find anything
>>>> on it by
>>>> searching. Anyway, I have an application with an Axis 2 web service
>>>> that is
>>>> deployed in a Geronimo 1.0 (yes, I know, but I'm stuck with it)
>>>> application
>>>> server. The issue I see is that the connector (listening on TCP  
>>>> 8080)
>>>> becomes available as the application itself is being brought up.
>>>> Unfortunately, there is some problem with Axis being hit before
>>>> it's ready
>>>> and I can easily get it into a state where it doesn't expose my web
>>>> service
>>>> endpoint. Obviously, this is a bad thing. I am guessing that this  
>>>> is a
>>>> result of web service clients pounding geronimo while it's on it's
>>>> way up
>>>> but not quite ready. Is there a way to have geronimo bring up the
>>>> applications first and then expose the TCP connectors once the
>>>> applications
>>>> are ready? I know other app servers behave this way out of the box
>>>> so I was
>>>> kind of surprised to see that order of bring up.
>>>> Thanks in advance for any tips,
>>>> Alski
>>>> -- 
>>>> View this message in context:
>>>> Application-Construction-Order...-tp15341625s134p15341625.html
>>>> Sent from the Apache Geronimo - Dev mailing list archive at
>> -- 
>> View this message in context: 
>> Application-Construction-Order...-tp15341625s134p15342519.html
>> Sent from the Apache Geronimo - Dev mailing list archive at  

View this message in context:
Sent from the Apache Geronimo - Dev mailing list archive at

View raw message