The cloudbees SDK 1.1 is attempting to connect to localhost:8080 when I run commands.
Any idea what I need to do to fix it?
Example
bees app:info -v
# CloudBees SDK version: 1.1
Enter application ID (ex: account/appname) : account/app
API call: http://localhost:8080/api?timestamp=1344846702&v=1.0&api_key=KEY&action=application.info&app_id=account%2Fapp&format=xml&sig_version=1&sig=SIGN
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Aug 13, 2012 6:31:42 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
ERROR: Connection refused
Thank you
Jono
Add bees.api.url=https\://api.cloudbees.com/api to ~/.bees/bees.config
After backing up ~/.bees and then running bees init and recreating my bees configuration directory I noticed the extra entry in bees.config.
Related
This question already has answers here:
Getting error while running the selenium test cases with selenium grid?
(1 answer)
What is the exact purpose of Selenium Grid?
(1 answer)
selenium grid listening on node port instead of hub port
(3 answers)
Closed 2 years ago.
I am trying to bring the selenium Grid up and running in my local machine and the below is the command that i ran on my local machine.
java -jar selenium-server-standalone-2.28.0.jar -role webdriver -hub http://<IP>:4444/grid/register -host <IP>
Nov 27, 2017 7:42:06 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid node
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: I/O exception (java.net.NoRouteToHostException) caught when connecting to the target host: No route to host (Host unreachable)
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: Retrying connect
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: I/O exception (java.net.NoRouteToHostException) caught when connecting to the target host: No route to host (Host unreachable)
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: Retrying connect
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: I/O exception (java.net.NoRouteToHostException) caught when connecting to the target host: No route to host (Host unreachable)
Nov 27, 2017 7:42:07 PM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: Retrying connect
Nov 27, 2017 7:42:07 PM org.openqa.grid.internal.utils.SelfRegisteringRemote startRemoteServer
WARNING: error getting the parameters from the hub. The node may end up with wrong timeouts.No route to host (Host unreachable)
19:42:07.460 INFO - Java: Oracle Corporation 25.131-b11
19:42:07.464 INFO - OS: Linux 4.10.0-38-generic amd64
19:42:07.477 INFO - v2.28.0, with Core v2.28.0. Built from revision 18309
19:42:07.582 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:5555/wd/hub
19:42:07.583 INFO - Version Jetty/5.1.x
19:42:07.584 INFO - Started HttpContext[/selenium-server,/selenium-server]
19:42:07.586 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler#1d8d30f7
19:42:07.587 INFO - Started HttpContext[/wd,/wd]
19:42:07.587 INFO - Started HttpContext[/selenium-server/driver,/selenium-
Also, i am facing the same issue while running the above command in my Virtual machine as well.
I have deployed a web application to Tomcat 7.0.47 however I see a 404 status.
I can access Tomcat homepage and Tomcat Application Manager without issues.
Here are the log files:
catalina.2016-07-13
Jul 13, 2016 8:51:29 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.8.0_31\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\OpenCL SDK\3.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\3.0\bin\x64;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;F:\MATLAB\R2014a\runtime\win64;F:\MATLAB\R2014a\bin;C:\Program Files\MATLAB\R2012a\runtime\win64;C:\Program Files\MATLAB\R2012a\bin;C:\Program Files (x86)\PharosSystems\Core;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\Doctrine extensions for PHP\;C:\Program Files\apache-maven-3.3.9-bin\bin;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\;.
Jul 13, 2016 8:51:29 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jul 13, 2016 8:51:29 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jul 13, 2016 8:51:29 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 514 ms
Jul 13, 2016 8:51:29 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jul 13, 2016 8:51:29 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.47
Jul 13, 2016 8:51:29 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\apache-tomcat-7.0.47\webapps\cs144.war
Jul 13, 2016 8:51:30 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\docs
Jul 13, 2016 8:51:30 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\examples
Jul 13, 2016 8:51:30 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\host-manager
Jul 13, 2016 8:51:31 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\manager
Jul 13, 2016 8:51:31 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\ROOT
Jul 13, 2016 8:51:31 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\Struts2Example
Jul 13, 2016 8:51:31 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.47\webapps\zurmo
Jul 13, 2016 8:51:31 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jul 13, 2016 8:51:31 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jul 13, 2016 8:51:31 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1435 ms
localhost.2016-07-13
Jul 13, 2016 8:51:30 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Jul 13, 2016 8:51:30 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Jul 13, 2016 8:51:30 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsCache', 'org.apache.jasper.compiler.TldLocationsCache#7a1f7380')
localhost_access_log.2016-07-13
0:0:0:0:0:0:0:1 - admin [13/Jul/2016:08:53:14 +0430] "POST /manager/html/upload?org.apache.catalina.filters.CSRF_NONCE=210FE5528CB1E9D58F23E5A11655B102 HTTP/1.1" 403 3287
0:0:0:0:0:0:0:1 - - [13/Jul/2016:08:53:14 +0430] "GET /favicon.ico HTTP/1.1" 200 21630
0:0:0:0:0:0:0:1 - - [13/Jul/2016:08:53:18 +0430] "GET /manager/ HTTP/1.1" 302 -
0:0:0:0:0:0:0:1 - admin [13/Jul/2016:08:53:18 +0430] "GET /manager/html?org.apache.catalina.filters.CSRF_NONCE=7D8792E571C6ABBD8D35351293AF54B8 HTTP/1.1" 200 20949
0:0:0:0:0:0:0:1 - - [13/Jul/2016:08:53:33 +0430] "GET /cs144/ HTTP/1.1" 404 963
manager.2016-07-13
Jul 13, 2016 8:53:14 AM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost'
Jul 13, 2016 8:53:14 AM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: init: Global resources are available
Jul 13, 2016 8:53:18 AM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
What you need to do is use the facility in web.xml.
The servlet spec provides a facility for applications to indicate what file(s) should be used when the client doesn't specify one in a path -- e.g. GET /directory/. You can specify as many files as you want, and the first one found will be used. So you could have e.g. index.html in there as well as anything else you might want. The default list is (in order):
index.html
index.htm
index.jsp
If you specify a <welcome-file-list> in your web.xml, you'll override the default. So, if you want to be able to fall-back to the original list, you'll need to specify all of the options.
Example:
web.xml
...
...
<welcome-file-list>
<welcome-file>results.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
...
...
The web.xml file should be in your application's WEB-INF/web.xml, and probably already exists. Make sure you follow the schema and put it in the right place.
I have deployed SOAP Service using tomcat. I pushed a request to the SOAP service and it worked. But when i submitted bulk request., tomcat crashed.
I can see below error in log files:-
SEVERE: Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=7106] ignored exception: java.net.SocketException: Too many open files
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:408)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:71)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
WARNING: Reinitializing ServerSocket
Jun 5, 2014 6:43:08 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
SEVERE: Endpoint null ignored exception: java.net.SocketException: Too many open files
java.net.SocketException: Too many open files
at java.net.ServerSocket.createImpl(ServerSocket.java:255)
at java.net.ServerSocket.getImpl(ServerSocket.java:205)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:141)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:293)
at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:469)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:71)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
Jun 5, 2014 6:43:08 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
WARNING: Restarting endpoint
Jun 5, 2014 6:43:08 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
SEVERE: Endpoint null shutdown due to exception: java.net.SocketException: Too many open files
java.net.SocketException: Too many open files
at java.net.ServerSocket.createImpl(ServerSocket.java:255)
at java.net.ServerSocket.getImpl(ServerSocket.java:205)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:141)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:293)
at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:481)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:71)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
Jun 5, 2014 6:43:08 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception (java.lang.ThreadDeath) executing org.apache.tomcat.util.net.LeaderFollowerWorkerThread#4d8d50, terminating thread
Can some body tell me cause and solution to the problem.
i'm trying to get CouldBees working. Heres the error i get when im running:
C:\cloudbees-sdk-1.5.0>bees init --proxyHost=localhost --proxyPort=8008 (or 8080)
You have not created a CloudBees configuration profile, let's create
one now... Enter your default CloudBees API end point [us | eu]: eu
Enter your CloudBees account email address: abs#abs.com
Enter your CloudBees account password: Jul 18, 2013 1:32:09 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect Jul 18, 2013 1:32:09 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: Retrying request Jul 18, 2013 1:32:10 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect Jul 18, 2013 1:32:10 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: Retrying request Jul 18, 2013 1:32:11 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect Jul 18, 2013 1:32:11 PM
org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: Retrying request
ERROR: Initialization failure: Cannot create configuration
Can anyone read out what's causing this error?
It looks like the SDK can't establish Internet connections to the CloudBees website. If you are running behind a proxy, you will need to use proxy flags to connect.
bees init --proxyHost=YOUR_PROXY_HOST --proxyPort=YOUR_PROXY_PORT
This is covered in the CloudBees SDK docs: Running behind a proxy
It helps, to set the system time exactly to six hours ago (US-time).
Also cloudbees documentation sais, that You should create on your file system (under Windows7) c:\Users\Your_User.bees\bees.config file, which contains following line (if you want to call cloudbbees eu server):
bees.api.url=https\://api-eu.cloudbees.com/api>
but actually it didn't help in my case (maybe outdated version)
When i tried to access Restful web service using JAXRS on localhost, I am receiving below mentioned ERROR. I did check for duplicate jar files and even my web.xml seems to be correct. Any idea where i am going wrong ?
ERROR (i) : [ when tried accessing localhost ]
ERROR (ii) : [in Eclipse console ]
INFO: Starting Servlet Engine: Apache Tomcat/7.0.27
May 10, 2012 2:08:19 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /validatorService threw load() exception
javax.servlet.ServletException: Resource configuration class, validatorService.ValidatorServiceConfig, is not a super class of class javax.ws.rs.core.Application
at com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig(WebComponent.java:741)
at com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig(WebComponent.java:678)
at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:203)
at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:373)
at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:556)
at javax.servlet.GenericServlet.init(GenericServlet.java:160)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1566)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1556)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
May 10, 2012 2:08:19 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files (x86)\apache-tomcat-7.0.27\webapps\docs
May 10, 2012 2:08:19 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files (x86)\apache-tomcat-7.0.27\webapps\examples
May 10, 2012 2:08:20 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
May 10, 2012 2:08:20 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
May 10, 2012 2:08:20 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsCache', 'org.apache.jasper.compiler.TldLocationsCache#79e582c1')
May 10, 2012 2:08:20 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files (x86)\apache-tomcat-7.0.27\webapps\host-manager
May 10, 2012 2:08:20 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files (x86)\apache-tomcat-7.0.27\webapps\manager
May 10, 2012 2:08:20 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files (x86)\apache-tomcat-7.0.27\webapps\ROOT
May 10, 2012 2:08:20 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
May 10, 2012 2:08:20 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
May 10, 2012 2:08:20 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 675 ms
ERROR (iii) Apache / log
127.0.0.1 - - [10/May/2012:14:28:18 -0500] "GET / HTTP/1.1" 200 11444
0:0:0:0:0:0:0:1 - - [10/May/2012:14:28:18 -0500] "GET /validatorService/WEB-INF/classes/validatorService/ValidatorService.java HTTP/1.1" 404 952
0:0:0:0:0:0:0:1 - - [10/May/2012:14:28:34 -0500] "GET /validatorService/rest/ HTTP/1.1" 500 2604
0:0:0:0:0:0:0:1 - - [10/May/2012:14:28:39 -0500] "GET /validatorService/rest/valid HTTP/1.1" 500 2604
0:0:0:0:0:0:0:1 - - [10/May/2012:14:28:52 -0500] "GET /validatorService/rest/valid HTTP/1.1" 500 2604
Should have figured it out, as soon as i saw this. Anyways this is what my mistake is
ERROR:
javax.servlet.ServletException: Resource configuration class, validatorService.ValidatorServiceConfig, is not a super class of class javax.ws.rs.core.Application
FIX:
public class ValidatorServiceConfig extends Application
BEFORE:
public class ValidatorServiceConfig