2016-06-27 92 views
0

我正在使用遷移工具作爲鏈接,將camunda從7.4(Wildfly)遷移到7.5(Wildfly 10):https://docs.jboss.org/author/display/CMTOOL/WildFly+8+to+10並正確基於此鏈接的一些配置:[在下面的評論中發佈,url_1]。將Camunda 7.4遷移到7.5(wildfiy 10)之後,camunda-welcome.war未加載

完成所有工作後,我可以啓動服務,沒有任何錯誤,但是當我打開URL - > [在下面的評論中,url_2]後,我得到了錯誤404,但是當我訪問[post in comment comment ,url_3],我可以正常訪問wildfly頁面。

我在server.log中登記了沒有記錄這個404,但我沒有比較,發現它沒有加載.war文件夾中的一個(camunda-welcome.war,路徑爲.server/wildfly-10.0.0.Final/standalone/deployments,請參閱以下日誌文​​件:你可以看到,/deployments/下的所有文件已經加載節選camunda-welcome.war文件夾提前

07:50:41,050 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.4) 
07:50:41,051 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = postgresql 
07:50:41,070 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 52) WFLYUT0014: Creating file handler for path '/camunda/jboss_7.5/deploy-package/./server/wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 
07:50:41,079 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. 
07:50:41,082 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting 
07:50:41,324 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 
07:50:41,389 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /camunda/jboss_7.5/deploy-package/./server/wildfly-10.0.0.Final/standalone/deployments 
07:50:41,423 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "camunda-example-invoice-7.5.1-ee.war" (runtime-name: "camunda-example-invoice-7.5.1-ee.war") 
07:50:41,438 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "camunda-webapp-ee-jboss-7.5.1-ee.war" (runtime-name: "camunda-webapp-ee-jboss-7.5.1-ee.war") 
07:50:41,449 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "camunda-h2-webapp-7.5.1-ee.war" (runtime-name: "camunda-h2-webapp-7.5.1-ee.war") 
07:50:41,459 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "camunda-engine-rest-7.5.1-ee.war" (runtime-name: "camunda-engine-rest-7.5.1-ee.war") 
07:50:41,620 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4) 
07:50:41,807 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final 
07:50:41,959 INFO [org.camunda.bpm.container.impl.jboss.deployment.processor.ProcessApplicationProcessor] (MSC service thread 1-1) Detected user-provided @ProcessApplication component with name 'org.camunda.bpm.example.invoice.InvoiceProcessApplication'. 
07:50:42,048 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ProcessEngine] 
07:50:42,048 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 
07:50:42,048 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/mydatabaseDS] 

感謝您的傢伙實物支持提前:)。

Sumana小姐W.

+0

url_1:https://docs.camunda.org/manual/latest/update/minor/74-to-75/jboss/ url_2:http:// localhost:8080/camunda-welcome/index.html url_3: http://10.1.1.159:8080/ – swongr18

回答

0

更新::

我可以從7.4版本遷移到7.5.0(7.5.2會給我之上,我做了,甚至遷移前的問題)。我已經打開問題Camunda隊..

仍然可以在這裏的任何意見。 :)

Sumana W.

0

添加更新..我沒有打開的情況下camunda和解決上述問題很簡單,你只是需要創建一個名爲「camunda-welcome.war.dodeploy」一個空文件在.server/wildfly-10.0.0.Final/standalone/deployments下,然後重新啓動服務..它將推camunda服務來滾動camunda-welcome.war.deployed ..現在該站點按預期加載:)。

相關問題