Re: [Php-java-bridge-users] Deploying the php-java bridge under JBoss

[<php...@li...>]

On Monday 30 November 2009, php...@li... wrote:
> This port clash seems to be a common problem in jboss 4. See
> http://www.thedance.net/~roth/TECHBLOG/jbossports.html
> Changing the ports as suggested should solve the problem.

Oh, 1000 thanks, indeed, changing the jboss default port solved the problem.


> I don't think we can do anything here. We can't change the log4j standard
> port and we can't change the jboss defaults.

On the contrary, I'm thinking of at least a couple of things :)

Even if you don't change anything, don't you think that at least it should be 
mentioned in the FAQ perhaps ? :)

In the beginning, it wasn't clear for me that the bridge scans for the port and 
then uses it because the exception I pasted on my original post really doesn't 
help at all.


But now that it came all clear, you can set the log4j logger to listen on a 
different port:

java -Dchainsaw.port=14445 org.apache.log4j.chainsaw.Main

In the same direction, does it make sense to ask for a new feature? 
The port that the bridge scans for, could also be configurable in the same way:
-Dphp.java.bridge.default_log_port=14445
(I see that it is a static final variable in php.java.bridge.ChainsawLogger)

This could eventually help your JBoss users to maintain all jboss default ports 
and just configure the bridge (which is the deployable). And not vice versa :)

If you'd like, I could contribute this small patch.


Thanks for your support! :)

> Regards,
> Jost Boekemeier


-- 
Thanos Kyritsis <djart at linux.gr>