Apache Friends Support Forum

I would run on the same computer Collabnet Subversion Edge 3.0.1 with its Apache instance and XAMPP 1.8.0 with its instance of Apache for others intranet services.
To avoid any conflict, I changed the port for XAMPP Apache to 81, but any instance is launched as second fail to start.
Further, if SubversionEdge is run first, the Control Panel of XAMPP looks like:

10.45.48 [apache] Possible problem detected!
10.45.48 [apache] Port 80 in use by "httpd.exe"!

Even if the XAMPP Apache is not set as a service.

Does the XAMPP Apache actually start? That 'might' be a warning only.

what happens when you go to http://localhost/index.php:81 ???

thanks

I cannot start Apache from Control Panel because the CP tells that Apache is already running on port 80 (see the messages of the CP below).
If I set xampp/Apache as service, I cannot start anymore the csvn/Apache!
Why the CP looks at port 80? Is there somthing else to configure?

Thanks a lot .
Giorgio


9.15.45 [main] Initializing Control Panel
9.15.45 [main] Windows Version: Windows XP SP3 32-bit
9.15.45 [main] XAMPP Version: 1.8.0
9.15.45 [main] Control Panel Version: 3.0.12 [ Compiled: June 24th 2012 ]
9.15.45 [main] Running with Administrator rights - good!
9.15.45 [main] XAMPP Installation Directory: "c:\xampp\"
9.15.45 [main] Initializing Modules
9.15.45 [apache] Possible problem detected!
9.15.45 [apache] Port 80 in use by "httpd.exe"!
9.15.45 [main] Starting Check-Timer
9.15.45 [main] Control Panel Ready

P.S.

I tryed to run XAMPP 1.7.7 an runs fine using the port 8088.
With XAMPP 1.8.0 i get the problem.

I changed the port to 8088 in xampp 1.8.0,
stop csvn\httpd.exe,
run xampp\apache\httpd
then start csvn\httpd.exe

and now works both apache.

Further the "admin" button of the Control Panel open in firefox the localhost instead of localhost:8088.
Seems that the Control Panel act only on the port 80, and the httpd.conf doen't change the behaviour of the CP.

P.P.S.
I found in \xampp\xampp-control.ini used by Control Panel 3.x
[ServicePorts]
Apache=80
This seems to force the Control Panel to use the port 80 in order to find, start & stop the Apache service, whatever port is configured in httpd.conf.

This cause some troubles if there is another Apache service that is using the port 80

That's why the Control Panel v3 has a configuration Button where you can change the ports the same as in your httpd.conf.
The CPv3 don't parse the Apache configuration files, because that is not an easy task. Configurations can be very different.

I know that I should read everything before to act.
But any suggestion is welcome asap . Thanks anyway.