Bug 891812
| Summary: | Jackrabbit repository configuration errors are not logged when deploying EE6 package on EAP 6 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Josh West <jowest> | ||||
| Component: | BRM (Guvnor) | Assignee: | Mark Proctor <mproctor> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.1 | ||||||
| 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: | 2025-02-10 03:27:13 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: |
|
||||||
Reassign to the guvnor team, now that I am working full time on planner. So these issues aren't forgotten. Is this not just a logging configuration issue? I don't believe so. Adding additional logging categories did not make the logging statement appear.
<logger category="org.jboss.seam">
<level name="WARN"/>
</logger>
<logger category="jboss.web.deployment">
<level name="WARN"/>
</logger>
<logger category="org.drools">
<level name="WARN"/>
</logger>
<logger category="org.apache">
<level name="WARN"/>
</logger>
I am guessing the issue is more along the lines in sufficient logging or a logging framework conflict.
Try to recreate the scenario and see for yourself. If the workaround is adding a logging category I'll gladly request that the suggested logging categories are added to the standard BRMS on EAP 6 documentation.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Created attachment 672290 [details] Byteman script to inject a stderr logging Description of problem: While misconfiguring the jackrabbit repository, exception details are not logged. Instead an ambiguous error is logged by the MSC service pointing to previous error that are not actually available. The error is published to the logging framework but does not show up. Version-Release number of selected component (if applicable): 5.3.1GA -> jboss-brms-manager-ee6.zip -> jboss-brms.war How reproducible: always Steps to Reproduce: 1. Deploy the EE6 jboss-brms.war on EAP 6 2. Put any invalid syntax in the repository.xml file 3. Start the EAP6 server 4. Open the server.log file Actual results: 23:32:53,943 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Initializing Mojarra 2.1.7-jbossorg-2 (20120412-0335) for context '/jboss-brms' 23:32:55,632 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Error listenerStart 23:32:55,632 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Context [/jboss-brms] startup failed due to previous errors 23:32:55,634 INFO [stdout] (MSC service thread 1-3) Removing all listeners... 23:32:55,635 INFO [stdout] (MSC service thread 1-3) Listeners removed... 23:32:55,642 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.web.deployment.default-host./jboss-brms: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./jboss-brms: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31] Expected results: Stacktrace detailing the configuration error. Additional info: To see the desired error use the attached byteman script.