Bug 779845 (SOA-2205)
| Summary: | Classloading conflict between ModeShape and JBoss ESB on Lucene | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> | ||||
| Component: | JBossESB, Build Process, EDS | Assignee: | trev <tkirby> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.1.0.ER1 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.0 GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2205 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
Dev2 build with ModeShape deployed
|
|||||
| Last Closed: | 2011-01-06 08:02:35 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: |
|
||||||
Unlikely to be leaking of classes, more likely to be order of deployment. Please attach a log file showing the complete sequence. Kev Log attached, it shows successful start of ModeShape repo during server startup and then unsuccessful re-deployment. Attachment: Added: ms.log.gz I tried another experiment. I have started server first and then deployed modeshape-services.jar. The result was exactly same as with redeployment - so it seems that if ModeShape is (re-)deployed after JBoss ESB deployment then it fails. Looks like deployment ordering modeshape before jbossesb means that 3.0 is used, jbossesb before modeshape (i.e. redeployment) means that 2.0 is used. Are there other versions in the server, for example within seam? If so, which versions? Kev Our version of lucene only seems to exist to support a JCR message store, so changing may be straight forward. Kev I can't find any source reference to lucene so we may even be able to remove it. Kev Seam contains Lucene 2.4.1 Candidate for SOA 5.1.0 Link: Added: This issue is related to SOA-2206 If you want to use hsearch from seam 3.1.x it won't work with lucene 3. The seam version of 2.4.1 comes in via hibernate search going to remove the esb version as part of the SOA build Ken will create a new JIRA to handle Lucene - Seam incompatabilities esb/build.xml esb/post-patch/remove_unneeded_jar.xml Committed revision 7507 Writer: Added: Darrin Verified in ER6 |
project_key: SOA Start the server execute touch deploy/modeshape-services.jar/META-INF/jboss-beans.xml The repository is undeployed 14:58:52,256 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ModeShapeDS' from JNDI name 'java:ModeShapeDS' 14:58:52,316 INFO [JNDIManagedRepositories] Unbound ModeShape Repositories unbound from JNDI name "jcr/local" After few seconds new deployment is in progress which fails with 14:59:15,758 ERROR [AbstractKernelController] Error installing to Start: name=ModeShapeEngine state=Create java.lang.NoSuchFieldError: ANALYZED at org.modeshape.search.lucene.LuceneSearchEngine.<clinit>(LuceneSearchEngine.java:89) at org.modeshape.jcr.NodeTypeSchemata.<init>(NodeTypeSchemata.java:116) at org.modeshape.jcr.RepositoryNodeTypeManager.getRepositorySchemata(RepositoryNodeTypeManager.java:244) at org.modeshape.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:277) at org.modeshape.jcr.JcrRepository.<init>(JcrRepository.java:636) ModeShape brings Lucene version 3.0. JBoss ESB in jbossesb.esb has Lucene version 2.0 From the error message it is obvious that after re-deployment the old Lucene version is used instead of correct one. So there must be a classloading problem either in JBoss ESB or in ModeShape that causes leaking of the classes.