| Summary: | Jackrabbit logs exceptions when connected to DB through XA DataSource on WAS 7 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||||||||||
| Component: | Configuration | Assignee: | Julian Coleman <jcoleman> | ||||||||||||
| Status: | ASSIGNED --- | QA Contact: | Jiri Locker <jlocker> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | high | ||||||||||||||
| Version: | 5.1.0 GA, BRMS 5.2.0.GA | CC: | atangrin, jlocker | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | future | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| URL: | http://jira.jboss.org/jira/browse/BRMS-566 | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: |
RHEL 5
IBM WebSphere Application Server - ND, 7.0.0.0
IBM JDK 6 SR8
Jackrabbit 2.1.0
|
|||||||||||||
| Last Closed: | Type: | Bug | |||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
Attaching a few resources: - SystemOut.log -- the server log - server1_6f5c6f5c_* -- more detailed exception dumps - repository.xml -- Jackrabit repository configuration - resources.xml -- should contain the DataSource configuration Attachment: Added: SystemOut.log Attachment: Added: server1_6f5c6f5c_11.03.10_07.45.26.2929125273516274881879.txt Attachment: Added: server1_6f5c6f5c_11.03.10_07.45.33.2074888330348122472464.txt Attachment: Added: repository.xml Attachment: Added: resources.xml Might be related to [JCR-2226|https://issues.apache.org/jira/browse/JCR-2226 JCR-2226] or [JCR-1349|https://issues.apache.org/jira/browse/JCR-1349]. Link: Added: This issue is related to JBQA-4169 After reconfiguring Jackrabbit repository.xml to not use a DataSource and to use JDBC directly (by providing PersistenceManager and FileSystem with driver, url, user and password parameters) ConectionRecoveryManager doesn't log this error anymore.
With this configuration a similar entry appears only once, when the application starts:
{noformat}
[3/15/11 15:16:50:350 EDT] 00000032 SystemOut O INFO 15-03 15:16:50,344 (RulesRepositoryConfigurator.java:getInstance:46) Creating an instance of the RulesRepositoryConfigurator.
[3/15/11 15:16:52:340 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,338 (DbUtility.java:logException:92) failed to close Statement
[3/15/11 15:16:52:342 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,340 (DbUtility.java:logException:94) Reason: Already closed
[3/15/11 15:16:52:344 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,342 (DbUtility.java:logException:95) State/Code: null/0
[3/15/11 15:16:52:346 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,344 (DbUtility.java:logException:92) failed to close Connection
[3/15/11 15:16:52:348 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,346 (DbUtility.java:logException:94) Reason: Connection is closed.
[3/15/11 15:16:52:350 EDT] 00000032 SystemOut O ERROR 15-03 15:16:52,348 (DbUtility.java:logException:95) State/Code: null/0
[3/15/11 15:16:55:606 EDT] 00000032 SystemOut O INFO 15-03 15:16:55,604 (LoggingHelper.java:info:51) Starting mailbox service
[3/15/11 15:16:55:608 EDT] 00000032 SystemOut O INFO 15-03 15:16:55,606 (LoggingHelper.java:info:51) mailbox service is up
[3/15/11 15:16:55:610 EDT] 00000032 SystemOut O Registering check-in listener
[3/15/11 15:16:55:616 EDT] 00000032 SystemOut O Check-in listener up
{noformat}
Again, overall repository functioning doesn't seem to be impaired.
Any ideas, Tiho? If not, I would have it documented and recommend to not use a DataSource.
|
securitylevel_name: Public The server log is crowded with Jackrabbit error messages: {noformat} [3/9/11 11:48:30:472 EST] 0000004b SystemOut O ERROR 09-03 11:48:30,471 (ConnectionRecoveryManager.java:logException:453) could not execute statement, reason: DSRA9110E: Statement is closed., state/code: null/0 {noformat} This exception is logged each time I perform a "write" operation such as checking in an asset or creating snapshot. However, changes seem to be saved successfully.