Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353888

Summary: Connecting to embedded AUT Agent is not always possible
Product: [Technology] Jubula Reporter: Oliver Goetz <Oliver.Goetz>
Component: AgentAssignee: Zeb Ford-Reitz <zeb.ford-reitz>
Status: CLOSED FIXED QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: normal    
Priority: P3 CC: Achim.Loerke, alexandra.schladebeck
Version: 1.0.0   
Target Milestone: Juno M6   
Hardware: All   
OS: Windows Server 2008   
Whiteboard:

Description Oliver Goetz CLA 2011-08-04 09:50:44 EDT
Sometimes connecting to the embedded Agent is not possible unless you change the port. This can be very confusing since this is an embedded AUT Agent. However the workaround is to change the port for the Agent.
Comment 1 Oliver Goetz CLA 2011-08-04 09:54:38 EDT
Maybe this problem appears when someone else is already using the embedded AUT Agent with the default port.
Comment 2 Achim Loerke CLA 2011-08-10 04:06:16 EDT
@Zeb: Please add a warning dialog
Comment 3 Zeb Ford-Reitz CLA 2011-09-13 11:48:42 EDT
Missed the cutoff for Indigo SR1. Re-scheduling to Indigo SR2.
Comment 5 Zeb Ford-Reitz CLA 2011-09-20 02:45:25 EDT
Fix also applied to the Indigo SR1 maintenance branch:
http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?h=indigo_sr1&id=1c536c71c5a927099a8af830108d2879072d7c97

This does not mean that the fix is included in Indigo SR1, just that, if we decide to release a patch version, this fix will be in it.
Comment 6 Oliver Goetz CLA 2011-09-27 03:26:59 EDT
Starting the embedded AUT Agent on the same port with two GUIdancers running now shows a "problem occurred"-dialog telling that another instance of the AUT Agent already uses this port. Tested with current GD