Exception in thread "main" javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Tag mismatch!
at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1533)
at sun.security.ssl.AppInputStream.available(AppInputStream.java:60)
at java.io.BufferedInputStream.available(BufferedInputStream.java:410)
at sun.net.www.MeteredStream.available(MeteredStream.java:170)
code countinues....
at java.io.FilterInputStream.close(FilterInputStream.java:181)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.close(HttpURLConnection.java:3527)
at org.gradle.wrapper.Download.downloadInternal(Download.java:77)
at org.gradle.wrapper.Download.download(Download.java:44)
at org.gradle.wrapper.Install$1.call(Install.java:61)
at org.gradle.wrapper.Install$1.call(Install.java:48)
I want to run auto generated code for the first time with android studio, to test that all is correctly set, but I can't, It shows the error in the given picture, I am new to this so please help
Related
We have been trying to start the claimcenter server from tomcat. The server is getting started even though it throws exception with the message "ClaimCenter unable to start" in the logs. Please find the log details below.
gw.pl.exception.GWLifecycleException: An exception was thrown while starting a component. Setting runlevel to NODAEMONS
Caused by: gw.pl.exception.GWLifecycleException:Messaging plugin does not implement MessageTransport interface error
Possible causes -
The xyzMessageTransport class failed to instantiate due to invalid parameters.
A class which is not implementation of MessageTransport inteface configured under
MessageTransport plugin. check messaging-config.xml.
Also - specify plugin name or attach whole log if possible.
I am trying to generate a report using Cucumber-jvm 6.11.0, and it works fine on my machine, when I put these properties in junit-platform.properties :
cucumber.publish.enabled=true
cucumber.plugin=pretty, json:build/reports/cucumber/report.json
cucumber.junit-platform.naming-strategy=long
However, when I run it on Jenkins, I get an ConnectException during the publication :
java.lang.RuntimeException: java.net.ConnectException: Connection timed out (Connection timed out)
at io.cucumber.core.plugin.MessageFormatter.writeMessage(MessageFormatter.java:36)
at io.cucumber.core.eventbus.AbstractEventPublisher.send(AbstractEventPublisher.java:51)
at io.cucumber.core.eventbus.AbstractEventBus.send(AbstractEventBus.java:12)
at io.cucumber.core.runtime.SynchronizedEventBus.send(SynchronizedEventBus.java:47)
at io.cucumber.core.runtime.CucumberExecutionContext.emitTestRunFinished(CucumberExecutionContext.java:102)
at io.cucumber.core.runtime.CucumberExecutionContext.finishTestRun(CucumberExecutionContext.java:74)
at io.cucumber.junit.platform.engine.CucumberEngineExecutionContext.finishTestRun(CucumberEngineExecutionContext.java:98)
at io.cucumber.junit.platform.engine.CucumberEngineDescriptor.after(CucumberEngineDescriptor.java:37)
at io.cucumber.junit.platform.engine.CucumberEngineDescriptor.after(CucumberEngineDescriptor.java:10)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:149)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:149)
at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
...
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1963)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1958)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1957)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1525)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1509)
at java.base/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:527)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:329)
at io.cucumber.core.plugin.UrlOutputStream.getResponseBody(UrlOutputStream.java:111)
at io.cucumber.core.plugin.UrlOutputStream.sendRequest(UrlOutputStream.java:83)
I tried with different combination of properties, and I see it starts happening the moment I enable the publishing, with only :
cucumber.publish.enabled=true
I am not finding the default behavior in the documentation, once we enable the publishing : where does it get published by default ? does it really try to upload it through http ? (I guess the proxy is not configured when running on Jenkins, while it is found when running on my machine, hence the different behavior)
How come I still get this error when I simply try to write the html or json report on disk ?
When you enable report publishing, it uploads test result to Cucumber cloud service and you get the unique URL that you (or anyone you share that link with) can use to access your report.
The report is self-destructive in 24 hours. You can find more details in official Cucumber blog.
When I try to debug an app and app execution stops on my breakpoint I can not see the current line or values. Debug window says Invalid method id. Tried cleaning, rebuilding and invalidate cache/restart.
I am trying to submit a code review request using CodeCollaborator client v7.2.7237 (server version is same too) but fails with the following error call stack –
com.smartbear.ccollab.datamodel.DataModelException: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:355)
at com.sun.proxy.$Proxy63.loadById(Unknown Source)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation.loadById(XmlRpcClientEngineImplementation.java:441)
at com.smartbear.ccollab.datamodel.Engine$DataObjectCache.loadObjectById(Engine.java:6691)
at com.smartbear.ccollab.datamodel.Engine.loadById(Engine.java:537)
at com.smartbear.ccollab.datamodel.Engine.loadEngineObjectById(Engine.java:564)
at com.smartbear.ccollab.datamodel.Engine.versionCreate(Engine.java:5913)
at com.smartbear.ccollab.datamodel.Scm.uploadScmVersion(Scm.java:629)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:448)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:392)
at com.smartbear.ccollab.datamodel.Scm.uploadChangelist(Scm.java:291)
at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.execute(AbstractAddChangelistCommand.java:139)
at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.execute(AbstractReviewCommand.java:125)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:345)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:419)
at com.smartbear.collaborator.Collaborator.execute(Collaborator.java:160)
at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:158)
at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:103)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at org.apache.xmlrpc.client.XmlRpcCommonsTransport.writeRequest(XmlRpcCommonsTransport.java:252)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:151)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:115)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientFactory$XmlRpcCommonsTransport2.sendRequest(XmlRpcClientFactory.java:75)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:256)
... 18 more
I have no problems accessing Perforce or CodeCollaborator from the machine when I get this error. I tried to submit using CodeCollaborator plugin in P4V (P4V/NTX64/2019.1/1797168) but got the same error message. I tried JRE 1.6, 1.7 but got the same error.
When I login to my CodeCollaborator account, I see that review request is being created but it is failing to add the source files to the review. My colleagues with the same CodeCollaborator, P4 versions are successfully able to submit the review requests. Checked this thread on CodeCollaborator forum who had reported similar issue but there was no solution to try. Any suggestions on how to troubleshoot ? Thanks.
I'm working on an Enterprise project with Java EE 5 and JSF 2.0 (Mojarra 2.0.3) on Weblogic 10.3.3
I don't have an error, but a very annoying warning in my console when going through my application.
Whenever I perform a redirect in JSF, I get a warning in my console of the following form:
Nov 7, 2011 5:36:46 PM com.sun.faces.application.resource.ResourceHandlerImpl logMissingResource
WARNING: JSF1064: Unable to find or serve resource, images/jquery-theme/ui-icons_cc0000_256x240.png.
Nov 7, 2011 5:36:46 PM com.sun.faces.application.resource.ResourceHandlerImpl logMissingResource
WARNING:
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:507)
at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:486)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
at weblogic.servlet.internal.ChunkOutput$2.checkForFlush(ChunkOutput.java:580)
at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:306)
at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:146)
at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:138)
at java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:275)
at com.sun.faces.application.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:277)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:310)
But in my application, the resource is displayed correctly. I don't know why this warning is being shown, when the image is loaded without a problem. I've read on an icefaces forum that it might be related to the <h:outputScript/> or the <h:outputStylesheet/> tags.
This is my usage of these tags:
<h:outputStylesheet name="jquery-theme/jquery-ui-1.8.16.custom.css" library="css"/>
and
<h:outputScript name="jquery-ui-1.8.16.custom.min.js" library="js"/>
These files are in the src/main/resources/css and src/main/resources/js folders respectively, and once again, they are correctly loaded and visible in the source code of the page. I just want to get rid of these warnings in my console.
java.net.SocketException: Software caused connection abort: socket write error
The connection was aborted while the resource was still busy downloading. That can happen when you for example navigated to a different page, or pressed Esc, or the closed the browser window while the browser is still busy downloading all resources.
I checked the Mojarra source code and see the following in ResourceHandlerImpl#handleResourceRequest() (lines 292-294 in Mojarra 2.1.3):
} catch (IOException ioe) {
send404(context, resourceName, libraryName, ioe, true);
}
So, the IOException on writing the response is been caught and forcibly handled as a 404. Personally, this should have been ignored or delegated to the servletcontainer by throws IOException, not forcibly be transformed into a HTTP 404 error.
I've reported this as issue 2245 the Mojarra guys. Until then, you can't do anything much against it, but it may be good to know that those warnings won't be logged when the javax.faces.PROJECT_STAGE is set to Production instead of Development. Instead, it will be logged as FINE.