Petals ESB Container

NPE if no property 'handlers' is defined in logging configuration

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 4.1.0
  • Fix Version/s: 4.2.0
  • Component/s: Configuration, Logging
  • Security Level: Public
  • Description:
    Hide

    If no property named 'handlers' is defined in the logging configuration, the following error occurs and Petals ESB startup fails:

    ___   ____ __   ___    __    ____   ____ ____ ___  
    / _ \ / __// /_ / _ |  / /   / __/  / __// __// _ ) 
   / ___// _/ / __// __ | / /__ _\ \   / _/ _\ \ / _  | 
  /_/   /___/ \__//_/ |_|/____//___/  /___//___//____/  

Initializing server ...
Listening for transport dt_socket at address: 8000
ERROR: null
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.ow2.petals.launcher.PetalsLauncher.launchPetalsServer(PetalsLauncher.java:103)
	at org.ow2.petals.launcher.PetalsLauncher.main(PetalsLauncher.java:202)
Caused by: org.ow2.petals.kernel.api.server.PetalsException: Problem while initializing Petals
	at org.ow2.petals.kernel.server.PetalsServerImpl.init(PetalsServerImpl.java:169)
	... 6 more
Caused by: java.lang.NullPointerException
	at com.ebmwebsourcing.easycommons.properties.PropertiesHelper.parsePropertyValues(PropertiesHelper.java:330)
	at org.ow2.petals.kernel.server.PetalsServerImpl.finalizeLoggingInitialization(PetalsServerImpl.java:702)
	at org.ow2.petals.kernel.server.PetalsServerImpl.initializeLogger(PetalsServerImpl.java:656)
	at org.ow2.petals.kernel.server.PetalsServerImpl.init(PetalsServerImpl.java:163)
	... 6 more
    Show
    If no property named 'handlers' is defined in the logging configuration, the following error occurs and Petals ESB startup fails: 
    ___   ____ __   ___    __    ____   ____ ____ ___  
    / _ \ / __// /_ / _ |  / /   / __/  / __// __// _ ) 
   / ___// _/ / __// __ | / /__ _\ \   / _/ _\ \ / _  | 
  /_/   /___/ \__//_/ |_|/____//___/  /___//___//____/  

Initializing server ...
Listening for transport dt_socket at address: 8000
ERROR: null
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.ow2.petals.launcher.PetalsLauncher.launchPetalsServer(PetalsLauncher.java:103)
	at org.ow2.petals.launcher.PetalsLauncher.main(PetalsLauncher.java:202)
Caused by: org.ow2.petals.kernel.api.server.PetalsException: Problem while initializing Petals
	at org.ow2.petals.kernel.server.PetalsServerImpl.init(PetalsServerImpl.java:169)
	... 6 more
Caused by: java.lang.NullPointerException
	at com.ebmwebsourcing.easycommons.properties.PropertiesHelper.parsePropertyValues(PropertiesHelper.java:330)
	at org.ow2.petals.kernel.server.PetalsServerImpl.finalizeLoggingInitialization(PetalsServerImpl.java:702)
	at org.ow2.petals.kernel.server.PetalsServerImpl.initializeLogger(PetalsServerImpl.java:656)
	at org.ow2.petals.kernel.server.PetalsServerImpl.init(PetalsServerImpl.java:163)
	... 6 more
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Wed, 11 Jul 2012 - 18:14:53 +0200
Field Original Value New Value
Fix Version/s 4.1.1 [ 10356 ]
Priority Minor [ 4 ]
Hide
Permalink
Christophe DENEUX added a comment - Wed, 11 Jul 2012 - 18:21:53 +0200

This problem is due to the hardcoded configuration of the logging system. If no hard-coded configuration is needed, this problem will disappear.

Show
Christophe DENEUX added a comment - Wed, 11 Jul 2012 - 18:21:53 +0200 This problem is due to the hardcoded configuration of the logging system. If no hard-coded configuration is needed, this problem will disappear.
Christophe DENEUX made changes - Wed, 11 Jul 2012 - 18:21:53 +0200
Link This issue depends on PETALSESBCONT-197 [ PETALSESBCONT-197 ]
Christophe DENEUX made changes - Mon, 3 Sep 2012 - 12:52:19 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Mon, 3 Sep 2012 - 12:52:22 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Mon, 3 Sep 2012 - 12:52:41 +0200

Now, if no handlers is configured, no trace is logged

Show
Christophe DENEUX added a comment - Mon, 3 Sep 2012 - 12:52:41 +0200 Now, if no handlers is configured, no trace is logged
Christophe DENEUX made changes - Mon, 3 Sep 2012 - 12:52:41 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 7 Mar 2013 - 12:13:59 +0100
Component/s Logging [ 10255 ]
Component/s Administration [ 10052 ]
Christophe DENEUX made changes - Tue, 12 Mar 2013 - 08:18:51 +0100
Component/s Configuration [ 10257 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
53d 18h 47m
1
Christophe DENEUX
Mon, 3 Sep 2012 - 12:52:19 +0200
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Mon, 3 Sep 2012 - 12:52:22 +0200
In Progress In Progress Resolved Resolved
19s
1
Christophe DENEUX
Mon, 3 Sep 2012 - 12:52:41 +0200



People

Dates

  • Created:
    Wed, 11 Jul 2012 - 18:05:02 +0200
    Updated:
    Tue, 12 Mar 2013 - 08:18:51 +0100
    Resolved:
    Mon, 3 Sep 2012 - 12:52:41 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.