WebSphere 9-重新启动应用程序 [英] WebSphere 9 - Restart application

查看:274
本文介绍了WebSphere 9-重新启动应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

成功安装并使用我们的一个Web应用程序后,我尝试重新启动该应用程序(通过Integrated Solutions Console),但结果与我的预期不同. SystemOut.log文件立即充满异常.我只强调最相关的内容:

After successfully installing and using one of our web applications, I tried to restart the application (via Integrated Solutions Console), but the outcome was not what I was expecting. The SystemOut.log file was immediately flooded with exceptions. I'll just highlight the most relevants:

java.lang.ClassCastException: pt.sibs.epms.persistence.entity.EpmsDebugParameters incompatible with pt.sibs.epms.persistence.entity.EpmsDebugParameters
                at pt.sibs.epms.ecc.ApplicationManager.init(ApplicationManager.java:100) ~[classes/:na]

java.lang.IllegalArgumentException: Object: x.EccAudit[ eccAuditPK=x.EccAuditPK[ eventUsername=system, eventTimestamp=Thu Jul 14 17:20:04 BST 2016, eventModule=ECC ] ] is not a known Entity type.
                at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4229) ~[com.ibm.ws.jpa.eclipselink.jar:na]

CWOWB2001E: A POST_CONSTRUCT lifecycle inteceptor threw an exception: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void pt.sibs.epms.ecc.ThreadPoolManager.init() on pt.sibs.epms.ecc.ThreadPoolManager@7878f48b
                at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)

CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "init" on bean "BeanId(EpmsControlCenter-v2#EpmsControlCenter.war#NotificationEventGenerator, null)". Exception data: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void pt.sibs.epms.ecc.ThreadPoolManager.init() on pt.sibs.epms.ecc.ThreadPoolManager@7878f48b
                at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)

CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "fireScheduledEvent". Exception data: javax.ejb.NoSuchEJBException: An error occurred during initialization of singleton session bean EpmsControlCenter-v2#EpmsControlCenter.war#NotificationEventGenerator, resulting in the discarding of the singleton instance.; nested exception is: javax.ejb.EJBException: See nested exception; nested exception is: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void pt.sibs.epms.ecc.ThreadPoolManager.init() on pt.sibs.epms.ecc.ThreadPoolManager@7878f48b
                at com.ibm.ejs.container.util.ExceptionUtil.NoSuchEJBException(ExceptionUtil.java:540)

SRVE0293E: [Servlet Error]-[Faces Servlet]: java.lang.IllegalArgumentException: Unknown Entity bean class: class pt.sibs.epms.persistence.entity.EpmsOtherSystemParameters, please verify that this class has been marked with the @Entity annotation.
                at org.eclipse.persistence.internal.jpa.EntityManagerImpl.find(EntityManagerImpl.java:718)

该应用程序不再起作用,我必须重新启动服务器以使其再次起作用.不酷.

The application is no longer working and I have to restart the server to make it work again. Not cool.

有什么想法吗?

编辑#1

这似乎只有在重新部署之后才会发生.

This seems to happen only after redeploys.

推荐答案

由于CDI不支持动态更新方案,因此您需要在重新部署后重新启动应用程序.

You need to restart the application after the redeploy, as CDI does not support the dynamic update scenario.

这篇关于WebSphere 9-重新启动应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆