2015-01-21 83 views
5

我嘗試運行JBoss服務器(Wildfly 8.1.0 Final),它使用jbpm 6.1推出,並且無法運行它,運行時一直非常煩人,因爲安裝順利進行,沒有任何問題,也沒有對任何配置進行更改,所以我猜它應該正常部署。JBPM 6.1 Final與Jboss Wildfly - 無法啓動.WeldStartService

這是我遇到

2015-01-21 11:33:45,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".WeldStartService: Failed to start service 
     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] 
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25] 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25] 
     at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25] 
    Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions: 
    Exception 0 : 
    org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void org.kie.workbench.backend.AppSetup.assertPlayground() on [email protected] 
     at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:91) 
     at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:72) 
     at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:95) 
     at org.jboss.weld.injection.producer.BeanInjectionTarget.postConstruct(BeanInjectionTarget.java:63) 
     at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) 
     at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) 
     at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98) 
     at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78) 
     at org.kie.workbench.backend.AppSetup$Proxy$_$$_WeldClientProxy.toString(Unknown Source) 
     at org.uberfire.commons.services.cdi.StartupBeanExtension.runPostConstruct(StartupBeanExtension.java:83) 
     at org.uberfire.commons.services.cdi.StartupBeanExtension.afterDeploymentValidation(StartupBeanExtension.java:67) 
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
     at java.lang.reflect.Method.invoke(Method.java:483) 
     at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) 
     at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266) 
     at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125) 
     at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) 
     at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232) 
     at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169) 
     at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128) 
     at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102) 
     at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63) 
     at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35) 
     at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28) 
     at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:396) 
     at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:85) 
     at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) 
     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) 
     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) 
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
     at java.lang.Thread.run(Thread.java:745) 
    Caused by: java.lang.reflect.InvocationTargetException 
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
     at java.lang.reflect.Method.invoke(Method.java:483) 
     at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:89) 
     ... 33 more 
    Caused by: java.lang.NullPointerException 
     at org.uberfire.backend.server.organizationalunit.OrganizationalUnitServiceImpl.addRepository(OrganizationalUnitServiceImpl.java:153) 
     at org.uberfire.backend.server.organizationalunit.OrganizationalUnitServiceImpl$Proxy$_$$_WeldClientProxy.addRepository(Unknown Source) 
     at org.jbpm.console.ng.bd.backend.server.AdministrationServiceImpl.bootstrapRepository(AdministrationServiceImpl.java:157) 
     at org.jbpm.console.ng.bd.backend.server.AdministrationServiceImpl$Proxy$_$$_WeldClientProxy.bootstrapRepository(Unknown Source) 
     at org.kie.workbench.backend.AppSetup.assertPlayground(AppSetup.java:104) 
     ... 38 more 

     at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:37) 
     at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28) 
     at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:396) 
     at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:85) 
     at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) 
     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] 
     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] 
     ... 3 more 

終於在這個問題非常結束

JBAS014777: Services which failed to start:service jboss.deployment.unit."jbpm-console.war".WeldStartService 

,服務器將不無論什麼開始。

這個問題報告過很多例子herehere 但這些問題都沒有適當的解決方案。有關如何解決此問題的任何想法?

我的環境是:

  • 的Windows 8
  • 的Java 1.8
  • Eclipse的月神
  • 的Jboss Wildfly 8.1最終
  • 使用默認H2數據庫
+0

我得到了與Wildfly 8.2相同的錯誤信息... ... – Gatschet 2015-01-21 13:41:44

+1

@Gatschet - 我知道這非常煩人,jbpm社區並不是非常有幫助。他們的API非常複雜,加上糟糕的文檔只是一團糟。你能投票回答這個問題嗎?有人試圖回答這個問題嗎? – 2015-01-21 18:34:07

+2

是的,我一直在嘗試幾天遷移到野蠻。迄今沒有成功。文檔是一個笑話!錯誤消息隨機......這是絕望! – Gatschet 2015-01-22 09:00:48

回答

2

的錯誤你正在經歷的是因爲你試圖開始野蠻沒有連接到互聯網或間歇性連接。請記住,jBPM是一個社區項目,所以你們可以幫助使文檔更好。 嘗試刪除在wildfly/bin /目錄內創建的.niogit(隱藏)目錄,並嘗試再次啓動它。 如果您想在沒有演示存儲庫的情況下啓動,因爲您處於脫機狀態或無法聯機,您可以通過設置文檔中詳細描述的標誌來實現此目的。條款:3.6.1。 Playgrounds -Dorg.kie.demo = false

+0

- 感謝您的回覆,但問題是我已連接到互聯網,但它是通過代理,我在build.xml中設置了'-Dorg.kie.demo = false',並且我運行了螞蟻目標jboss.start,但仍然無法啓動jbpm控制檯。 – 2015-01-23 14:14:10

+0

我將嘗試刪除隱藏的文件夾並查看是否有效。 – 2015-01-23 14:14:40

+0

我的意思是'start.jboss' – 2015-01-23 14:31:45

相關問題