首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >由于与其他正在进行的工作发生冲突,无法激活com.bea.wli.config.deployment.server.ServerDeploymentConflictException:会话

由于与其他正在进行的工作发生冲突,无法激活com.bea.wli.config.deployment.server.ServerDeploymentConflictException:会话
EN

Stack Overflow用户
提问于 2017-06-15 08:29:14
回答 1查看 725关注 0票数 0

当我试图为传输类型的业务服务更新OSB上的ejb时,我一直收到这个错误。

代码语言:javascript
复制
com.bea.wli.config.deployment.server.ServerDeploymentConflictException: Session could not be activated due to a conflict with other work in progress. Please retry the activation.
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.commitViaEditService(ServerDeploymentInitiator.java:603)
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.__serverCommit(ServerDeploymentInitiator.java:535)
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.access$200(ServerDeploymentInitiator.java:90)
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator$1.run(ServerDeploymentInitiator.java:382)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.serverCommit(ServerDeploymentInitiator.java:375)
    at com.bea.wli.config.deployment.server.ServerDeploymentInitiator.execute(ServerDeploymentInitiator.java:255)
    at com.bea.wli.config.session.impl.SessionManager.commitSessionUnlocked(SessionManager.java:314)
    at com.bea.wli.config.session.impl.SessionManager.commitSession(SessionManager.java:233)
    at com.bea.wli.config.session.impl.SessionManager.commitSession(SessionManager.java:190)
    at com.bea.wli.config.session.impl.SessionManager.commitSession(SessionManager.java:199)
    at com.bea.wli.config.mbeans.Session.commitSession(Session.java:94)
    at com.bea.wli.sb.management.configuration.SessionManagement.activateSession(SessionManagement.java:30)
    at com.bea.wli.sb.management.configuration.DelegatedSessionManagementMBeanImpl.activateSession(DelegatedSessionManagementMBeanImpl.java:32)
    at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:835)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:771)
    at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:351)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

正如堆栈跟踪提到的那样,我尝试过重新尝试激活:

由于与正在进行的其他工作发生冲突,无法启动会话。请重试激活。

同样的错误也会发生。

这意味着什么,我能做什么?

EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2017-06-15 08:29:14

似乎在总线服务器上出现了一个正在运行的更改。结束了从总线控制台的变更中心的改变,它起作用了。

变更中心位于总线控制台的左上角:

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/44562502

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档