. . JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m . CLASSPATH=C:\PROGRA~1\Java\JDK18~1.0_1\lib\tools.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\lib\weblogic_sp.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\lib\weblogic.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\lib\webservices.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\oracle_common\modules\org.apache.ant_1.7.1/lib/ant-all.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\oracle_common\modules\net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\modules\features\oracle.wls.common.nodemanager_1.0.0.0.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\oracle_common\modules\com.oracle.cie.config-wls-online_8.0.0.0.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\common\derby\lib\derbyclient.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\common\derby\lib\derby.jar;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\lib\xqrl.jar . PATH=;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\native\win\x64;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\bin;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\oracle_common\modules\org.apache.ant_1.7.1\bin;C:\PROGRA~1\Java\JDK18~1.0_1\jre\bin;C:\PROGRA~1\Java\JDK18~1.0_1\bin;C:\Users\LINDHA~1\bin;C:\PROGRA~2\Git\mingw32\bin;C:\PROGRA~2\Git\usr\bin;C:\PROGRA~2\Git\usr\bin;C:\PROGRA~2\Git\mingw32\bin;C:\PROGRA~2\Git\usr\bin;C:\Users\LINDHA~1\bin;C:\PROGRA~1\COMMON~1\MICROS~1\WINDOW~1;C:\PROGRA~2\COMMON~1\MICROS~1\WINDOW~1;C:\camunda\tools\PYTHON~1;C:\camunda\tools\PYTHON~1\Scripts;C:\PROGRA~1\Python27\Lib\SITE-P~1\PyQt4;C:\PROGRA~2\Intel\ICLSCL~1;C:\PROGRA~1\Intel\ICLSCL~1;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WINDOW~1\v1.0;C:\PROGRA~1\Intel\INTEL(~2\DAL;C:\PROGRA~1\Intel\INTEL(~2\IPT;C:\PROGRA~2\Intel\INTEL(~1\DAL;C:\PROGRA~2\Intel\INTEL(~1\IPT;C:\PROGRA~1\Intel\WiFi\bin;C:\PROGRA~1\COMMON~1\Intel\WIRELE~1;C:\PROGRA~2\Intel\OPENCL~1\3.0\bin\x86;C:\PROGRA~2\Intel\OPENCL~1\3.0\bin\x64;C:\PROGRA~1\Lenovo\FINGER~1;C:\PROGRA~2\Lenovo\ACCESS~1;C:\PROGRA~2\COMMON~1\Lenovo;C:\PROGRA~2\git-cola\bin;C:\PROGRA~1\MICROS~4\110\Tools\Binn;C:\PROGRA~1\SlikSvn\bin;C:\camunda\tools\GnuPG\pub;C:\Users\LINDHA~1\AppData\Roaming\nvm;C:\PROGRA~1\nodejs;C:\Go\bin;C:\PROGRA~2\WIC4A1~1\Shared;C:\PROGRA~2\WI3CF2~1\10\WINDOW~1;C:\PROGRA~2\Git\cmd;C:\Users\LINDHA~1\CARGO~1\bin;C:\PROGRA~1\Java\JDK18~1.0_1\bin;C:\camunda\tools\APACHE~1.3\bin;C:\PROGRA~1\Python27;C:\PROGRA~2\Git\usr\bin;C:\PROGRA~1\Java\JDK18~1.0_1\jre\bin\server;C:\camunda\tools\checksum;C:\camunda\tools\hugo;C:\camunda\tools\ant\bin;C:\Users\LINDHA~1\AppData\Roaming\nvm;C:\PROGRA~1\nodejs;C:\PROGRA~1\R\R-32~1.0\bin;C:\camunda\tools\mdbook;C:\PROGRA~1\CMake\bin;C:\camunda\tools\ponylang\PONYC-~1.0-W\ponyc\bin;C:\PROGRA~2\Git\usr\bin\VENDOR~1;C:\PROGRA~2\Git\usr\bin\CORE_P~1;C:\Users\LINDHA~1\bin;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\native\win\x64\oci920_8 . *************************************************** * To start WebLogic Server, use a username and * * password assigned to an admin-level user. For * * server administration, use the WebLogic Server * * console at http:\\hostname:port\console * *************************************************** starting weblogic with Java version: java version "1.8.0_172" Java(TM) SE Runtime Environment (build 1.8.0_172-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode) Starting WLS with line: C:\PROGRA~1\Java\JDK18~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server\lib\weblogic.policy -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y -Xverify:none -Djava.endorsed.dirs=C:\PROGRA~1\Java\JDK18~1.0_1\jre\lib\endorsed;C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\oracle_common\modules\endorsed -da -Dwls.home=C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server -Dweblogic.home=C:\camunda\repos\CA6244~1\qa\WEBLOG~1\target\wls12120\wlserver\server weblogic.Server Listening for transport dt_socket at address: 8000 <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> Jan 23, 2019 6:15:34 PM org.camunda.bpm.container.impl.threading.ra.JcaExecutorServiceConnector start INFORMATION: camunda BPM executor service started. Jan 23, 2019 6:15:37 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-08020 Found camunda bpm platform configuration through META-INF/bpm-platform.xml at zip:C:/camunda/repos/camunda-bpm-platform-ee/qa/weblogic-runtime/target/domains/mydomain/servers/AdminServer/tmp/_WL_user/camunda-bpm-platform/beuyne/camunda-oracle-weblogic-service.jar!/META-INF/bpm-platform.xml Jan 23, 2019 6:15:37 PM org.springframework.transaction.jta.JtaTransactionManager checkUserTransactionAndTransactionManager INFORMATION: Using JTA UserTransaction: ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+localhost:17001+mydomain+t3+, XAResources={WSATGatewayRM_AdminServer_mydomain, camunda bpm DS_mydomain},NonXAResources={})] Jan 23, 2019 6:15:37 PM org.springframework.transaction.jta.JtaTransactionManager checkUserTransactionAndTransactionManager INFORMATION: Using JTA TransactionManager: ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+localhost:17001+mydomain+t3+, XAResources={WSATGatewayRM_AdminServer_mydomain, camunda bpm DS_mydomain},NonXAResources={})] Jan 23, 2019 6:15:37 PM org.springframework.transaction.jta.JtaTransactionManager initTransactionSynchronizationRegistry INFORMATION: Using JTA TransactionSynchronizationRegistry: ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+localhost:17001+mydomain+t3+, XAResources={WSATGatewayRM_AdminServer_mydomain, camunda bpm DS_mydomain},NonXAResources={})] Jan 23, 2019 6:15:37 PM org.springframework.transaction.jta.WebLogicJtaTransactionManager loadWebLogicTransactionClasses INFORMATION: Support for WebLogic transaction names available Jan 23, 2019 6:15:37 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-12003 Plugin 'ProcessApplicationEventListenerPlugin' activated on process engine 'default' Jan 23, 2019 6:15:37 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-12003 Plugin 'SpinProcessEnginePlugin' activated on process engine 'default' Jan 23, 2019 6:15:37 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: SPIN-01010 Discovered Spin data format provider: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormatProvider[name = application/json] Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: SPIN-01010 Discovered Spin data format provider: org.camunda.spin.impl.xml.dom.format.DomXmlDataFormatProvider[name = application/xml] Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: SPIN-01009 Discovered Spin data format: org.camunda.spin.impl.xml.dom.format.DomXmlDataFormat[name = application/xml] Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: SPIN-01009 Discovered Spin data format: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormat[name = application/json] Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-12003 Plugin 'ConnectProcessEnginePlugin' activated on process engine 'default' Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: CNCT-01004 Discovered provider for connector id 'http-connector' and class 'org.camunda.connect.httpclient.impl.HttpConnectorImpl': 'org.camunda.connect.httpclient.impl.HttpConnectorProviderImpl' Jan 23, 2019 6:15:38 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: CNCT-01004 Discovered provider for connector id 'soap-http-connector' and class 'org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorImpl': 'org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorProviderImpl' Jan 23, 2019 6:15:55 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-00008 History Cleanup Job reconfiguration failed on Process Engine Bootstrap. Possible concurrent execution with the JobExecutor: foobar Jan 23, 2019 6:15:55 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-00001 Process Engine default created. Jan 23, 2019 6:15:55 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-14014 Starting up the JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor]. Jan 23, 2019 6:15:55 PM org.camunda.bpm.container.impl.threading.ra.JcaExecutorServiceConnector stop INFORMATION: camunda BPM executor service stopped. <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> <23.01.2019 18:15 Uhr MEZ> Jan 23, 2019 6:15:56 PM org.jboss.arquillian.container.wls.WebLogicServerControl$StartupAdminServerCommand execute INFO: Started WebLogic Server. Jan 23, 2019 6:16:01 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient deploy INFO: Starting weblogic.Deployer to deploy the test artifact. <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> Jan 23, 2019 6:16:06 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient forkWebLogicDeployer INFO: weblogic.Deployer appears to have terminated successfully. Jan 23, 2019 6:16:08 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient deploy INFO: Starting weblogic.Deployer to deploy the test artifact. Jan 23, 2019 6:16:12 PM org.camunda.commons.logging.BaseLogger logInfo INFORMATION: ENGINE-08024 Found processes.xml file at zip:C:/camunda/repos/camunda-bpm-platform-ee/qa/weblogic-runtime/target/domains/mydomain/servers/AdminServer/tmp/_WL_user/pa1/bgm80e/war/WEB-INF/lib/_wl_cls_gen.jar!/META-INF/processes.xml <23.01.2019 18:16 Uhr MEZ> 'Deployment of process archive 'pa': Cannot deploy process archive 'pa' to default process: no such process engine exists: processEngine is null at org.camunda.bpm.container.impl.ContainerIntegrationLogger.exceptionWhilePerformingOperationStep(ContainerIntegrationLogger.java:315) at org.camunda.bpm.container.impl.spi.DeploymentOperation.execute(DeploymentOperation.java:135) at org.camunda.bpm.container.impl.jmx.MBeanServiceContainer.executeDeploymentOperation(MBeanServiceContainer.java:159) at org.camunda.bpm.container.impl.spi.DeploymentOperation$DeploymentOperationBuilder.execute(DeploymentOperation.java:215) at org.camunda.bpm.container.impl.RuntimeContainerDelegateImpl.deployProcessApplication(RuntimeContainerDelegateImpl.java:101) Truncated. see log file for complete stacktrace Caused By: org.camunda.bpm.engine.exception.NullValueException: Cannot deploy process archive 'pa' to default process: no such process engine exists: processEngine is null at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.camunda.bpm.engine.impl.util.EnsureUtil.generateException(EnsureUtil.java:380) Truncated. see log file for complete stacktrace > <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> Jan 23, 2019 6:16:13 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient forkWebLogicDeployer WARNING: weblogic.Deployer terminated abnormally with exit code 1 Jan 23, 2019 6:16:13 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient forkWebLogicDeployer INFO: The output of the weblogic.Deployer process was: weblogic.Deployer invoked with options: -adminurl t3://localhost:17001 -username weblogic -deploy -name pa1 -source C:\Users\LINDHA~1\AppData\Local\Temp\arquillian8688692482185173670pa1.war\pa1.war -targets AdminServer -upload -debug [WebLogicDeploymentManagerImpl.():119] : Constructing DeploymentManager for J2EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():162] : Connecting to admin server at localhost:17001, as user weblogic [ServerConnectionImpl.getEnvironment():295] : setting environment [ServerConnectionImpl.getEnvironment():298] : getting context using t3://localhost:17001 [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://localhost:17001/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3://localhost:17001/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5f683daf [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5f683daf [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@67080771 [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@67080771 [ServerConnectionImpl.initialize():178] : Connected to WLS domain: mydomain [ServerConnectionImpl.setRemote():489] : Running in remote mode [ServerConnectionImpl.init():168] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@5ace1ed4 [BasicOperation.dumpTmids():740] : Incoming tmids: [BasicOperation.dumpTmids():742] : {Target=AdminServer, WebLogicTargetType=server, Name=pa1}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: pa1 <23.01.2019 18:16 Uhr MEZ> [BasicOperation.dumpTmids():740] : Incoming tmids: [BasicOperation.dumpTmids():742] : {Target=AdminServer, WebLogicTargetType=server, Name=pa1}, targeted=true [BasicOperation.loadGeneralOptions():655] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: C:\Users\LINDHA~1\AppData\Local\Temp\Lindhauer\.\config\deployments\pa1 App config: C:\Users\LINDHA~1\AppData\Local\Temp\Lindhauer\.\config\deployments\pa1\plan Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=pa1,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=falsespecifiedTargetsOnly=false} [ServerConnectionImpl.upload():862] : Uploaded app to C:\camunda\repos\camunda-bpm-platform-ee\qa\weblogic-runtime\target\domains\mydomain\.\servers\AdminServer\upload\pa1 [BasicOperation.execute():472] : Initiating deploy operation for app, pa1, on targets: [BasicOperation.execute():474] : AdminServer Task 1 initiated: [Deployer:149026]deploy application pa1 on AdminServer. dumping Exception stack Task 1 failed: [Deployer:149026]deploy application pa1 on AdminServer. Target state: deploy failed on Server AdminServer javax.ejb.NoSuchEJBException: Singleton DefaultEjbProcessApplication(Application: pa1, EJBComponent: pa1.war) failed to initialize. at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:785) at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:645) at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:288) at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:284) at weblogic.ejb.container.deployer.EJBDeployer.initializeBeans(EJBDeployer.java:1227) at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:1124) at weblogic.ejb.container.deployer.EjbModuleExtension.start(EjbModuleExtension.java:168) at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:362) at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:586) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295) at weblogic.work.ExecuteThread.run(ExecuteThread.java:254) [ServerConnectionImpl.close():341] : Closing DM connection [ServerConnectionImpl.close():361] : Unregistered all listeners [ServerConnectionImpl.closeJMX():381] : Closed JMX connection [ServerConnectionImpl.closeJMX():393] : Closed Runtime JMX connection [ServerConnectionImpl.closeJMX():405] : Closed Edit JMX connection Jan 23, 2019 6:16:13 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient undeploy INFO: Starting weblogic.Deployer to undeploy the test artifact. <23.01.2019 18:16 Uhr MEZ> Jan 23, 2019 6:16:17 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient forkWebLogicDeployer INFO: weblogic.Deployer appears to have terminated successfully. Jan 23, 2019 6:16:17 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient undeploy INFO: Starting weblogic.Deployer to undeploy the test artifact. <23.01.2019 18:16 Uhr MEZ> Jan 23, 2019 6:16:21 PM org.jboss.arquillian.container.wls.WebLogicDeployerClient forkWebLogicDeployer INFO: weblogic.Deployer appears to have terminated successfully. Stopping Weblogic Server... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Connecting to t3://localhost:17001 with userid weblogic ... Successfully connected to Admin Server "AdminServer" that belongs to domain "mydomain". Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead. Shutting down the server AdminServer with force=false while connected to AdminServer ... <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> <23.01.2019 18:16 Uhr MEZ> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 WLST lost connection to the WebLogic Server that you were connected to, this may happen if the server was shutdown or partitioned. You will have to re-connect to the server once the server is available. Disconnected from weblogic server: AdminServer Jan 23, 2019 6:16:32 PM org.jboss.arquillian.container.wls.WebLogicServerControl$ShutdownAdminServerCommand execute INFO: Stopped WebLogic Server.