Bug 1095363
| Summary: | Dashbuilder hangs during start operation on WebSphere. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||
| Component: | Documentation | Assignee: | Vikram Goyal <vigoyal> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Radovan Synek <rsynek> | ||||
| Severity: | high | Docs Contact: | Vikram Goyal <vigoyal> | ||||
| Priority: | high | ||||||
| Version: | 6.0.2 | CC: | brms-docs, dgutierr, rrajasek | ||||
| Target Milestone: | CR1 | ||||||
| Target Release: | 6.0.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-06-02 06:44:38 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Radovan Synek
2014-05-07 14:36:36 UTC
It is indeed. So I added the missing instructions to the community READMEs: Github commits (master): https://github.com/droolsjbpm/jbpm-dashboard/commit/a1b7c5734c75f478cfa0c98cd1936dc8bba77461 https://github.com/droolsjbpm/dashboard-builder/commit/6e281090cebc74ead670751ee663ae68423bfaf0 Github commits (6.0.x): https://github.com/droolsjbpm/jbpm-dashboard/commit/f60828e058c36208a46aeb5c3778e62764f3f994 https://github.com/droolsjbpm/dashboard-builder/commit/b6dea565658d3be895967d2c7f88f9e7aabe2e9a Vikram, can you make sure the updated information in the community readme's makes into the product documentation? I have added the updated content for Dashbuilder [1] about the classloading strategy being checked. If this is part of the docs, it doesn't require a release notes mention so removing that flag. Moving to ON_QA. [1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html/IBM_Websphere_Installation_and_Configuration_Guide/Install_Dashbuilder.html @Radovan, I've installed the latest dashbuilder build provided by @Ryan, and I haven't found any deployment issues. Everything worked as expected. (See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1061149) As for your freezing issue, I've seen WAS freezing in the past, but that was caused by a lack of memory in the JVM. I fixed it by increasing the JVM max heap size: Servers>Server Types>WAS app servers - server1> Server Infrastructure>Process Definition>Java Virtual Machine (Set the JVM max heap size to a value greater than 1024 Mb). So, to sum up. 1.- I'm going to set this BZ as no reproducible. @Radovan, please try to install again the last Ryan's build. If you still have issues please let me know and I'll try to help you out. 2.- My suggested solution of changing the app's class loader settings was wrong as it caused this other BZ https://bugzilla.redhat.com/show_bug.cgi?id=1095391. So @Vikram, the product documentation changes done should be reverted. Class loader setting should NOT be changed for Dashbuilder. If done you can end up with an error while opening the login page: Error 500: java.lang.ClassCastException: org.jboss.dashboard.ui.components.SessionAwareLocaleManager_$$_javassist_74 incompatible with javassist.util.proxy.ProxyObject For business-central, those settings are required instead. I can confirm that I cannot reproduce the issue locally, so it's environment specific. David is right regarding the class loader settings (should be left in the default state). I have reverted the changes [1]. Moving to ON_QA. [1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html/IBM_Websphere_Installation_and_Configuration_Guide/Install_Dashbuilder.html Resolved by migration to more capable HW. |