Oracle db wso2 BPS 3.5.0的Bpel部署失敗

Question

我用ORACLE更改了H2的WSO2_CARBON_DB和BPSDB以及活動DB。 BPS的版本是3.5.0

我已發現此問題https://wso2.org/jira/browse/BPS-185，但已在此版本中修復。

現在，當我進行部署時，會出現以下錯誤：

[2015-11-05 14：35：11,692] WARN {Transaction}-beforeCompletion中發生意外的異常； 事務將回滾org.apache.openjpa.persistence.InvalidStateException：嘗試提交null javax.transaction.Transaction。 如果發生回滾，某些應用程序服務器會將事務設置為null。 位於org.apache.openjpa.kernel.BrokerImpl.setRollbackOnlyInternal（BrokerImpl.java:1654）位於org.apache.openjpa.kernel.BrokerImpl.setRollbackOnly（BrokerImpl.java:1640）位於org.apache.openjpa.kernel.DelegatingB （DelegatingBroker.java:981）在org.apache.openjpa.persistence.EntityManagerImpl.setRollbackOnly（EntityManagerImpl.java:631）在org.apache.openjpa.persistence.PersistenceExceptions $ 2.translate（PersistenceExceptions.java:77）在org.apache org.apache.openjpa.kernel.BrokerImpl.beforeCompletion（BrokerImpl.java:1994）的.openjpa.kernel.BrokerImpl.translateManagedCompletionException（BrokerImpl.java:2060）org.apache.geronimo.transaction.manager.TransactionImpl.beforelet .java：514），位於org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare（TransactionImpl.java:400），位於org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion（TransactionImpl.java:498）。 apache.geronimo.transaction.manager.TransactionImpl.commit（Transa org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit（TransactionManagerImpl.java:238）的org.apache.ode.store.jpa.DbConfStoreConnectionFactory.commitTransaction（DbConfStoreConnectionFactory.java:86）的ctionImpl.java:257） .wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl $ Callable.call（ProcessStoreImpl.java:739）在java.util.concurrent.FutureTask.run（FutureTask.java:262）在java.util.concurrent .ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1145）at java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:615）at java.lang.Thread.run（Thread.java:745）[2015-11-11 05 14：35：11,696]錯誤{org.wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl}-DbError java.lang.RuntimeException：java.lang.IllegalStateException：與組織中的當前線程無關的事務。 org.wso2.carbon.bpel.core.ode.integration.store.Pro上的apache.ode.store.jpa.DbConfStoreConnectionFactory.rollbackTransaction（DbConfStoreConnectionFactory.java:97） cessStoreImpl $ Callable.call（ProcessStoreImpl.java:745）在java.util.concurrent.FutureTask.run（FutureTask.java:262）在java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1145）在java.util java.lang.Thread.run（Thread.java:745）上的.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:615）原因：java.lang.IllegalStateException：與org.apache上的當前線程無關的事務。 org.apache.ode.store.jpa.DbConfStoreConnectionFactory.rollbackTransaction（DbConfStoreConnectionFactory.java:95）上的geronimo.transaction.manager.TransactionManagerImpl.rollback（TransactionManagerImpl.java:247）... 5個[2015-11-05 14： 35：11,697]錯誤{org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl}-BPEL包部署在ODE層失敗。 可能的原因：DbError org.apache.ode.bpel.iapi.ContextException：DbError位於org.wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl.exec（ProcessStoreImpl.java:775）位於org.wso2.carbon位於org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deployBPELPackageInODE（TenantProcessStoreImpl.java:703）的org.wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl.onBPELPackageDeployment（ProcessStoreImpl.java:332） org.apache上的.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy（TenantProcessStoreImpl.java:243）在org.apso.carbon.bpel.deployer.BPELDeployer.deploy（BPELDeployer.java:107）在org.apache org.apache.axis2.deployment.DeploymentEngine.doDeploy（DeploymentEngine.java:807）上的.axis2.deployment.repository.util.DeploymentFileData.deploy（DeploymentFileData.java:136）在org.apache.axis2.deployment.repository.util org.apache.axis2.deployment上的.WSInfoList.update（WSInfoList.java:144）.org.apache.axis2.deployme上的.WSInfoList.update（WSInfoList.java:144） org.apache.axis2.deployment.DeploymentEngine.loadServices（DeploymentEngine.java:135）上的nt.RepositoryListener.checkServices（RepositoryListener.java:254）在org.wso2.carbon.core.CarbonAxisConfigurator.deployServices（CarbonAxisConfigurator.java:567）上在org.wso2.carbon.core.org的org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore（CarbonCoreServiceComponent.java:235）的org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup（DeploymentServerStartupObserver.java:51）處org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged（StartupFinalizerServiceComponent.java:288）上的.internal.StartupFinalizerServiceComponent.completeInitialization（StartupFinalizerServiceComponent.java:185）在org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged .java：107），位於org.eclipse.osgi.framework.even，位於org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent（BundleContextImpl.java:861） 位於org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue.java:148）的tmgr.EventManager.dispatchEvent（EventManager.java:230）位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged（ServiceRegistry。 java：819）位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771）位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register（ServiceRegistrationImpl.java:130） org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:433）的.osgi.internal.serviceregistry.ServiceRegistry.registerService（ServiceRegistry.java:214）在org.eclipse.osgi.framework.internal org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent（ThrottlingAgentServiceComponent.java:123）的org.wso2.carbon.throttling.agent.internal.Thro的.core.BundleContextImpl.registerService（BundleContextImpl.java:451） 位於sun.reflect.NativeMethodAccessorImpl.invoke0（本地方法）處的ttlingAgentServiceComponent.activate（ThrottlingAgentServiceComponent.java:100）在sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.invoke：（DelegatingMethodAccessorImpl。 43）在org.eclipse.equinox.internal.ds.model.ServiceComponent.activate（ServiceComponent.java:260）在java.lang.reflect.Method.invoke（Method.java:606）在org.eclipse.equinox.internal org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build（Service.org.eclipse.equinox.internal.ds.InstanceProcess處的.ds.model.ServiceComponentProp.activate（ServiceComponentProp.java:146） org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents（InstanceProcess.java:197）的org.eclipse.equinox.internal.ds.Resolver.getEligible（Resolver.java:343的.buildComponent（InstanceProcess.java:620） ）在org.eclipse.equinox.internal.ds.SCRManager.serviceChanged（SCRManager.java:222） 在org.eclipse.osgi上的org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent（BundleContextImpl.java:861）上的org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged（FilteredServiceListener.java:107） org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue.java:148）上的.framework.eventmgr.EventManager.dispatchEvent（EventManager.java:230）在org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivilegeded （ServiceRegistry.java:819），位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771），位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register（ServiceRegistrationImpl.java:130） org.eclipse.osgi上的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService（ServiceRegistry.java:214）在org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:433）。 framework.internal.co org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon（CarbonServerManager.java:517）上的re.BundleContextImpl.registerService（BundleContextImpl.java:451）在org.wso2.carbon.core.init.CarbonServerManager.start（CarbonServerManager。 java：219）位於org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate（CarbonCoreServiceComponent.java:91）位於sun.reflect.NativeMethodAccessorImpl.invoke0（本地方法）位於sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java： 57）在org.eclipse.equinox.internal.ds.model.ServiceComponent.activate的java.lang.reflect.Method.invoke（Method.java:606）在sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43） （ServiceComponent.java:260）在org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate（ServiceComponentProp.java:146）在org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build（ServiceComponentProp.java ：345），位於org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent（Ins 位於org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents（InstanceProcess.java:197）的org.eclipse.equinox.internal.ds.Resolver.getEligible（Resolver.java:343）的tanceProcess.java:620） org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged（FilteredServiceListener.java:107）的.eclipse.equinox.internal.ds.SCRManager.serviceChanged（SCRManager.java:222）org.eclipse.osgi.framework.internal的。 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent（EventManager.java:230）上的.core.BundleContextImpl.dispatchEvent（BundleContextImpl.java:861）在org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue .java：148），位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771），位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged（ServiceRegistry.java:819）。 eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register（ServiceRegis trationImpl.java:130）位於org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService（ServiceRegistry.java:214）位於org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:433）在org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService（Activator.java:81）在org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet（Activator.java:60）在org.eclipse org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init（DelegationServlet.java:38）（位於org.apache.catalina.core）的.equinox.http.servlet.internal.ProxyServlet.init（ProxyServlet.java:40） org.apache.catalina.core.StandardWrapper.loadServlet（StandardWrapper.java:1197）的org.apache.catalina.core.StandardWrapper.load（StandardWrapper.java:1087）的.StandardWrapper.initServlet（StandardWrapper.java:1284） org.apache.catalina.core.StandardContext.startInternal（StandardContext.java:5550）上的org.apache.catalina.core.StandardContext.loadOnStartup（StandardContext.java:5262） 在org.apache.catalina.core.ContainerBase的org.apache.catalina.core.ContainerBase $ StartChild.call（ContainerBase.java:1575）的org.apache.catalina.util.LifecycleBase.start（LifecycleBase.java:150）處java.util.concurrent.FutureTask.run（FutureTask.java:262）處的$ StartChild.call（ContainerBase.java:1565）java.util。處的java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1145）處的$ StartChild.call（ContainerBase.java:1565） java.lang.Thread.run（Thread.java:745）上的current.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:615）原因：java.util.concurrent.ExecutionException：java.lang.RuntimeException：javax.transaction。 RollbackException：無法提交：事務標記為回滾的事務位於org.wso2.carbon的java.util.concurrent.FutureTask.get（FutureTask.java:188）處的java.util.concurrent.FutureTask.report（FutureTask.java:122） .bpel.core.ode.integration.store.ProcessStoreImpl.exec（ProcessStoreImpl.java:773）... 87更多原因：java.lang.RuntimeException：javax.transaction.RollbackException：無法提交： 在org.wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl $ Callable.call（ProcessStoreImpl。）上的org.apache.ode.store.jpa.DbConfStoreConnectionFactory.commitTransaction（DbConfStoreConnectionFactory.java:88）處標記為回滾的事務。 java：739）...另外4個原因：javax.transaction.RollbackException：無法提交：在org.apache.geronimo.transaction.manager.TransactionImpl.commit（TransactionImpl.java:271）處標記為回滾的事務。 org.apache.ode.store.jpa.DbConfStoreConnectionFactory.commitTransaction（DbConfStoreConnectionFactory.java:86）上的apache.geronimo.transaction.manager.TransactionManagerImpl.commit（TransactionManagerImpl.java:238）... 5個[2015-11-05 14：35：11,703]錯誤{org.wso2.carbon.bpel.deployer.BPELDeployer}-部署BPEL包時出錯：SBIC_1.0.0.zip org.apache.ode.bpel.iapi.ContextException：org.wso2.carbon上的DbError .bpel.core.ode.integration.store.ProcessStoreImpl.exec（ProcessStoreImpl.java:775）位於org.wso2.carbon.bpel.core.ode.integr org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deployBPELPackageInODE（TenantProcessStoreImpl.java:703）上的ation.store.ProcessStoreImpl.onBPELPackageDeployment（ProcessStoreImpl.java:332）在org.wso2.carbon.bpel處。 org.wso2.carbon.bpel.deployer.BPELDeployer.deploy（BPELDeployer.java:107）上的core.ode.integration.store.TenantProcessStoreImpl.deploy（TenantProcessStoreImpl.java:243），org.apache.axis2.deployment.repository。 org.apache.axis2.deployment.DeploymentEngine.doDeploy（DeploymentEngine.java:807）上的util.DeploymentFileData.deploy（DeploymentFileData.java:136）在org.apache.axis2.deployment.repository.util.WSInfoList.update（WSInfoList。 java：144）位於org.apache.axis2.deployment.RepositoryListener.update（RepositoryListener.java:377）位於org.apache.axis2.deployment.RepositoryListener.checkServices（RepositoryListener.java:254）位於org.apache.axis2.deployment org.wso2.carbon.core.CarbonAxisConfigurator.deployServices的.DeploymentEngine.loadServices（DeploymentEngine.java:135） （CarbonAxisConfigurator.java:567）位於org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup（DeploymentServerStartupObserver.java:51）位於org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore（CarbonCoreServiceComponent.java:235） org.eclipse.osgi.internal上的org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged（StartupFinalizerServiceComponent.java:288）上的org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization（StartupFinalizerServiceComponent.java:185） org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent（BundleContextImpl.java:861）處的serviceregistry.FilteredServiceListener.serviceChanged（FilteredServiceListener.java:107）在org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent（ org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue.java:148）的org.eclipse.osgi.internal.serviceregistry.ServiceRegis的EventManager.java:230） 在org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register（ServiceRegistrationImpl.register（ServiceRegistrationImpl.java）上的try.publishServiceEventPrivileged（ServiceRegistry.java:819）在org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771）在org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register（ServiceRegistrationImpl.java： 130）在org.eclipse的org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:433）的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService（ServiceRegistry.java:214） org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent（ThrottlingAgentServiceComponent.java:123）上的.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:451）在org.wso2.carbon.throttling上.agent.internal.ThrottlingAgentServiceComponent.activate（ThrottlingAgentServiceComponent.java:100）在sun.reflect.NativeMethodAccessorImpl.invoke0（本機方法）在sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl。 org.eclipse.equinox.internal.ds.model.ServiceComponent的java.lang.reflect.Method.invoke（Method.java:606）處的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）處的Java：57） org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate（ServiceComponent.java:260）org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build（ServiceComponentProp .java：345），位於org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent（InstanceProcess.java:620），位於org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents（InstanceProcess.java:197）。 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged（SCRManager.java:222）上的eclipse.equinox.internal.ds.Resolver.getEligible（Resolver.java:343）在org.eclipse.osgi.internal.serviceregistry。 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent（BundleContextImpl.j）上的FilteredServiceListener.serviceChanged（FilteredServiceListener.java:107） ava：861）在org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent（EventManager.java:230）在org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue.java:148）在org.eclipse org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771）上的.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged（ServiceRegistry.java:819）org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService（ServiceRegistry.java:214）上的.register（ServiceRegistrationImpl.java:130）org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java） ：433），位於org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon（CarbonServerManager.java:517），位於org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService（BundleContextImpl.java:451）。 wso2.carbon.core.init.CarbonServerManager.star 在org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate（CarbonCoreServiceComponent.java:91）處的t（CarbonServerManager.java:219）在sun.reflect.NativeMethodAccessorImpl.invoke0（本機方法）處在sun.reflect.NativeMethodAccessorImpl.invoke（ org.eclipse.equinox.internal.ds.model處的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）處的NativeMethodAccessorImpl.java:57）java.lang.reflect.Method.invoke（Method.java:606）處的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43） org.eclipse.equinox.internal.ds.model .ServiceComponent.activate（ServiceComponent.java:260）org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build處的.ServiceComponentProp.activate（ServiceComponentProp.java:146） （ServiceComponentProp.java:345）在org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent（InstanceProcess.java:620）在org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents（InstanceProcess.java:197） org.eclipse.equinox上的org.eclipse.equinox.internal.ds.Resolver.getEligible（Resolver.java:343）。 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged（FilteredServiceListener.java:107）處的internal.ds.SCRManager.serviceChanged（SCRManager.java:222）在org.eclipse.osgi.framework.internal.core.BundleContextImpl。 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent（EventManager.java:230）上的org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous（ListenerQueue.java:148）上的dispatchEvent（BundleContextImpl.java:861）在org.eclipse.osgi.internal上的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent（ServiceRegistry.java:771）上的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged（ServiceRegistry.java:819） org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService（.org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService處的.serviceregistry.ServiceRegistrationImpl.register（ServiceRegistrationImpl.java:130） （BundleConte org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService（Activator.java:81）處的xtImpl.java:433）org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet（Activator.java： 60）在org.eclipse.equinox.http.servlet.internal.ProxyServlet.init（ProxyServlet.java:40）在org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init（DelegationServlet.java:38）在org org.apache.catalina.core.StandardWrapper.loadServlet（StandardWrapper.java:1197）的.apache.catalina.core.StandardWrapper.initServlet（StandardWrapper.java:1284）org.apache.catalina.core.StandardWrapper.load（StandardWrapper） .java：1087），位於org.apache.catalina.core.StandardContext.startInternal（StandardContext.java:5550），位於org.apache.catalina.core.StandardContext.startInternal（StandardContext.java:5550），位於org.apache.catalina.core.StandardContext.loadOnStartup（StandardContext.java:5262）。 org.apache.catalina.core.ContainerBase $ StartChild.call（ContainerBase.java:1575）處的util.LifecycleBase.start（LifecycleBase.java:150）在org.apache.catalina.core.ContainerBase $ StartChild.call（C ontainerBase.java:1565）at java.util.concurrent.FutureTask.run（FutureTask.java:262）at java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1145）at java.util.concurrent.ThreadPoolExecutor $ Worker java.lang.Thread.run（Thread.java:745）上的.run（ThreadPoolExecutor.java:615）原因：java.util.concurrent.ExecutionException：java.lang.RuntimeException：javax.transaction.RollbackException：無法提交：標記為回滾的事務位於org.wso2.carbon.bpel.core的java.util.concurrent.FutureTask.get（FutureTask.java:188）處的java.util.concurrent.FutureTask.report（FutureTask.java:122）處。 ode.integration.store.ProcessStoreImpl.exec（ProcessStoreImpl.java:773）...還有87個原因由：java.lang.RuntimeException：javax.transaction.RollbackException：無法提交：事務標記為在org.apache.ode回滾org.wso2.carbon.bpel.core.ode.integration.store.ProcessStoreImpl $的.store.jpa.DbConfStoreConnectionFactory.commitTransaction（DbConfStoreConnectionFactory.java:88） Callable.call（ProcessStoreImpl.java:739）...還有4個原因：javax.transaction.RollbackException：無法提交：在org.apache.geronimo.transaction.manager.TransactionImpl.commit（TransactionImpl.java）上標記為回滾的事務：271），位於org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit（TransactionManagerImpl.java:238），位於org.apache.ode.store.jpa.DbConfStoreConnectionFactory.commitTransaction（DbConfStoreConnectionFactory.java:86）... 5和其他

Answer 1

確保在bps-datasource.xml配置中添加了<defaultAutoCommit>true</defaultAutoCommit>條目。