> -----Original Message----- > From: Florin Vancea [mailto:[EMAIL PROTECTED] > Sent: 06 August 2003 18:02 > To: Cactus Developers List > Subject: Re: setPort is missing on JBoss3xContainer > > Cactus waits on the container by polling the URL, which is composed with > the > port, too. > If I setup a JBoss on 9080 (for the reasons below), I have no means to > tell > Cactus that the JBoss started with the "startup" script should be > "contacted" at 9080. Cactus will look for it at 8080 and obviously it will > decide that the startup process failed, even if the startup was > successful, > but on 9080. >
You're right! ;-) > Therefore I have to be able to tell Cactus "I've manually taken care of > the > details and be so kind to look for the JBoss you are starting at _this_ > port" > > About setting the port (aka configuring JBoss programatically on an > arbitrary port): > The method is different in 3.0.x and 3.2.x. > In 3.0.x, there is a "tomcatX-service.xml" in deploy dir, that holds the > Tomcat config element. Changing it will change the port, but it's rather > complicated. JMX is also tricky, because the Web container is tightly > bound. > In 3.2.x , there is jbossweb-tomcat.sar, conatining in META-INF a > jboss-service.xml rather equivalent to the above "tomcatX-service.xml". > Same > level of difficulty. > yep, that's what I imagined... Not easy but possible. That will be a todo for now... > In short, I see no easy way to reliably configure the port where JBoss's > web > container is listening and the config sould be done manually (short of > duplicating entire "default" configuration and translating all occurences > of > "8080" into the value of cactus.port property). > > My 2c. > > Thanks for replying anyway. > I'm making the change for the port attribute. Thanks -Vincent > Florin > > > ----- Original Message ----- > From: "Vincent Massol" <[EMAIL PROTECTED]> > To: "'Cactus Developers List'" <[EMAIL PROTECTED]> > Sent: Wednesday, August 06, 2003 6:36 PM > Subject: RE: setPort is missing on JBoss3xContainer > > > > Hi Florin, > > > > It's just not done yet. One issue is that setting the port for JBoss is > > done in one of the config file I think. So we'll need to include this > > file in the default Cactus config for JBoss. But then, if you provide > > your own jboss config, how can the Cactus port setting have any effect > > on it? > > > > There may be some Jboss system property that I'm not aware of. > > > > Thanks > > -Vincent > > > > > -----Original Message----- > > > From: Florin Vancea [mailto:[EMAIL PROTECTED] > > > Sent: 06 August 2003 17:30 > > > To: 'Cactus Developers List' > > > Subject: setPort is missing on JBoss3xContainer > > > > > > Hi all. > > > > > > Why there's no > > > > > > public final void setPort(int thePort) > > > > > > in org.apache.cactus.integration.ant.container.jboss.JBoss3xContainer? > > > > > > About all other sibling Containers have it. > > > > > > OK, I understand that currently there's no (simple) way to "move > > around" > > > programatically an existing JBoss installation, but one should be able > > to > > > move the JBoss installation manually, then specify cactus.port=xxxx . > > > > > > I have to run a Cactus setup on a server where 8080 is already taken > > by > > > another server and I cannot afford to move it. > > > > > > If setPort would be available in JBoss3xContainer, then I could setup > > my > > > JBoss on e.g. 9080 (which I actually did) and just tell Cactus to look > > for > > > it there. > > > > > > If it's acceptable, can some of you kind souls make the addition to > > > JBoss3xContainer, so it can get into the next nightly jar or such? > > > > > > Many thanks, > > > Florin > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
