Bug 878036
| Summary: | Errors in boot.log when stopping portal | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | vramik | ||||
| Component: | Portal | Assignee: | Default User <jbpapp-maint> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | vramik | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 | CC: | bdawidow, epp-bugs, hfnukal | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-16 08:55:25 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: |
|
||||||
I see that exo.kernel.container version 2.4.0-CR1 is used. This issue has been fixed in exo.kernel.container version 2.4.0-CR2 (JCR 1.15.0-CR1) (https://jira.exoplatform.org/browse/KER-217). Fix was introduced to GateIn with commit: 234b8f5, and is part of GateIn 3.5.0.Beta02. Marko Strukelj <mstrukel> made a comment on jira GTNPORTAL-2675 I think this issue can be closed with Fix Version set to 3.5.0.Beta02. Thomas Heute <theute> updated the status of jira GTNPORTAL-2675 to Resolved |
Created attachment 647767 [details] boot.log Description of problem: There are two errors in boot.log when stopping portal. (using ctrl+c) Version-Release number of selected component (if applicable): JPP6.0.ER02 How reproducible: Always Steps to Reproduce: 1. start portal (sh standlone.sh) 2. stop portal (ctrl+c) 3. see jboss-jpp-6.0/stanalone/log/boot.log