Bug 470393 - Unable to record a test - Socket is closed
Summary: Unable to record a test - Socket is closed
Status: NEW
Alias: None
Product: RCPTT
Classification: Technology
Component: IDE (show other bugs)
Version: 2.0M4   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-17 11:03 EDT by Axel RICHARD CLA
Modified: 2015-06-19 08:54 EDT (History)
2 users (show)

See Also:


Attachments
console.log (58.76 KB, application/octet-stream)
2015-06-19 08:03 EDT, Axel RICHARD CLA
no flags Details
rcptt log (16.96 KB, application/octet-stream)
2015-06-19 08:54 EDT, Axel RICHARD CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel RICHARD CLA 2015-06-17 11:03:30 EDT
With Mac OS, I can't record a test, just replay existing ones.

When I try to record a test, after the contexts initialization step, I get the following error. The test is automatically stopped and the button stop recording is not available anymore in the toolbar of the Control Panel. Instead, the buttons record & replay are active again.

The IDE I used is the one available from the website : http://download.eclipse.org/rcptt/nightly/2.0.0/201506170743/ide/rcptt.ide-2.0.0-N201506170743-macosx.cocoa.x86_64.zip.

I try to update the IDE with the latest version from : http://download.eclipse.org/rcptt/nightly/2.0.0/latest/full/repository
but nothing has changed.

java.net.SocketException: Socket is closed
	at java.net.Socket.getInputStream(Socket.java:903)
	at org.eclipse.rcptt.tesla.internal.core.network.TeslaNetworkCommunication.doConnect(TeslaNetworkCommunication.java:129)
	at org.eclipse.rcptt.core.recording.NetworkRecorder.setFeature(NetworkRecorder.java:201)
	at org.eclipse.rcptt.ui.recording.UiNetworkRecorder.setReplayShortcuts(UiNetworkRecorder.java:122)
	at org.eclipse.rcptt.ui.recording.RecordingSupport$ConnectionRunnable$1$2.run(RecordingSupport.java:848)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
Comment 1 Ulyana Skorokhodova CLA 2015-06-19 04:11:44 EDT
Hi Axel,

Could you please provide us an AUT to reproduce the bug on our side?
Probably, you have a trial/demo version to download? 

Kind regards,
Ulyana.
Comment 3 Ulyana Skorokhodova CLA 2015-06-19 05:46:07 EDT
Hi Axel,

I've just tried on MacOS and everything worked fine. 

Could you please switch you firewall off and try again?
Could you please also check what ports are displayed in your AUT preferences/RCPTT Runtime? Please send their values to us and also, please, attach a console.log file.

Kind regards,
Ulyana.
Comment 4 Axel RICHARD CLA 2015-06-19 08:02:16 EDT
Ulyana,

I try to switch my firewall off but nothing has changed.
when I ran my AUT an information message is displayed in the error log: Activating AUT at host localhost. ECL port: 7001. Tesla port: 7002.
You will find the console.log in attachment.

Thanks for your time.
Comment 5 Axel RICHARD CLA 2015-06-19 08:03:23 EDT
Created attachment 254577 [details]
console.log
Comment 6 Ulyana Skorokhodova CLA 2015-06-19 08:42:56 EDT
Hi Axel,

Could you please also attach RCPTT log file (the attached one seems to be AUT log file)?
You can find it in RCPTT workspace/.metadata directory. 

Kind regards,
Ulyana.
Comment 7 Axel RICHARD CLA 2015-06-19 08:54:48 EDT
Created attachment 254578 [details]
rcptt log

Ulyana,

You will find the rcptt log in attachment.

Regards,