Having a hard time getting Hibernate Search 4.0.0.Alpha2 to deploy. All I have configured is:

hibernate.search.default.directory_provider
hibernate.search.default.indexBase

This is on AS 7.0.1. Any ideas?

16:47:12,635 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.persistenceunit."oss.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."oss.war#primary": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1786)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.hibernate.search.SearchException: HSEARCH000103: Unable to initialize IndexManager oss.organization.Organization
at org.hibernate.search.util.logging.impl.Log_$logger.unableToInitializeIndexManager(Log_$logger.java:890)
at org.hibernate.search.indexes.impl.IndexManagerHolder.createDirectoryManager(IndexManagerHolder.java:200)
at org.hibernate.search.indexes.impl.IndexManagerHolder.buildEntityIndexBinding(IndexManagerHolder.java:113)
at org.hibernate.search.spi.SearchFactoryBuilder.initDocumentBuilders(SearchFactoryBuilder.java:405)
at org.hibernate.search.spi.SearchFactoryBuilder.buildNewSearchFactory(SearchFactoryBuilder.java:257)
at org.hibernate.search.spi.SearchFactoryBuilder.buildSearchFactory(SearchFactoryBuilder.java:146)
at org.hibernate.search.event.impl.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:125)
at org.hibernate.search.hcore.impl.HibernateSearchIntegrator.integrate(HibernateSearchIntegrator.java:82)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:294)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1722)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:884)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.jboss.as.jpa.service.PersistenceUnitService.createContainerEntityManagerFactory(PersistenceUnitService.java:143)
at org.jboss.as.jpa.service.PersistenceUnitService.start(PersistenceUnitService.java:77)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
... 4 more
Caused by: org.hibernate.search.SearchException: HSEARCH000082: Unable to start serialization layer
at org.hibernate.search.util.logging.impl.Log_$logger.unableToStartSerializationLayer(Log_$logger.java:995)
at org.hibernate.search.backend.BackendFactory.createSerializer(BackendFactory.java:133)
at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:94)
at org.hibernate.search.indexes.impl.IndexManagerHolder.createDirectoryManager(IndexManagerHolder.java:197)
... 19 more
Caused by: java.lang.NullPointerException
at org.hibernate.search.indexes.serialization.avro.impl.AvroSerializationProvider.parseSchema(AvroSerializationProvider.java:119)
at org.hibernate.search.indexes.serialization.avro.impl.AvroSerializationProvider.<init>(AvroSerializationProvider.java:77)
at org.hibernate.search.backend.BackendFactory.createSerializer(BackendFactory.java:124)
... 21 more

Hi,
are you using jax-rs too ? If so you should exclude the jackson libraries from being included in your webapp, they are conflicting with the ones being used by resteasy.

Not using jax-rs and the only jackson libs being included in the war are

jackson-core-asl-1.7.3.jar
jackson-mapper-asl-1.7.3.jar

which appear to be being pulled in from Hibernate Search.

Should I still exclude them?

I went ahead and excluded the jackson jars in my pom but I still get the same deployment error.

Here are the jars which are included in my project.war/WEB-INF/lib/

antlr-2.7.7.jar
avro-1.5.1.jar
backport-util-concurrent-3.1.jar
bcmail-jdk14-1.38.jar
bcmail-jdk14-138.jar
bcprov-jdk14-1.38.jar
bcprov-jdk14-138.jar
bctsp-jdk14-1.38.jar
classmate-0.5.4.jar
commons-codec-1.4.jar
commons-collections-3.2.1.jar
commons-io-1.4.jar
commons-lang-2.6.jar
commons-logging-1.1.1.jar
cssparser-0.9.5.jar
datecalc-common-1.2.0.jar
datecalc-jdk-1.2.0.jar
dom4j-1.6.1.jar
faces-vdl-documentation-1.jar
guava-r08.jar
hibernate-commons-annotations-4.0.0.CR2.jar
hibernate-core-4.0.0.CR2.jar
hibernate-jpa-2.0-api-1.0.1.Final.jar
hibernate-search-4.0.0.Alpha2.jar
hibernate-search-analyzers-4.0.0.Alpha2.jar
ical4j-1.0.jar
itext-2.1.7.jar
jandex-1.0.0.Beta7.jar
javassist-3.12.0.GA.jar
jboss-logging-3.0.0.GA.jar
jboss-logging-generator-1.0.0.Beta7.jar
jboss-logging-processor-1.0.0.Beta7.jar
joda-time-2.0.jar
jta-1.1.jar
log4j-1.2.12.jar
lucene-analyzers-3.3.0.jar
lucene-core-3.3.0.jar
lucene-grouping-3.3.0.jar
lucene-highlighter-3.3.0.jar
lucene-memory-3.3.0.jar
lucene-misc-3.3.0.jar
lucene-smartcn-3.3.0.jar
lucene-spatial-3.3.0.jar
lucene-spellchecker-3.3.0.jar
lucene-stempel-3.3.0.jar
oro-2.0.8.jar
paranamer-2.3.jar
picketlink-idm-api-1.5.0.Alpha02.jar
picketlink-idm-common-1.5.0.Alpha02.jar
picketlink-idm-core-1.5.0.Alpha02.jar
picketlink-idm-spi-1.5.0.Alpha02.jar
richfaces-components-api-4.1.0.20110805-M1.jar
richfaces-components-ui-4.1.0.20110805-M1.jar
richfaces-core-api-4.1.0.20110805-M1.jar
richfaces-core-impl-4.1.0.20110805-M1.jar
sac-1.3.jar
seam-catch-3.1.0.Beta2.jar
seam-catch-api-3.1.0.Beta2.jar
seam-config-xml-3.1.0.Beta2.jar
seam-faces-3.1.0.Beta2.jar
seam-faces-api-3.1.0.Beta2.jar
seam-international-3.1.0.Beta2.jar
seam-international-api-3.1.0.Beta2.jar
seam-mail-core-api-3.1.0-SNAPSHOT.jar
seam-mail-core-impl-3.1.0-SNAPSHOT.jar
seam-mail-velocity-impl-3.1.0-SNAPSHOT.jar
seam-persistence-3.1.0.Beta2.jar
seam-persistence-api-3.1.0.Beta2.jar
seam-security-3.1.0.Beta2.jar
seam-security-api-3.1.0.Beta2.jar
seam-servlet-3.1.0.Beta2.jar
seam-servlet-api-3.1.0.Beta2.jar
seam-solder-3.1.0-SNAPSHOT.jar
seam-solder-api-3.1.0-SNAPSHOT.jar
seam-solder-logging-3.1.0-SNAPSHOT.jar
seam-transaction-3.1.0.Beta2.jar
seam-transaction-api-3.1.0.Beta2.jar
slf4j-api-1.6.1.jar
snappy-java-1.0.1-rc3.jar
solr-analysis-extras-3.3.0.jar
solr-commons-csv-3.3.0.jar
solr-core-3.3.0.jar
solr-solrj-3.3.0.jar
velocity-1.6.4.jar
xml-apis-1.0.b2.jar

While experimenting with he Alpha-1 version I had a similar problem.

I've solved that doing this


I've just tried the indexing anywway. I don't know if it can cause problem in more complex scenarios.

Thanks for the suggestion, but unfortunately it still fails the same way.

I had the same problem in 4.0.0.beta1 and believe it is a bug. I guess it only happens on Windows.
In the class AvroSerializationProvider, method parseSchema the resulting InputStream "in" is null due to the line:

If you overwrite the class in your project and comment the line, it works.
Since the file to be read is in the jar, this line is superfluous.

Cheers

I am using windows as well.

Did you happen to file a JIRA on this?

Done - HSEARCH-921