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!
Related
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?
We have an EJB application deployed on WebSphere 8.5, We are getting the following exception on console,
java.rmi.Exception:CORBA NO_RESPONSE 0x4942fb01 Maybe: nested exception is:
RESPONSE: Request 221370 timed out vmcid: IBM minor code: B01 Completed maybe
I can also see the root cause of exception as below:
caused by: org.omg.CORBA.NO_RESPONSE: Request timed out vmcid: B01 Completed maybe
at com.ibm.rmi.iiop.Connection.getCallStream(Connection.java:2493)
The effect of it is end user is unable to connect to the application.
Upon doing some analysis: I found out that main reason could be the connection pool settings.
So Can someone please help me on following:
possible root causes of above exception
possible way to fix this exception
Request timed out means that the EJB request timed out (default 180 seconds): https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/uorb_rsetg.html
This may have many causes, but in general, it's best to analyze the performance of the EJB backend service (e.g. garbage collection, long response times due to a database, etc.). Here is a place to start on investigating general WAS performance problems: https://publib.boulder.ibm.com/httpserv/cookbook/Recipes-WAS_Traditional_Recipes-General_WAS_Traditional_Performance_Problem.html
A key item is step 8 which gathers thread dumps and basic OS statistics during the problem. If you are stuck analyzing that data, you may open an IBM support request with that MustGather data.
I am working on a JDI project and connecting it to a tomcat server. If I have a bug in my code that causes my project to fail, while attached to the tomcat server, I will start to get com.sun.jdi.InternalException: Unexpected JDWP Error: 502 when invoking. The only way I have found to resolve this is restarting my JDI project and the tomcat server. Is there another method of resolving a JDWP code 502 programmatically? Based on the info in the below article, is it possible to terminate all previously invoked methods on a virtual machine after connecting to it?
According to this article JDPW Error List is defined as:
ALREADY_INVOKING 502 Previous invoke not complete.
I am using nexus 2.10 having recently upgraded from nexus 2.8. The reason I upgraded was because I was getting the following exception in my logs and thus the jar was not downloaded and Nexus 2.10 gives a few more details in the log regarding the broken pipe error.
So in my logs I get the following error (replaced i[p address with string host name).
2014-10-21 15:18:22,556+0100 INFO [qtp-855494215-66] anonymous org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "Central" [id=central]...
2014-10-21 15:23:59,440+0100 WARN [qtp-855494215-69] anonymous org.sonatype.nexus.content.internal.ContentServlet - org.eclipse.jetty.io.EofException, caused by: java.io.IOException: Broken pipe [client=host.name,ua=m2e/3.9.1.v20130814-1242/1.4.0.20130601-0317/1.6.0_45,req=GET http://xx.xx:8081/nexus/content/groups/public/org/springframework/spring-jdbc/4.1.1.RELEASE/spring-jdbc-4.1.1.RELEASE.jar]
2014-10-21 15:24:43,329+0100 WARN [qtp-855494215-67] anonymous org.sonatype.nexus.content.internal.ContentServlet - org.eclipse.jetty.io.EofException, caused by: java.io.IOException: Broken pipe [client=host.name,ua=m2e/3.9.1.v20130814-1242/1.4.0.20130601-0317/1.6.0_45,req=GET http://xx.xx5:8081/nexus/content/groups/public/org/springframework/spring-tx/4.1.1.RELEASE/spring-tx-4.1.1.RELEASE.jar]
2014-10-21 15:24:58,333+0100 WARN [qtp-855494215-66] anonymous org.sonatype.nexus.content.internal.ContentServlet - org.eclipse.jetty.io.EofException, caused by: java.io.IOException: Broken pipe [client=host.name,ua=m2e/3.9.1.v20130814-1242/1.4.0.20130601-0317/1.6.0_45,req=GET http://xx.xx:8081/nexus/content/groups/public/org/springframework/spring-context/4.1.1.RELEASE/spring-context-4.1.1.RELEASE-sources.jar]
Can anyone advise how to get past this error because currently some jars are not being downloaded. This does not apply to all jars for eg i just downloaded the nekohtml-0.9.5.jar no issues. Could this be possibly something to do with size? In my maven repository I just get a spring-test-4.1.1.RELEASE.jar.lastUpdated jar which is only 1kb in size.
Also I am running behind a firewall so have a proxy server configured in the nexus settings.
UPDATE:
this seems to be an issue only when done through eclipse. I was able to download sources and jars etc fine when I did it from the command line. I am using Eclipse keplar and the m2e plugin. Can anyone comment on this?
All advice appreciated
Thanks
The broken pipe exception occurs when nexus has received an http request from a client, prepares a response, but when it goes to write the response it finds the socket has already been closed.
Likely causes of this are:
An end user initiating a request and then canceling it (or
navigating away from a web page before it completes)
A client which does not properly close socket connections
A client's read timeout setting being reached
A reverse proxy in between nexus and the client (such as apache or
nginx) terminating the connection
Therefore you'll need to begin your investigation on the client side. If it turns out the client or reverse proxy's read timeout setting is triggering this then you'll need to investigate why nexus is responding slowly.
Your Nexus server is probably not able to reach some external repositories if it is running inside a network behind a proxy. You have to make sure you have the http proxy configured in Nexus and that any URL's of remote proxy repositories you want to access are allowed in the proxy.
You can use the "Browse Remote" feature to check if the access works. More details are in the Nexus book http://books.sonatype.com/nexus-book/reference/configxn-sect-customizing-server.html
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.