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.
Related
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.
I've been getting this error for weeks:
INFO: Closed connection [connectionId{localValue:820}] to 127.0.0.1:27017 because there was a socket exception raised by this connection.
Exception in thread "main" com.mongodb.MongoSocketReadException: Prematurely reached end of stream
at com.mongodb.connection.SocketStream.read(SocketStream.java:88)
at com.mongodb.connection.InternalStreamConnection.receiveResponseBuffers(InternalStreamConnection.java:492)
at com.mongodb.connection.InternalStreamConnection.receiveMessage(InternalStreamConnection.java:222)
at com.mongodb.connection.CommandHelper.receiveReply(CommandHelper.java:134)
at com.mongodb.connection.CommandHelper.receiveCommandResult(CommandHelper.java:121)
at com.mongodb.connection.CommandHelper.executeCommand(CommandHelper.java:32)
at com.mongodb.connection.InternalStreamConnectionInitializer.initializeConnectionDescription(InternalStreamConnectionInitializer.java:83)
at com.mongodb.connection.InternalStreamConnectionInitializer.initialize(InternalStreamConnectionInitializer.java:43)
at com.mongodb.connection.InternalStreamConnection.open(InternalStreamConnection.java:116)
at com.mongodb.connection.UsageTrackingInternalConnection.open(UsageTrackingInternalConnection.java:49)
at com.mongodb.connection.DefaultConnectionPool$PooledConnection.open(DefaultConnectionPool.java:384)
at com.mongodb.connection.DefaultConnectionPool.get(DefaultConnectionPool.java:101)
at com.mongodb.connection.DefaultConnectionPool.get(DefaultConnectionPool.java:87)
at com.mongodb.connection.DefaultServer.getConnection(DefaultServer.java:86)
at com.mongodb.binding.ClusterBinding$ClusterBindingConnectionSource.getConnection(ClusterBinding.java:86)
at com.mongodb.operation.OperationHelper.withConnectionSource(OperationHelper.java:239)
at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:214)
at com.mongodb.operation.FindOperation.execute(FindOperation.java:483)
at com.mongodb.operation.FindOperation.execute(FindOperation.java:80)
at com.mongodb.Mongo.execute(Mongo.java:818)
at com.mongodb.Mongo$2.execute(Mongo.java:805)
at com.mongodb.OperationIterable.iterator(OperationIterable.java:47)
at com.mongodb.OperationIterable.forEach(OperationIterable.java:70)
at com.mongodb.FindIterableImpl.forEach(FindIterableImpl.java:158)
I followed the directions given by the answer to this question but nothing has changed. I cannot seem to decipher the MongoDB Java documentation well enough to figure out what can be done (spent countless hours doing so) since Mongo is constantly changing its standards.
What other options can I change to fix this problem? A code example that includes the Mongo Client creation and the options builder from start to finish would be really helpful.
The jar is deployed on a Ubuntu Amazon EC2 instance.
we have a heavy load EJB application running on WebSphere 6.1. Lately, we've been having a lot of connection problems, Client application (standalone java app) gets the exception below and the request is not completed. The server is up and running, pings are fine and other clients can connect and send requests, so it is not a connection issue. We couldn't reproduce this problem on our test servers. Could anyone please help us figure out what's causing this problem? Is there some WebSphere config param we're missing?
EDIT We also found that during times when the server gives this exception we can not telnet on that port either. So it means our server-side ORB is not working properly?
Thank you.
Caused by: java.rmi.MarshalException: CORBA MARSHAL 1229125820 No; nested exception is:
org.omg.CORBA.MARSHAL: Error sending fragment vmcid: IBM minor code: 8BC completed: No
at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:197)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:67)
at com.xyz.facade.ejb.api.remote._FnoDataFacadeRemote_Stub.findDocs(_FnoDataFacadeRemote_Stub.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.xyz.app.util.locator.RemoteServiceInterceptor$1.call(RemoteServiceInterceptor.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.omg.CORBA.MARSHAL: Error sending fragment vmcid: IBM minor code: 8BC completed: No
at com.ibm.rmi.iiop.IIOPOutputStream.sendFragment(IIOPOutputStream.java:196)
at com.ibm.rmi.iiop.CDROutputStream.completeFragment(CDROutputStream.java:666)
at com.ibm.rmi.iiop.CDROutputStream.alignAndReserve(CDROutputStream.java:643)
at com.ibm.rmi.iiop.CDROutputStream.writeOctetArrayPiece(CDROutputStream.java:1100)
at com.ibm.rmi.iiop.CDROutputStream.write_octet_array(CDROutputStream.java:1076)
at com.ibm.rmi.iiop.CDROutputStream.writeRepositoryId(CDROutputStream.java:2445)
at com.ibm.rmi.iiop.CDROutputStream.writeString(CDROutputStream.java:2737)
at com.ibm.rmi.iiop.CDROutputStream.fast_write_value_internal(CDROutputStream.java:1580)
at com.ibm.rmi.iiop.CDROutputStream.fast_write_value(CDROutputStream.java:1623)
at com.ibm.rmi.iiop.CDROutputStream.fast_write_value(CDROutputStream.java:1554)
at com.ibm.rmi.io.IIOPOutputStream.writeValueType(IIOPOutputStream.java:1142)
at com.ibm.rmi.io.IIOPOutputStream.writeObjectField(IIOPOutputStream.java:1090)
at com.ibm.rmi.io.IIOPOutputStream.outputClassFields(IIOPOutputStream.java:1021)
at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:1005)
at com.ibm.rmi.io.IIOPOutputStream.writeSerializable(IIOPOutputStream.java:1050)
at com.ibm.rmi.io.IIOPOutputStream.simpleWriteObjectInternal(IIOPOutputStream.java:427)
at com.ibm.rmi.io.IIOPOutputStream.simpleWriteObjectLoop(IIOPOutputStream.java:455)
at com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:512)
at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:159)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1502)
at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1522)
at com.ibm.rmi.iiop.ClientRequestImpl.write_value(ClientRequestImpl.java:857)
... 11 more
Enable the ORBRas=all trace string and reproduce the problem. trace.log should contain the root cause of the exception. My guesses would be either a network I/O error or a product defect.
Would it be an option to use JacORB as client ORB?
I am getting a NullPointerException Exception while adding data from the online JSP page.
The error description is as follows:
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK:
javax.transaction.TransactionRolledbackException: ; nested exception is:
java.lang.NullPointerException vmcid: 0x0 minor code: 0 completed: No
I am using Websphere server "IBM WebSphere Application Server - ND, 6.0.2.35".
However, there was no problem when i was using "IBM WebSphere Application Server - ND, 6.0.2.17"
Is there any idea why this is happending.
Appreaciate all your efforts in this regard.
Thanks,
Manoja.
Likely, the NPE occurs in an EJB called when processing entered data.
In SystemOut/Err log, there likely will be complete stacktrace of the error. Find the nested NPE there and check its stacktrace for classes that belong to your application (i.e. no IBM or Java ones). That should give you some clue at least.