Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Bug
Resolution: Won't Fix
Priority: Low
Fix Version/s: None
Affects Version/s: 4.0 - Beta 1
Component/s: Infrastructure & Services - Application Lifecycle
Labels:
- affects-server

Introduced in Version:
4

log4j:ERROR LogMananger.repositorySelector was null likely due to error in class
 reloading, using NOPLoggerRepository.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class
 reloading, using NOPLoggerRepository.

is detailed by

JRASERVER-17624 Address findings from the jira-home and plugins2 blitz test.

Closed

Assignee:: Unassigned
Reporter:: Mark Lassau (Inactive)

Created:: 12/Jun/2009 4:27 AM
Updated:: 12/Sep/2019 6:50 AM
Resolved:: 15/Jun/2009 2:59 AM
Archived:: 12/Sep/2019 6:57 AM