The following is the error I'm getting in the server logs.
04:42:53.259 [41] [http-nio-8080-exec-8] ERROR org.springframework.web.socket.server.support.DefaultHandshakeHandler - Handshake failed due to invalid Upgrade header: null
I have gone through almost all questions out there regarding the similar issue but none seems to solve the issue. For me the issue is occurring intermittently, not every requests fails. There is also no proxy involved.
The application is deployed in kubernetes. Is there any other reason other that proxies that this issue can occur?
Related
We have Spring Boot applications which use Kubernetes and Istio. The application connects to AWS OpenSearch for CRUD functionality. Recently, the requests to OpenSearch started failing and we encountered this error repeatedly in the application logs:
method [POST], host [http://vpc-application-name.us-east-1.es.amazonaws.com], URI [/dummy/uri?param1=dummy1¶m2=dummy2], status line [HTTP/1.1 503 Service Unavailable] upstream connect error or disconnect/reset before headers. reset reason: connection failure
When we tried to hit this URL through Postman, it was working. We also tried to bash into the Kubernetes pods of this service and tried to curl this URL from there, but we were getting proper response. So it looks like an issue from the Java side. When we restarted the pods, the error was gone.
What could have caused this error?
How to identify or narrow down the root cause of this issue?
I am fairly new to Istio, Kubernetes and AWS, and I do not know what to expect. Any help is appreciated.
I downloaded bpm-installer-full-7.39.0.Final.zip from here https://download.jboss.org/jbpm/release/7.39.0.Final/
and trying to install it.
In contrast to 7.33 there's no ddl-scripts folder under /db path.
Then, when I made run
ant install.demo.noeclipse
ant start.demo.noeclipse
I kept seeing lots of similar traces:
2020-08-10 12:26:58,268 WARN [org.kie.server.services.impl.controller.DefaultRestControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at http://localhost:8080/jbpm-console/rest/controller/server/default-kieserver error Error while sending PUT request to http://localhost:8080/jbpm-console/rest/controller/server/default-kieserver response code 500
2020-08-10 12:27:08,284 INFO [org.kie.server.controller.websocket.client.WebSocketKieServerControllerImpl] (KieServer-ControllerConnect) Kie Server points to non Web Socket controller 'http://localhost:8080/jbpm-console/rest/controller', using default REST mechanism
2020-08-10 12:27:08,299 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /jbpm-console/rest/controller/server/default-kieserver: org.jboss.resteasy.spi.UnhandledException: java.lang.NoSuchMethodError: org.kie.server.api.marshalling.json.JSONMarshaller$2.verifyBaseTypeValidity(Lcom/fasterxml/jackson/databind/cfg/MapperConfig;Lcom/fasterxml/jackson/databind/JavaType;)Lcom/fasterxml/jackson/databind/jsontype/PolymorphicTypeValidator;
at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:82)
at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:346)
at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:193)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:456)
However, PUT http://localhost:8080/jbpm-console/rest/controller/server/default-kieserver works fine and returns 201 status. Client-side cannot handle the response? then why is server response 500 according to the logs?
And GUI (process management) says:
Attention
Execution Server Unavailable
There is currently no server connected.
Does anyone have a guess what I am doing wrong?
PS I installed jbpm v 7.33 on the same PC a couple of months ago without a headache.
Thanks.
I made it work(at least traces are gone and GUI is not throwing warnings).
I went into jbpm-installer-7.39.0.Final\wildfly-18.0.1.Final\modules\system\layers\base\com\fasterxml\jackson
and upgraded
jackson-annotations
jackson-core
jackson-databind
up to 2.10.4 version as exactly this version is used for jbpm .war packages.
I am wondering how they delivered such untested and raw version!
When I start up Solr, I get the following error
I/O exception caught when connecting to https://localhost:;
java.security.NoSuchAlgorithmException:
Error construct:sun.security.ssl.SSLContextImpl$DefaultSSLContext
Did anyone ever come across the same issue before?
What is causing this error and how can I fix it?
Try to connect using http://localhost. You are using https and it requires proper certificates and extra configuration. For localhost http is ok but is high recommend that you use https on production.
We are having an issue with a Seam application deployed to a Glassfish server, connecting to a MS SQL Server 2008 R1.
The glassfish server suddenly started logging the following error:
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN
|_ThreadID=30;_ThreadName=httpSSLWorkerThread-8080-32;_RequestID=a1eaa1df-59f2-4eab-8f1f-aeeaf0915002;
|ConnectionID:24617: batch completion: Encountered unexpected unknown token (0x30)|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.Reader
|_ThreadID=30;_ThreadName=httpSSLWorkerThread-8080-32;_RequestID=a1eaa1df-59f2-4eab-8f1f-aeeaf0915002;
|ConnectionID:24617 got unexpected value in TDS response at offset:12|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN
|_ThreadID=42;_ThreadName=httpSSLWorkerThread-8080-38;_RequestID=86e50fbc-cde0-4ffe-a83e-4cca657f8669;
|ConnectionID:24617: FetchBufferTokenHandler: Encountered unexpected unknown token (0x30)|#]
[#|2012-03-01T09:59:10.682+1300|SEVERE|sun-appserver2.1|com.microsoft.sqlserver.jdbc.internals.TDS.Reader
|_ThreadID=42;_ThreadName=httpSSLWorkerThread-8080-38;_RequestID=86e50fbc-cde0-4ffe-a83e-4cca657f8669;
|ConnectionID:24617 got unexpected value in TDS response at offset:12|#]
We had to stop this being logged through glassfish as it got to 30GB before we we're able to stop.
We have not been able to find any reason for what could have caused this.
Has anyone anywhere seen this before??!
I'm trying to deploy my java based appengine app through the eclipse plugin. I get an error at the very end of the process whichI pasted below. Any ideas what this could mean?
com.google.appengine.tools.admin.AdminException: Unable to update app: Error posting to URL: http://appengine.google.com/api/queue/update?app_id=ipoobeta&version=v1-6&
500 Internal Server Error
Server Error (500)
A server error has occurred.
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:62)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:271)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: Error posting to URL: http://appengine.google.com/api/queue/update?app_id=ipoobeta&version=v1-6&
500 Internal Server Error
Server Error (500)
A server error has occurred.
at com.google.appengine.tools.admin.ServerConnection.send(ServerConnection.java:143)
at com.google.appengine.tools.admin.ServerConnection.post(ServerConnection.java:81)
at com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java:522)
at com.google.appengine.tools.admin.AppVersionUpload.updateQueue(AppVersionUpload.java:255)
at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:134)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:56)
... 4 more
Since this question was written there have been many enhancements to the serving infrastructure of Google App Engine. Be sure you are using the High Replication Datastore (HRD). It is extremely unlikely that you will encounter this type of error and if you do it will be transient.