TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Cédric Beust ♔-2
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

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

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Di6I8zyLhUoJ">veena...@...> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Di6I8zyLhUoJ">veena...@... 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Di6I8zyLhUoJ">testng-users...@googlegroups.com.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Di6I8zyLhUoJ">testng...@....
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Fanindra Bapat
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Fanindra Bapat
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena

Identify some relationship with LookBack Adapter in windows 7, but not able to fix it ....
any clue?


On Wednesday, 10 July 2013 15:27:23 UTC+5:30, Veena Devi wrote:
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

veena

Removed the localhost setup from host file .. Done ! Fixed....


On Wednesday, 10 July 2013 17:04:13 UTC+5:30, Veena Devi wrote:

Identify some relationship with LookBack Adapter in windows 7, but not able to fix it ....
any clue?


On Wednesday, 10 July 2013 15:27:23 UTC+5:30, Veena Devi wrote:
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)
	at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213)
	at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201)
	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:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


On Tuesday, 9 July 2013 09:22:39 UTC+5:30, Cédric Beust ♔ wrote:
This typically happens because you have another (older) testng.jar in your classpath.

What happens if you create a workspace from scratch and try again?


-- 
Cédric



On Mon, Jul 8, 2013 at 7:26 PM, Veena Devi <[hidden email]> wrote:
Hi, I am using eclipse with testng from past 2 yrs. Yesterday suddently my eclipse hans on test ng test case execution with showing 57% process. 

I tried to stop /restart/ reinstall testng ,/Change workspace, created new work space, installed test ng from plugin / from eclipse marketplace ...  new eclipse... 
almost all combination..But still no luck . 

Please provide a solution , its high priority for me and very urgent . 

Quick response is highly appreciated. 

Cheers 
Veena 
[hidden email] 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Krishnan Mahadevan
Veena

For the sake of future reference can you please explain in detail as to what you did to fix the problem ?


On Thursday, July 11, 2013, Veena Devi wrote:

Removed the localhost setup from host file .. Done ! Fixed....


On Wednesday, 10 July 2013 17:04:13 UTC+5:30, Veena Devi wrote:

Identify some relationship with LookBack Adapter in windows 7, but not able to fix it ....
any clue?


On Wednesday, 10 July 2013 15:27:23 UTC+5:30, Veena Devi wrote:
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:


--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Yohann CINTRE
I just ran into the same issue.

Removing the redirection from "localhost" to a virtual machine IP in the Windows host file fixed it.

Thanks Veena for the tip!


Config used :
Win 7 64 bit
Juno Service Release 2
Java 1.6
TestNG 6.8.1



On Thursday, July 11, 2013 6:46:29 AM UTC+2, Krishnan wrote:
Veena

For the sake of future reference can you please explain in detail as to what you did to fix the problem ?


On Thursday, July 11, 2013, Veena Devi wrote:

Removed the localhost setup from host file .. Done ! Fixed....


On Wednesday, 10 July 2013 17:04:13 UTC+5:30, Veena Devi wrote:

Identify some relationship with LookBack Adapter in windows 7, but not able to fix it ....
any clue?


On Wednesday, 10 July 2013 15:27:23 UTC+5:30, Veena Devi wrote:
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:


--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: TestNg Crash in Eclipse-Win7 64 Bit Java 1.6 testng 6.8

Snigdha
Yohann,
    I am still facing the same issue... All the lines in the hosts file is commented. Could you guide me? And if hosts file was the issue, then why was it running fine earlier?

Thanks,
Snigdha.

On Monday, November 18, 2013 8:36:41 PM UTC+5:30, Yohann CINTRE wrote:
I just ran into the same issue.

Removing the redirection from "localhost" to a virtual machine IP in the Windows host file fixed it.

Thanks Veena for the tip!


Config used :
Win 7 64 bit
Juno Service Release 2
Java 1.6
TestNG 6.8.1



On Thursday, July 11, 2013 6:46:29 AM UTC+2, Krishnan wrote:
Veena

For the sake of future reference can you please explain in detail as to what you did to fix the problem ?


On Thursday, July 11, 2013, Veena Devi wrote:

Removed the localhost setup from host file .. Done ! Fixed....


On Wednesday, 10 July 2013 17:04:13 UTC+5:30, Veena Devi wrote:

Identify some relationship with LookBack Adapter in windows 7, but not able to fix it ....
any clue?


On Wednesday, 10 July 2013 15:27:23 UTC+5:30, Veena Devi wrote:
Can anyone Provide online Help? Through skype?

veenadevi.s -my Skype Id



On Wednesday, 10 July 2013 15:13:09 UTC+5:30, Veena Devi wrote:
No luck :-(....


Whats this Error stack means for?

!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:373)


On Wednesday, 10 July 2013 14:28:39 UTC+5:30, Fanindra Bapat wrote:
Navigate to Debug section and remove breakpoints from there

On Wednesday, 10 July 2013 14:23:42 UTC+5:30, Veena Devi wrote:
How to remove breackpoints? fro where ? 
I Have only one version of testng ...

On Wednesday, 10 July 2013 14:07:11 UTC+5:30, Fanindra Bapat wrote:
Try following things:

  •    Remove all existing breakpoints
  •    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
  •   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.



On Wednesday, 10 July 2013 13:31:36 UTC+5:30, Veena Devi wrote:

I tried All possible options

1. New Eclipse +TestNG
2. Complete New WorkSpace
3. Eclipse Juno/helios
4. Tesng from Maven 
5. Update my eclipe .ini with increased size...



But no Luck , Any help is highly appreciated  as this is blocker ...




Error Log from eclipse


ENTRY org.testng.eclipse 4 4 2013-07-10 13:10:00.276
!MESSAGE Error
!STACK 0
java.net.SocketTimeoutException: Accept timed out
	at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method)
	at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
	at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
	at java.net.PlainSocketImpl.accept(Unknown Source)
	at java.net.ServerSocket.implAccept(Unknown Source)
	at java.net.ServerSocket.accept(Unknown Source)
	at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128)
	at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:


--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

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