Ticket #8196 (closed task: invalid)

Opened 7 years ago

Last modified 7 years ago

Changes in VirtualBox webserver broke the virtualbox-plugin for Hudson

Reported by: mmzik Owned by:
Priority: major Component: webservices
Version: VirtualBox 4.0.2 Keywords: vboxwebsrv
Cc: Guest type: other
Host type: other


Changes made from VirtualBox version 3.2+ to 4.0+ broke the virtualbox-plugin for Hudson. I highly suggest that you ensure compatibility, because a) both products Hudson and VirtualBox are made by your company and b) the virtualbox-plugin for Hudson should be considered as a key-plugin!

I created a issue on the Hudson-side too, please see here:

When Hudson (or to be precise the virtualbox-plugin) tries to connect to the VirtualBox-webserver (4.0+) the following exception-stack is dumped:

FATAL: HTTP transport error: Connection refused: connect HTTP transport error: Connection refused: connect at at at at at at at at at at at at at at $Proxy47.iWebsessionManagerLogon(Unknown Source) at at hudson.plugins.virtualbox.VirtualBoxUtils.connect( at hudson.plugins.virtualbox.VirtualBoxUtils.getMachines( at hudson.plugins.virtualbox.VirtualBoxCloud.retrieveMachines( at hudson.plugins.virtualbox.VirtualBoxCloud.getVirtualMachines( at hudson.plugins.virtualbox.VirtualBoxPlugin.getVirtualBoxMachine( at hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch( at hudson.slaves.SlaveComputer$ at java.util.concurrent.FutureTask$Sync.innerRun( at at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: Connection refused: connect at Method) at at at at at at at at at at<init>( at at at at at at at ... 26 more

Change History

comment:1 Changed 7 years ago by frank

  • Status changed from new to closed
  • Resolution set to invalid

Sorry, this is the wrong place to report this issue.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use