Menu
▾
▴
babeldoc-devel
|
From: Michael A. <mic...@ze...> - 2003-10-28 22:40:05
|
Hi,
Has anybody deployed the JMX Scanner recently? I've successfully gotten
it deployed, but when the received document is placed into the pipeline,
it causes a CNF Exception, and I can't make out why. Here is the stack
trace:
21:14:42,606 INFO [AsynchronousFeeder] Processing document...
21:14:42,933 INFO [SyncPipelineStageProcessor] PipelineStage name:
entry
21:14:42,994 ERROR [ResourceLoader] [ResourceLoader.getClass] Error when
trying to load: com.babeldoc.core.pipeline.stage.NullPipelineStage
java.lang.ClassNotFoundException: Unexpected error during load of:
com.babeldoc.core.pipeline.stage.NullPipelineStage,
msg=com/babeldoc/core/pipeline/PipelineStage
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:196)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.babeldoc.core.ResourceLoader.getClass(Unknown Source)
at
com.babeldoc.core.service.ServiceFactory.getServiceClass(Unknown Source)
at com.babeldoc.core.Type.getTypeClass(Unknown Source)
Is there some special config for the pipeline or the scanner that needs
to be included? Any other tips/hints/suspicions that will be useful?
Perhaps it's not JBoss at all, and I'm just configuring incorrectly.
I've got scanner/config.properties, feeder/config.properties and
pipeline/config.properties files in the babeldoc.sar directory, and the
scanner config is definitely making it into JBoss, because the scanner
that is being loaded comes from the scanner/config.properties.
This is a dir listing of the babledoc.sar directory:
bash-2.05b$ dir
babeldoc_babelfish.jar babeldoc-scanner.jar commons-collections.jar
commons-net.jar META-INF
babeldoc_conversion.jar babeldoc_soap.jar commons-dbcp.jar
commons-pool.jar pipeline
babeldoc_core.jar babeldoc_sql.jar commons-digester.jar
csv19.jar poi.jar
babeldoc_crypto.jar babeldoc_web.jar commons-discovery.jar
feeder scanner
babeldoc_gui.jar babeldoc_xslfo.jar commons-httpclient.jar
journal.log velocity.jar
babeldoc_init.jar commons-beanutils.jar commons-lang.jar
junit.jar
babeldoc_j2ee.jar commons-cli.jar commons-logging.jar
log4j.jar
It occured to me that it may be because JBoss is using it's own
classloader, but if the classloader can load com.babeldoc.core.Type,
then why can't it load com.babeldoc.core.pipeline.PipelineStage?
Cheers...
MikeA
|
|
From: Michael A. <mic...@ze...> - 2003-12-02 10:37:34
|
Hi, I've also committed changes to the jmx scanner, including a jar rule which creates a jboss service archive, which can simply be copied into the jboss deploy directory. Hot deploy works. Not sure the hot undeploy works quite as well. I seem to get stray documents being placed into the pipeline after restarting from a hot undeploy. Anyway, after running the jboss rule, copy your pipeline/, scanner/, resource/, feeder/ and journal/ directories into the jboss conf directory, and then copy the .sar file to the jboss deploy directory. If necessary, start jboss. You scanners should be active. It's still not as stable as I would like. I have added a property so that the babeldoc_home and babeldoc_user properties can be set in the jmx-console. I have defaulted them both to the conf directory, although I'm sure it's not quite right. Seems to work though. Also, I've only tested this with the SqlQuery, DirectoryScanner, JFreeReport and FileWriter stages/scanners. There may be classpath issues with other stages. This stuff is available (until I merge it into the HEAD) on the TEMP_MIKEA branch (cvs update babeldoc -r TEMP_MIKEA). PLEASE NOTE: this is development code, and should not yet be used in production systems. Have fun, bug reports readily accepted... MikeA |
|
From: Michael A. <mic...@ze...> - 2003-10-30 23:49:13
|
OK, I think I've found my problem. I was previously using JBoss 3.2.2 RC4, when receiving the error below. I've since installed the production release of 3.2.2, and it seems to work. There must have been an anomoly in the JBOss class loader that was causing it. I got the example directory scanner to load a file, and it was processesd through the example pipeline. So, on to other challenges ;-) MikeA On Tue, 2003-10-28 at 22:36, Michael Ansley wrote: > Hi, > > Has anybody deployed the JMX Scanner recently? I've successfully gotten > it deployed, but when the received document is placed into the pipeline, > it causes a CNF Exception, and I can't make out why. Here is the stack > trace: > 21:14:42,606 INFO [AsynchronousFeeder] Processing document... > 21:14:42,933 INFO [SyncPipelineStageProcessor] PipelineStage name: > entry > 21:14:42,994 ERROR [ResourceLoader] [ResourceLoader.getClass] Error when > trying to load: com.babeldoc.core.pipeline.stage.NullPipelineStage > java.lang.ClassNotFoundException: Unexpected error during load of: > com.babeldoc.core.pipeline.stage.NullPipelineStage, > msg=com/babeldoc/core/pipeline/PipelineStage > at > org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:196) > at java.lang.ClassLoader.loadClass(ClassLoader.java:235) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:141) > at com.babeldoc.core.ResourceLoader.getClass(Unknown Source) > at > com.babeldoc.core.service.ServiceFactory.getServiceClass(Unknown Source) > at com.babeldoc.core.Type.getTypeClass(Unknown Source) > > > Is there some special config for the pipeline or the scanner that needs > to be included? Any other tips/hints/suspicions that will be useful? > Perhaps it's not JBoss at all, and I'm just configuring incorrectly. > I've got scanner/config.properties, feeder/config.properties and > pipeline/config.properties files in the babeldoc.sar directory, and the > scanner config is definitely making it into JBoss, because the scanner > that is being loaded comes from the scanner/config.properties. > > This is a dir listing of the babledoc.sar directory: > bash-2.05b$ dir > babeldoc_babelfish.jar babeldoc-scanner.jar commons-collections.jar > commons-net.jar META-INF > babeldoc_conversion.jar babeldoc_soap.jar commons-dbcp.jar > commons-pool.jar pipeline > babeldoc_core.jar babeldoc_sql.jar commons-digester.jar > csv19.jar poi.jar > babeldoc_crypto.jar babeldoc_web.jar commons-discovery.jar > feeder scanner > babeldoc_gui.jar babeldoc_xslfo.jar commons-httpclient.jar > journal.log velocity.jar > babeldoc_init.jar commons-beanutils.jar commons-lang.jar > junit.jar > babeldoc_j2ee.jar commons-cli.jar commons-logging.jar > log4j.jar > > It occured to me that it may be because JBoss is using it's own > classloader, but if the classloader can load com.babeldoc.core.Type, > then why can't it load com.babeldoc.core.pipeline.PipelineStage? > > Cheers... > > > MikeA > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
Thanks for helping keep SourceForge clean.
X