Did you ever figure this out?  I'm having a very similar issue and have yet 
to find a solution.

Thanks

Dan

On Monday, June 20, 2011 6:15:02 AM UTC-4, Inge wrote:
>
>
> According to both docs and several other resources (e.g. 
> http://confluence.public.thoughtworks.org/display/CCNET/The+Server+Service+Application)
>  
> it sounds like running multiple instances of ccnet should be easy as pie.
>
> I have a separate copy of the server in its own directory, and it works 
> fine.
> I then change the TCP port it is using, which defaults to 21234. I do this 
> in ccnet.exe.config as I am testing from the console app, like so:
>
>   <system.runtime.remoting>
>     <application>
>       <channels>
>         <!--<channel ref="tcp" port="21234">-->
>     <channel ref="tcp" port="7777">
>           <serverProviders>
>             <formatter ref="binary" typeFilterLevel="Full"/>
>           </serverProviders>
>         </channel>
>       </channels>
>     </application>
>   </system.runtime.remoting>
>
> This looks good during initial startup:
>
> C:\CCNET\Main>ccnet
> CruiseControl.NET Server 1.6.7981.1 -- .NET Continuous Integration Server
> Copyright © 2003 - 2011 ThoughtWorks Inc.  All Rights Reserved.
> .NET Runtime Version: 2.0.50727.4959    Image Runtime Version: v2.0.50727
> OS Version: Microsoft Windows NT 6.1.7600.0     Server locale: nb-NO
>
> <-- snip -->
>
> [CCNet Server:WARN] Configuration does not have any version information - 
> assuming the configuration is for version 1.6
> [CCNet Server:INFO] Log cache time set to 5 minutes
> [CCNet Server:INFO] Registered channel: tcp
> [CCNet Server:INFO] CruiseManager: Listening on url: tcp://
> 164.9.245.117:7777/CruiseManager.rem
> [CCNet Server:INFO] Registered channel: tcp
> [CCNet Server:INFO] CruiseServerClient: Listening on url: tcp://
> 164.9.245.117:7777/CruiseServerClient.rem
> [CCNet Server:INFO] Starting CruiseControl.NET Server
>
> However, then it still tries to connect to the default port:
>
> [Cargo:DEBUG] Retrieving ProjectStatus from server: 
> tcp://localhost:21234/CruiseManager.rem
>
> Which of course doesn't work so well:
>
> [Cargo:ERROR] INTERNAL ERROR: No connection could be made because the 
> target machine actively refused it 127.0.0.1:21234
> ----------
> ThoughtWorks.CruiseControl.Remote.CommunicationsException: No connection 
> could be made because the target machine actively refused it 
> 127.0.0.1:21234
>    at 
> ThoughtWorks.CruiseControl.Remote.RemotingConnection.SendMessage(String 
> action, ServerRequest request)
>    at 
> ThoughtWorks.CruiseControl.Remote.CruiseServerClient.GetProjectStatus()
>    at 
> ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.GetCurrentProjectStatus()
>    at ThoughtWorks.CruiseControl.Core.Triggers.ProjectTrigger.Fire()
>    at ThoughtWorks.CruiseControl.Core.Triggers.MultipleTrigger.Fire()
>    at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.PollTriggers()
>    at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate()
>    at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Run()
> ----------
>
>
> Checking with netstat and telnet I can confirm that it IS listening on 
> port 7777 and that it is possible to connect.
>
> So at this point I am not sure if there is something obvious I have 
> missed, or if there is an actual bug related to this.
>
> Thank you for your time.
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ccnet-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to