gauge java plugin 0.7.4 error "Environment variable name or value is too long"

[Rajesh Patil]

I am getting an issue running gauge java plugin with below error with latest gauge install 1.0.7 and java 0.7.4

Environment variable name or value is too long.

At C:\install\Gauge\plugins\java\0.7.4\launcher.ps1:91 char:5

+     $env:CLASSPATH = $global:classpath

+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : InvalidOperation: (:) [], ArgumentException

+ FullyQualifiedErrorId : ProviderContentWriteError

Error: Could not find or load main class com.thoughtworks.gauge.GaugeRuntime

Caused by: java.lang.ClassNotFoundException: com.thoughtworks.gauge.GaugeRuntime

my configuration is:-

 

Gauge version: 1.0.7

Commit Hash: ed7b4fd6

Plugins

-------

csharp (0.10.6)

dotnet (0.1.2)

html-report (4.0.9)

java (0.7.4)

python (0.3.7)

ruby (0.5.2)

screenshot (0.0.1)

spectacle (0.1.4)

xml-report (0.2.3)

[Srikanth V]

Hi,

Windows has a limit on the number of characters that it's environment variables can hold . See https://stackoverflow.com/questions/34491244/environment-variable-is-too-large-on-windows-10/41946844 for a more detailed explanation.

I think you'll have to explore and see how you can manage your CLASSPATH, since Gauge preserves your CLASSPATH value while launching gauge-java.

Hope this helps, but feel free to post back with any more information that can help us try and replicate this error.

best regards

Srikanth

[Rajesh Patil]

Hi Srikanth,

I was passed the issue after manipulating the launcher.ps1 file but I am now facing RPC error any help would be appreciated. give below is the error we are getting after running gauge

Failed to kill Runner: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:54339: connectex: No connection could be made because the target machine actively refused it." 

[Srikanth V]

Hi,

Please check the logs/gauge.log in your project directory. It should have logged some more information about the error.

--srikanth