Friends i am trying to automate in IE9 using selenium webdriver but getting following error in eclipse log . Please help.
Internet Explorer is selected
Started InternetExplorerDriver server (32-bit)
2.27.0.0
Listening on port 5032
May 23, 2014 4:48:43 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: recv failed
May 23, 2014 4:48:43 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request
Add this before creating a driver. This will avoid showing the port info.
System.setProperty("webdriver.ie.driver.silent","true");
You can safely ignore the INFO messages which is not actually an issue or error.
Details information on those INFO message are at http://jimevansmusic.blogspot.in/2012/12/seeing-info-messages-in-log-does-not.html
Related
I download the 2020-03 Eclipse Platform Runtime Binary (v4.15 from eclipse-platform-4.15-linux-gtk-x86_64.tar.gz), then invoke the p2 director to install CDT package, but I'm always getting multiple caught exceptions of http://download.eclipse.org not responding (http/https switch doesn't have effect on this).
./eclipse -application org.eclipse.equinox.p2.director -profile SDKProfile -noSplash -roaming -repository http://download.eclipse.org/releases/2020-03,http://download.eclipse.org/releases/2020-03/202003181000/,http://download.eclipse.org/eclipse/updates/4.15/,http://download.eclipse.org/releases/latest,http://download.eclipse.org/tools/cdt/releases/9.11 -installIU org.eclipse.cdt.feature.group/9.11.0.202003091030
I tried it with Oracle JRE 8 and with Oracle JDK 14, I tried it on Debian and RHEL machines, tried different network connection (3 different IPS locations), removed all other plugins I install to nail it down to the CDT plugin. I do not know why or what is causing it, and searching for this problems shows to people that ISP fixed or some similar solution. While mine is consistent for about a year. I always eventually finishes, but it will will print out multiple messages:
Installing org.eclipse.cdt.feature.group 9.11.0.202003091030.
Apr 22, 2020 1:44:29 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://download.eclipse.org:80: The target server failed to respond
Apr 22, 2020 1:44:29 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://download.eclipse.org:80
Apr 22, 2020 1:44:36 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://download.eclipse.org:80: The target server failed to respond
Apr 22, 2020 1:44:36 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://download.eclipse.org:80
Operation completed in 44091 ms.
Using the HTTPS repositories has similar output:
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://download.eclipse.org:443: The target server failed to respond
Apr 22, 2020 4:02:50 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://download.eclipse.org:443
Operation completed in 46934 ms.
It's not critical as it eventually completes and the end result works, but I would like to understand it better what is happening, what has effect on this behaviour. When I shrink the list of repositories to these two, it will still install, but the messages will be present:
http://download.eclipse.org/releases/2020-03,http://download.eclipse.org/tools/cdt/releases/9.11
Is there maybe a resource/documentation which probably I missed and is explaining more in the detail what is happening and why?
I've inherited a platform which runs Zookeeper and Solr. The main problem at first was the zoo.cfg and Zookeeper had old setup so DNS named resolution wasn't working.
I've already fixed. I also fixed the issue of the myid value in /var/lib/zookeeper thanks to this thread (someone left a string value there...)
Zookeeper - three nodes and nothing but errors
Now, the output of logs is different:
2017-08-28 14:24:19,368 [myid:3] - WARN [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager#400] - Cannot open channel to 2 at election address zookeeper-test-2/10.240.102.89:3888
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:381)
at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectAll(QuorumCnxManager.java:426)
at org.apache.zookeeper.server.quorum.FastLeaderElection.lookForLeader(FastLeaderElection.java:843)
at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:822)
2017-08-28 14:24:19,368 [myid:3] - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:QuorumPeer$QuorumServer#149] - Resolved hostname: zookeeper-test-2 to address: zookeeper-test-2/10.240.102.89
2017-08-28 14:24:19,368 [myid:3] - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:FastLeaderElection#852] - Notification time out: 400
and If I run this script from one EC2 inside the VPC I can see is almost working:
+
+ SOLR
+ Online Nodes: 2
+ solrcloud-test-2 [ Connection to 8983 succeeded ]
+ solrcloud-test-1 [ Connection to 8983 succeeded ]
-------------
+ ELB not responding properly. HTTP response: 503
+
+ ZOOKEEPER
+ Online Instances: 3
+ zookeeper-test-3 [ Connection to 2181 succeeded ]
+ zookeeper-test-2 [ Connection to 2181 succeeded ]
+ zookeeper-test-1 [ Connection to 2181 succeeded ]
+ Minimal Configured: 3
+ Cluster Status: UP
as you can see even the Solr Ec2 seems to be online the ELB doesn't detect the path of the Solr.
I checked the parameters of how Tomcat was bringing up the Solr and I detected again a misconfiguration related to the hostnames so I fixed and restarted Tomcat, however my ELB health check still does not detect the url.
This check is setup as
HTTP:8983/solr/
I do a netstat I can see the port up and listening
[root#solrcloud-test-2 ~]# netstat -lnp |grep 8983
tcp 0 0 :::8983 :::* LISTEN 3338/java
Moreover another thing I noticed is even I restarted tomcat the logs of serviced are freezed in the past 25th of August!
ERROR - 2017-08-25 17:10:25.369; org.apache.solr.common.SolrException; null:org.apache.solr.common.SolrException: java.net.UnknownHostException: zookeeper-1: unknown error
at org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient.java:139)
at org.apache.solr.cloud.ZkController.<init>(ZkController.java:207)
at org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:152)
at org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:67)
at org.apache.solr.core.CoreContainer.load(CoreContainer.java:216)
at org.apache.solr.servlet.SolrDispatchFilter.createCoreContainer(SolrDispatchFilter.java:189)
at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:136)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:105)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4939)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5633)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1092)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1984)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.UnknownHostException: zookeeper-1: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at org.apache.zookeeper.client.StaticHostProvider.<init>(StaticHostProvider.java:61)
at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:445)
at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:380)
at org.apache.solr.common.cloud.SolrZooKeeper.<init>(SolrZooKeeper.java:41)
at org.apache.solr.common.cloud.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:37)
at org.apache.solr.common.cloud.SolrZkClient.<init>(SolrZkClient.java:114)
... 22 more
INFO - 2017-08-25 17:10:25.370; org.apache.solr.servlet.SolrDispatchFilter; SolrDispatchFilter.init() done
ERROR - 2017-08-25 17:10:25.525; org.apache.solr.core.CoreContainer; CoreContainer was not shutdown prior to finalize(), indicates a bug -- POSSIBLE RESOURCE LEAK!!! instance=650576553
But in the other hand the catalina.out
INFO: Deploying web application archive /var/lib/tomcat7/webapps/solr.war
Aug 29, 2017 8:39:26 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Aug 29, 2017 8:39:26 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more Filters failed to start. Full details will be found in the appropriate container log file
Aug 29, 2017 8:39:26 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/solr] startup failed due to previous errors
Aug 29, 2017 8:39:26 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /var/lib/tomcat7/webapps/solr.war has finished in 3,447 ms
Aug 29, 2017 8:39:26 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8983"]
Aug 29, 2017 8:39:26 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8443"]
Aug 29, 2017 8:39:26 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Aug 29, 2017 8:39:26 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3579 ms
So maybe my problem here is I don't know how exactly restart the Solr component? Is really my first work with this software so apologies if my questions are totally noob :)
UPDATE:
I found new info in the logs. Now I think I'm closer to the root issue. However I don't understand the problem, some files missing?
Aug 29, 2017 9:12:11 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter SolrRequestFilter
java.lang.NoClassDefFoundError: Failed to initialize Apache Solr: Could not find necessary SLF4j logging jars. If using Jetty, the SLF4j logging jars need to go in the jetty lib/ext directory. For other containers, the corresponding directory should be used. For more information, see: http://wiki.apache.org/solr/SolrLogging
Thanks
Wow, apologies people. Maybe I shot the question very fast. The setup was completely misconfigured so basically to sum up, Zookeeper cluster was partially running because service was up and running but it was lack of service. So Solr was unable to connect to them. Once I was able to bring up Zookeeper to good status Solr could connect to it.
thanks anyway
I wanted to integrate postgresql in wordpress. To see postgres in xampp control panel I tried to do something. After that I could not be able to start apache. When I try to do that the following message is shown.
2:59:25 PM [Apache] Error: Apache shutdown unexpectedly.
2:59:25 PM [Apache] This may be due to a blocked port, missing dependencies,
2:59:25 PM [Apache] improper privileges, a crash, or a shutdown by another method.
2:59:25 PM [Apache] Press the Logs button to view error logs and check
2:59:25 PM [Apache] the Windows Event Viewer for more clues
2:59:25 PM [Apache] If you need more help, copy and post this
2:59:25 PM [Apache] entire log window on the forums
Can anyone help me in this purpose
My QuickFIX client is sending logout before login everyday. Is it possible not to have this logout message sent before login ... ?
Followings are the setting I am using now:
[default]
FileStorePath=/home/quickfix/crons/exe/quickfix/filestore
ConnectionType=initiator
SenderCompID=TN7_42
TargetCompID=EMS
SocketConnectHost=xxxxx
TimeZone=Asia/Tokyo
StartTime=07:50:00 Asia/Tokyo
EndTime=20:00:00 Asia/Tokyo
HeartBtInt=30
ReconnectInterval=5
CheckLatency=N
UseLocalTime=Y
[session]
BeginString=FIX.4.2
SocketConnectPort=12061
ResetOnLogon=Y
ResetOnLogout=Y
ResetOnDisconnect=Y
RefreshOnLogon=N
.. and following is the log message I get everyday:
Oct 11, 2011 7:56:00 AM quickfix.SessionSchedule <init>
INFO: [FIX.4.2:TN7_42->EMS] daily, 22:50:00-UTC - 11:00:00-UTC
<20111010-22:56:00.820, FIX.4.2:TN7_42->EMS, event> (Session FIX.4.2:TN7_42->EMS schedule is daily, 22:50:00-UTC - 11:00:00-UTC)
<20111010-22:56:00.821, FIX.4.2:TN7_42->EMS, event> (Session state is not current; resetting FIX.4.2:TN7_42->EMS)
<20111010-22:56:00.821, FIX.4.2:TN7_42->EMS, event> (Created session: FIX.4.2:TN7_42->EMS)
Oct 11, 2011 7:56:00 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketTcpNoDelay=true
Oct 11, 2011 7:56:00 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketSynchronousWrites=false
Oct 11, 2011 7:56:00 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketSynchronousWriteTimeout=30000
Oct 11, 2011 7:56:00 AM quickfix.mina.initiator.IoSessionInitiator <init>
INFO: [FIX.4.2:TN7_42->EMS] [/xxxxx:12061]
Oct 11, 2011 7:56:00 AM quickfix.mina.SessionConnector startSessionTimer
INFO: SessionTimer started
Oct 11, 2011 7:56:00 AM quickfix.mina.initiator.InitiatorIoHandler sessionCreated
INFO: MINA session created for FIX.4.2:TN7_42->EMS: local=/xxxxx:48477, class org.apache.mina.transport.socket.nio.SocketSessionImpl, remote=/xxxxx:12061
<20111010-22:56:01.860, FIX.4.2:TN7_42->EMS, outgoing> (8=FIX.4.2^A9=52^A35=5^A34=1^A49=TN7_42^A52=20111010-22:56:01.859^A56=EMS^A10=085^A)
Oct 11, 2011 7:56:01 AM quickfix.Session disconnect
INFO: [FIX.4.2:TN7_42->EMS] Disconnecting: Session reset
Oct 11, 2011 7:56:05 AM quickfix.mina.initiator.InitiatorIoHandler sessionCreated
INFO: MINA session created for FIX.4.2:TN7_42->EMS: local=/xxxxx:48478, class org.apache.mina.transport.socket.nio.SocketSessionImpl, remote=/xxxxx:12061
<20111010-22:56:06.844, FIX.4.2:TN7_42->EMS, outgoing> (8=FIX.4.2^A9=70^A35=A^A34=1^A49=TN7_42^A52=20111010-22:56:06.844^A56=EMS^A98=0^A108=30^A141=Y^A10=166^A)
<20111010-22:56:06.845, FIX.4.2:TN7_42->EMS, event> (Initiated logon request)
<20111010-22:56:06.847, FIX.4.2:TN7_42->EMS, incoming> (8=FIX.4.2^A9=179^A35=5^A49=EMS^A56=TN7_42^A34=1^A43=N^A52=20111010-22:56:06.846^A58=Catastropic Error: Incoming sequence number (1) is less than expected (2) without PossDupFlag being set. Logging out.^A10=226^A)
Oct 11, 2011 7:56:06 AM quickfix.Session disconnect
INFO: [FIX.4.2:TN7_42->EMS] Disconnecting: IO Session closed
<20111010-22:56:06.849, FIX.4.2:TN7_42->EMS, error> (quickfix.SessionException Logon state is not valid for message (MsgType=5))
<20111010-22:56:06.849, FIX.4.2:TN7_42->EMS, event> (Already disconnected: Verifying message failed: quickfix.SessionException: Logon state is not valid for message (MsgType=5))
<20111010-22:56:10.887, FIX.4.2:TN7_42->EMS, error> (java.net.ConnectException: java.net.ConnectException: Connection refused(Next retry in 5000 milliseconds))
<20111010-22:56:15.898, FIX.4.2:TN7_42->EMS, error> (java.net.ConnectException: java.net.ConnectException: Connection refused(Next retry in 5000 milliseconds))
You're being bitten by bug QFJ-357, which although it is against the Java project also seems to be an issue for the straight C++ version.
This has actually been fixed in trunk for C++ by the fix in revision 2269.
Incoming sequence number is less than expected
This says it all. The sequence number being sent in the FIX message to the acceptor has a different sequence number then expected from the acceptor, hence the forced logoff message. This is done primarily to keep both the acceptor and initiator in sync while sending and receiving messages.
There is a flag in the config which mentions to reset all sequence numbers during connection. Use that flag to get over this problem for now, but better stick with the original sequence numbers. In the reject message you should get the sequence number being expected by the acceptor. Parse the sequence number and then start the logon process again.
Try making your session end time a bit earlier, and confirm that you are actually sending a logout due to the end time being reached, and not just terminating your application without logging out.
There also have been one or two bugs in QuickFIX around this area which did not exist in 1.12, so you might try that older version and see if it works better for you.
I have 2 projects in eclipse. One of them runs fine and when added to Tomcat server, server can restart without any problems. However, the other project gets error when added
Server Tomcat v6.0 Server at localhost was unable to start within 45 seconds. If the
server requires more time, try increasing the timeout in the server editor.
I don't believe it's a timeout issue as I've changed time to no avail. Is there other settings/places I should be looking for errors?
This is console output for project that successfully starts vs one that doesn't
INFO: Initializing Coyote HTTP/1.1 on http-8080
24-Jun-2011 15:17:38 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 472 ms
24-Jun-2011 15:17:38 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
24-Jun-2011 15:17:38 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
24-Jun-2011 15:17:39 org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
24-Jun-2011 15:17:39 org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
24-Jun-2011 15:17:39 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
24-Jun-2011 15:17:39 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
24-Jun-2011 15:17:39 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/47 config=null
24-Jun-2011 15:17:39 org.apache.catalina.startup.Catalina start
INFO: Server startup in 1332 ms
One that fails:
INFO: Initializing Coyote HTTP/1.1 on http-8080
24-Jun-2011 15:18:34 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 425 ms
24-Jun-2011 15:18:34 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
24-Jun-2011 15:18:34 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Has anyone any idea on what could be stopping this from running?
Where did you change the time for the timeout?
In eclipse:
open your servers view
doubleclick on the server
check Timeouts (add a big number for Start)
May I know when you get this problem? If you get this while debugging, it means that it is waiting for your key press (either F5 or F6) to move to the next execution manually step by step. So you need not change the server's "timeout" property. Hope you get a little idea from this...
I got the same error message too. Sometimes it is just a library or a source folder which is out-of-synch. Please be sure that you clean your working directories, clean your projects and republish them. Sometimes it helps if you start the server first, then add the project and restart it. I was able to get this error message after that:
java.net.ConnectException: Connection refused. If this is the case, here you can find some suggestions to solve this problem: java.net.ConnectException: Connection refused. Hope that it helps.
Addition: A very useful method to find out from where exactly the error comes. http://www.vogella.com/blog/2010/02/16/tomcat-unable-to-start/ .
In my case, it occurred after I put "tcnaive-1.dll" in jre/bin.
Because I tried to remove the warning message when running the other one(tomcat6.0).
So, I deleted tcnative-1.dll for tomcat5.5-going-well even if keep warning message on tomcat6.0.