I am trying to create a new lagom scala project on windows 7 machine (behind proxy) but I get error message "org.eclipse.jgit.api.errors.TransportException: git://github.com/lagom/lagom-scala.g8.git: Connection time out"
Here is the command : sbt new lagom/lagom-scala.g8
I have the proxy environment variable http_proxy set but still I get this error. Any thoughts idea..to make this work ?
There's a discussion about this at https://github.com/lagom/lagom/issues/683
The conclusion is that this is a limitation of sbt 0.13.13, which uses the git protocol to clone templates and cannot be made to use an alternate protocol.
You can work around this by both forcing a newer version of sbt and specifying the complete https URL of the repository, like this:
sbt new -Dsbt.version=0.13.15 https://github.com/lagom/lagom-scala.g8
Related
I am trying to execute a Gatling scenario to the https://demostore.gatling.io website, after register it through Chrome HAR export (inside my dev environment).
Import and everything goes smoothly, but when I run the scenario I receive the following error:
i.n.c.ConnectTimeoutException: connection timed out: demostore.gatling.io/54.147.169.32:80
I then tried to set up the IntelliJ proxy from Settings → System Settings → HTTP Proxy, setting it to Manually and providing the correct proxy configuration → Test Connection vs http://demostore.gatling.io and the IDE returns Connection Succesful.
Currently, my environment is as follow:
Intellij IDEA 2020.3
Gatling 3.5.1
Ubuntu 20.04 LTS 64 bit (on VirtualBox)
I am behind a VPN with proxy (need this since Maven is configured to use the internal Nexus repo)
This question was answered by #StéphaneLANDELLE, but the thread was deleted after editing something in the above question.
Stéphane was pointing me correctly to: Proxy parameters in the official Gatling documentation and after setting:
http.proxy(Proxy("<URL>", <PORT>).credentials("<user>", "<pwd>"))
everything started working as expected.
I'm trying to build kotlin multiplatfrom project behind corporate proxy connection and got and error:
Couldn't find package "webpack#4.42.1" required by "projectName#version" on the npm registry.
and so on.. (I'm not listing all the error dependencies, but it got the same message)
I'm using kotlin.gradle.kts
and I have already tried
systemProp.http.proxyHost=..
systemProp.http.proxyPort=..
...
systemProp.https.proxyHost=..
systemProp.https.proxyPort=..
and so on with domain credential ..., it works with gradle wrapper download, or gradle sync.. but not when it come to kotlinNpmInstall..
I tried using public connection from my personal device and works, so I think it still the proxy issue..
is there anything I missed to setup the proxy related to the kotlinNpmInstall ? and is there any kotlin-gradle-dsl approach for this kind of proxy configuration for spesific js build ?
Your problem looks like KT-38067. As a WA you can configure settings for yarn via .yarnrc and .npmrc in the project folder.
I don't see any issues when I run the server and client on the local worksapce(via eclipse). However there are issues if the client is executed from a different machine than on server or executed from exported client product(i.e. Eclipse rcp).
I also read article on JNDI and various online blogs. Please let me know if I am missing anything obvious. Trying to get the remote client working for couple of days now. :(
Object returnValue = context.lookup("ejb:GeoEE/GeoEJB/UserRegistrationService!com.geo.request.ejb.IUserRegistrationService");
above line returns Object in local environment and null in case of remote or exported client.
Replace "ejb:" to "/"
If not set, use this properties to init context(replace server and port):
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.provider.url=http-remoting://127.0.0.1:8080
jboss.naming.client.ejb.context=true
I have installed Android studio and i want to build first app. Unfortunately "Gradle project sync failed" Error: Connection refused: connect.
I know it's because i use proxy server (my company does). I already made changes in Setings->HTTP Proxy-> Auto-detect proxy settings, but I guess, Gradle doesn't look on it. I read I should make write in gradle.properties my proxy server, user and password, but I don't know this parameters, and i don't know how to get them (even if it is available or not).
Can you help me? there are two ways: 1. If you know tell me how to avoid this problem without that parameters. For example like Auto-detect 2. How to get those parameters?
Apparently this code works
systemProp.http.proxyHost=<hostname>
systemProp.http.proxyPort=8080
systemProp.http.proxyUser=
systemProp.http.proxyPassword=
systemProp.http.nonProxyHosts=localhost
or for https
systemProp.https.proxyHost=<hostname>
systemProp.https.proxyPort=8080
systemProp.https.proxyUser=
systemProp.https.proxyPassword=
systemProp.https.nonProxyHosts=localhost
when password isn't set up.
It should be in gradle.properties file.
Enable No Proxy from Appearance and Behavior -> System Settings-> HTTP Proxy -> NO Proxy
This is worked for me
I'm using cargo to deploy my project to a test server. The cargo config is fine, works well on my local machine. However, on the hudson machine it always fails with a stacktrace showing:
Caused by: java.io.IOException: Server returned HTTP response code: 407 for URL: http://ppdtest.kbcsecurities.net:8080/manager/text/list
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:507)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:644)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:657)
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:173)
... 34 more
The thing is however, I have NO proxy defined anywhere. Not in my setting.xml, not in the pom.xml files (parent or childs).
Anyone has some pointers or help to offer?
Are you sure that this is a proxy problem? The URL looks like it's Tomcat's Manager application. Can you verify that you're using the right credentials for your Tomcat instance?
If you want to make sure that no proxy is involved, please check the environment variables of the machine to see whether there's any global proxy setting that Java could be picking up, either in the global Maven options or in the options for Hudson.
One other thing to try is whether you can access the URL in question using a browser from the Hudson machine. If it's a headless machine, you can use a terminal browser like links and see if you can authenticate with that.