These error message can be found in the migration log when the tool reach the following step moving to version 7.9.0:
These error message can be found in the migration log when the tool reach the following step moving to version 7.8.0:
Let's suppose you have your Tomcat with Bonita up and running, and you have a third client application that needs to consume Bonita rest API.
You may have communication issues that you need to troubleshoot.
The goal of this post is to show how to log the access information in Tomcat.
Before getting into the details, just a few words about Bonita rest authentication...
Component: Linux or java process | Version: N/A
The failure occurs sporadically.
The two servers are active and the service is available.
All of a sudden, the load balancer fails to find an healthy bonita: Internal Server Error 500 is received in response to the HTTP requests.
These messages are generated in the log files:
Component: sap-jco3-callfunction | Version: 1.0.0Component: Bonita | Version: All | Edition: Subscription
We are using the bonita Connector in order to Call a SAP function (BAPI, RFC or ZBAPI) using SAPjco3. There are several connectors used with different tasks, which are part of several processes.
Component: Bonita Engine | Version: All
Oracle Database error - WARNING: bitronix.tm.recovery.Recoverer error running recovery on resource 'jdbc/bonitaDSXA', resource marked as failed (background recoverer will retry recovery) (error=XAER_RMERR)
I am having this error when starting Bonita, what can be happening :
Component: Engine | Version: N/A
I cannot deploy the bdm.zip in my portal and see this error in the bonita logs:
Component: PostGreSQL | Version: 9.3Component: Bonita | Version: 7.8.3
Downloading the configuration from Bonita engine database into the local disk using setup.sh pull is super slow: arround 60 seconds.
Usually, this action is taking less than 2 seconds.
Component: Migration Tool | Version: N/A
I am unable to use the migration tool on my PostgreSQL 10.x server.
There are these messages in the migration-2019-03-13-104435.log file:
Component: Migration Tool | Version: 2.39.0
There are these messages in the migration-2019-03-19-124431.log file: