| Summary: | gwt-console-server component cannot talk to Guvnor if guvnor.connect.timeout and guvnor.read.timeout properties are not set | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> |
| Component: | jBPM Console | Assignee: | Kris Verlaenen <kverlaen> |
| Status: | VERIFIED --- | QA Contact: | Jiri Locker <jlocker> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | BRMS 5.3.0.GA | CC: | lpetrovi |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.3.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Locker
2011-12-14 16:11:48 UTC
Can you describe to me a usecase where an user would go into the jbpm.console.properties file (which has the defaults set) and actually remove them rather than changing to something that makes more sense to them? Thanks. Good point, but, as I mentioned in the 1. step to reproduce, in the product builds that we receive the properties file is missing these two properties. As a result the processes don't show up in the console (see bug 727440) and it really sucks to debug such issues when there's no exception in the log. I'm not sure if it is an issue that the two properties are missing, but I am certain that there are several issues in the GuvnorConnectionUtils code. That's why this bug was reported. Let me summarize: 1) if I load a property that I know to be later converted to number and I am using a default value in case it is not set in the properties file, then I need to use a default value that makes sense (e.i. not "", but something like "0" or "1000") 2) this is more important in case that the code doing the conversion is called inside a try-catch block which catches any Exception and only logs it's message (no stack trace). This is not QE-friendly and is worth fixing, I believe :) Fix committed to the jBPM 5.2.x branch (see also https://issues.jboss.org/browse/JBPM-3472). Fixed, many thanks! |