0

hello,   We have recently upgraded our test branch of the project from  Mendix Studio Pro version from 8.18.14 directly t 9.15.0  and then checked it in and we the build success on the server so we went with implementing the DocuSign connector on the same, but our changes are not getting reflected so we uninstalled all the modules related to DocuSign and checked  in the code again but we are still getting the DocuSign related error as mentioned in the log below . Please can you give us some pointers how we can overcome the issue   INFO:                                ##        .                          ## ## ##       ==                        ## ## ## ##      ===                    /""""""""""""""""\___/ ===               ~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ /  ===- ~~~                    \______ o          __/                      \    \        __/                       \____\______/      __  __        _  _     _____             _     |  \/  |      | || |   |  __ \           | |     | \  / |_  __ | || |_  | |  | | ___   ___| | _____ _ __     | |\/| \ \/ / |__   _| | |  | |/ _ \ / __| |/ / _ \ '__|     | |  | |>  <     | |   | |__| | (_) | (__|   <  __/ |     |_|  |_/_/\_\    |_|   |_____/ \___/ \___|_|\_\___|_|                                 digitalecosystems@mendix.com      INFO: Executing export_industrial_edge_config_variable... INFO: Adding uid to /etc/passwd INFO: Mendix Cloud Foundry Buildpack v4.30.2 [362b35b] starting... INFO: Fixing up permissions of directory 'model' with mode 700 INFO: Fixing up permissions of directory 'web' with mode 755 INFO: Fixing up permissions of directory 'data' with mode 700 INFO: Using external file store configured by user-defined settings. See https://github.com/mendix/cf-mendix-buildpack for file store configuration details. INFO: MENDIX-LOGGING-HEARTBEAT: Heartbeat number 1 INFO: Using Java version: INFO: openjdk version "11.0.15" 2022-04-19 INFO: OpenJDK Runtime Environment Temurin-11.0.15+10 (build 11.0.15+10) INFO: OpenJDK 64-Bit Server VM Temurin-11.0.15+10 (build 11.0.15+10, mixed mode) INFO: The buildpack is starting the runtime... INFO: Trying to start the MxRuntime... 2022-08-10 08:22:29.521 INFO - M2EE: Added admin request handler '/prometheus' with servlet class 'com.mendix.metrics.prometheus.PrometheusServlet' 2022-08-10 08:22:29.787 INFO - Logging: Logging to file: /opt/mendix/build/log/out.log, max size: 1099511627776KiB, max rotation: 10 INFO - M2EE: Added admin request handler '/prometheus' with servlet class 'com.mendix.metrics.prometheus.PrometheusServlet' INFO - Logging: Logging to file: /opt/mendix/build/log/out.log, max size: 1099511627776KiB, max rotation: 10 INFO - M2EE: Initializing runtime... INFO - Core: Mendix Runtime 9.15.0.47426 (build 9.15.0.47426). Copyright © 2003-2022 Mendix bv. All rights reserved. INFO - M2EE: Initialized runtime. INFO - M2EE: Creating Runtime server... INFO - M2EE: Setting MaxFormContentSize for Runtime Server to 10485760 INFO - M2EE: Runtime server started. INFO - Configuration: Updating configuration... INFO - Configuration: updateConfiguration: ApplicationRootUrl=http://test-pcm.pall.com, com.mendix.storage.PerformDeleteFromStorage=false, LogMinDurationQuery=10000, ConnectionPoolingTimeBetweenEvictionRunsMillis=10000, ConnectionPoolingNumTestsPerEvictionRun=50, com.mendix.core.StorageService=com.mendix.storage.s3, ConnectionPoolingSoftMinEvictableIdleTimeMillis=10000 INFO - Configuration: Configuration updated. INFO - Metrics: Started metrics on Micrometer INFO - Core: Initializing InternalCore and Modules... WARNING - ConnectionBus: Database connections: 0 active, 0 idle. ERROR - ConnectionBus: Opening JDBC connection to np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com:3306/pcm failed with SQLState: 08000 Error code: -1 Message: "Could not connect to address=(host=np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com)(port=3306)(type=master) : (conn=524935) could not load system variables", retrying...(1/4) WARNING - ConnectionBus: Database connections: 0 active, 0 idle. ERROR - ConnectionBus: Opening JDBC connection to np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com:3306/pcm failed with SQLState: 08000 Error code: -1 Message: "Could not connect to address=(host=np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com)(port=3306)(type=master) : (conn=524936) could not load system variables", retrying...(2/4) WARNING - ConnectionBus: Database connections: 0 active, 0 idle. ERROR - ConnectionBus: Opening JDBC connection to np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com:3306/pcm failed with SQLState: 08000 Error code: -1 Message: "Could not connect to address=(host=np-test-ssd-mendix-aurora-1-cluster.cluster-cesikezci6lm.us-east-1.rds.amazonaws.com)(port=3306)(type=master) : (conn=524937) could not load system variables", retrying...(3/4) INFO - Core: Initialized InternalCore and Modules. INFO - Core: Initializing ConnectionBus... INFO - Core: Initialized ConnectionBus. ERROR - M2EE: An error occurred while initializing the Runtime: Could not find child entity with id 4ad2a034-e90e-4cc5-957c-6142dee41870 for association DocusignConnector.Documents_Template ERROR - M2EE: com.mendix.m2ee.api.AdminException: An error occurred while initializing the Runtime: Could not find child entity with id 4ad2a034-e90e-4cc5-957c-6142dee41870 for association DocusignConnector.Documents_Template     at com.mendix.basis.impl.MxRuntimeImplBase.start(MxRuntimeImplBase.java:268) Caused by: com.mendix.connectionbus.ConnectionBusRuntimeException: Could not find child entity with id 4ad2a034-e90e-4cc5-957c-6142dee41870 for association DocusignConnector.Documents_Template     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.handleAssociationResult$1(DatabaseMappingReader.scala:270)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.$anonfun$fillAssociations$5(DatabaseMappingReader.scala:309)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.$anonfun$fillAssociations$5$adapted(DatabaseMappingReader.scala:309)     at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)     at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)     at com.mendix.connectionbus.util.ResultSetIterator.foreach(ResultSetIterator.scala:5)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.$anonfun$fillAssociations$4(DatabaseMappingReader.scala:309)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.$anonfun$fillAssociations$4$adapted(DatabaseMappingReader.scala:309)     at scala.util.Using$.resource(Using.scala:261)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.fillAssociations(DatabaseMappingReader.scala:309)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader.fillModel(DatabaseMappingReader.scala:64)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader$.$anonfun$getDatabaseMappingModel$4(DatabaseMappingReader.scala:34)     at scala.util.Using$.resource(Using.scala:261)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader$.$anonfun$getDatabaseMappingModel$3(DatabaseMappingReader.scala:34)     at scala.Option.map(Option.scala:242)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader$.getDatabaseMappingModel(DatabaseMappingReader.scala:32)     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader$.$anonfun$getDatabaseMappingModel$1(DatabaseMappingReader.scala:19)     at scala.util.Using$.resource(Using.scala:261) ERROR: Executing start did not succeed: result: 1, message: class com.mendix.m2ee.api.AdminException occurred while executing an admin action request. See logging output for details., caused by: class com.mendix.connectionbus.ConnectionBusRuntimeException occurred while executing an admin action request. See logging output for details.     at com.mendix.connectionbus.modelsynchronization.analysis.mappingreaders.DatabaseMappingReader$.getDatabaseMappingModel(DatabaseMappingReader.scala:19)     at com.mendix.connectionbus.ConnectionBusImpl.fillMappingCache(ConnectionBusImpl.scala:397)     at com.mendix.connectionbus.ConnectionBusImpl.getInitialDatabaseCommands(ConnectionBusImpl.scala:392)     at com.mendix.basis.impl.MxRuntimeImplBase.collectDdlCommands(MxRuntimeImplBase.java:372) ERROR: Starting application failed: Application start failed     at com.mendix.basis.impl.MxRuntimeImplBase.doSynchronization(MxRuntimeImplBase.java:286)     at com.mendix.basis.impl.MxRuntimeImplBase.startConnectionBus(MxRuntimeImplBase.java:275)     at com.mendix.basis.impl.MxRuntimeImplBase.start(MxRuntimeImplBase.java:247)     at com.mendix.m2ee.appcontainer.actions.StartAction.startRuntime(StartAction.scala:30) INFO: Waiting for the application to shutdown...     at com.mendix.m2ee.appcontainer.actions.StartAction.execute(StartAction.scala:17)     at com.mendix.m2ee.appcontainer.server.handler.HttpAdminHandlerBase.service(HttpAdminHandlerBase.java:128)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508)     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1378)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:463)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1300)     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)     at org.eclipse.jetty.server.Server.handle(Server.java:562)     at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)     at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)     at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:319)     at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)     at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:412)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:381)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:268)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:138)     at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:407)     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:894)     at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1038)     at java.base/java.lang.Thread.run(Unknown Source) INFO - Core: Mendix Runtime is shutting down now... INFO - Core: Mendix Runtime is now shut down. INFO: The application has been stopped successfully.    

asked 2022-08-11

1 answers