Issuing a command like "/usr/local/dspace-1.7.1/bin/dspace packager --help"
while in the /usr/local/dspace-1.7.1/bin directory produces the following
(non-fatal) error:
java.lang.IllegalArgumentException: Resource path
[/usr/local/dspace-1.7.1/bin/dspace] does not denote a directory
at
org.springframework.core.io.support.PathMatchingResourcePatternResolver.retrieveMatchingFiles(PathMatchingResourcePatternResolver.java:563)
at
org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindMatchingFileSystemResources(PathMatchingResourcePatternResolver.java:543)
at
org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindPathMatchingFileResources(PathMatchingResourcePatternResolver.java:526)
at
org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:342)
at
org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:263)
at
org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:375)
at
org.dspace.servicemanager.config.DSpaceConfigurationService.<init>(DSpaceConfigurationService.java:60)
at
org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:145)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:51)
Issuing the same command in some other directory, e.g,. one level up, in the
/usr/local/dspace-1.7.1 directory, does not produce the error.
I've tracked down through the stack trace as far as line 375 in
DSpaceConfigurationService and it appears to be calling the
org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources()
method with the argument "classpath*:dspace/config-*.cfg". The only thing I
can figure out is that, when issuing the command in the bin/ directory, there
is a match for "dspace" (i.e. the bin/dspace file) that is not a directory and
hence doesn't make sense if it's trying to track down resources of the form
"dspace/config-*.cfg". Elsewhere (e.g., up one level), there isn't a match for
"dspace" at all and hence no "something called dspace is there but it isn't a
directory" error.
As I said, the error appears to be non-fatal and the command executes despite
it but it's a little unsettling to get the error. Has anyone else seem
anything like this and know of a way to avoid it (other than not calling the
command while in the bin/ directory)?
Thanks.
--Jim
================================================
Jim Coble
Core Services Technical Lead and Program Coordinator
Information Technology Services
Perkins Library
Email: [email protected]
Voice: 919-660-5974 Fax: 919-668-2578
Box 90196, Duke University
Durham, NC 27708-0196
================================================
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
