![]() |
|
|
|
|
Issue Type:
|
![Task]() Task
|
|
Affects Versions:
|
3.2, 3.1, 3.0 |
|
Assignee:
|
Unassigned |
|
Components:
|
DSpace API |
|
Created:
|
14/Aug/13 8:31 PM
|
|
Description:
|
Since DSpace 3, every time a command line command is launched, 4 log lines are written to stderr:
$ /dspace/bin/dspace -h
INFO [main] (DSpaceKernelInit.java:52) - Created new kernel: DSpaceKernel:org.dspace:name=8a47f3ad-6e21-4f8d-bb0f-a6748f0f838b,type=DSpaceKernel:lastLoad=null:loadTime=0:running=false:kernel=null
INFO [main] (ConfigurationManager.java:1224) - Loading from classloader: file:/dspace/config/dspace.cfg
INFO [main] (ConfigurationManager.java:1224) - Using dspace provided log configuration (log.init.config)
INFO [main] (ConfigurationManager.java:1224) - Loading: /dspace/config/log4j.properties
This is too much output with too little informational value. Suggested options:
1) Remove it altogether. We got by just fine without it up to DSpace 1.8 and it's in the log anyway.
2) Reduce it to a single line pointing to the configuration file used.
|
|
Environment:
|
command line launcher
|
|
Project:
|
DSpace
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Ivan Masár
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
