Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338222

Summary:	A message with the key 'ME0003I' was not found
Product:	[RT] Virgo	Reporter:	Chris Frost <eclipse>
Component:	runtime	Assignee:	Project Inbox <virgo-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	dmitry, glyn.normington, hsiliev
Version:	3.0.0.M01
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Chris Frost

2011-02-25 09:33:17 EST

<ME0001W> A message with the key 'ME0003I' was not found. The inserts for the message were '[serviceability\dump\2011-01-31-21-26-328]' 

Occurs under certain Kernel starup failures. Due to user modification I suspect but the message key should still have a message.

Comment 1 Dmitry Sklyut

2011-02-28 11:10:36 EST

The key with message live in org.eclipse.virgo.medic EventLogMessages.properties.

ME0003I=Dump '{}' generated

ME0001W is a "Message missing" key static in LogBackEventLogger.
private static final String MISSING_MESSAGE_EVENT_CODE = "ME0001W";

Same "ME0001W" is also persent in EventLogMessages.properties with a different message.
ME0001W=The directory '{}' does not exist and could not be created

One on those keys must be changed or suffer confusion.

I was not able to recreate this issue yet in 3.0.0.M01 to figure out if a medic is using wrong bundleContext to look up message bundle resources.

Comment 2 Hristo Iliev

2011-02-28 16:28:00 EST

Bug 337306 contains similar issue (duplicate ME0001W) as the one spotted by Dmitry.

The servicability dump was not displayed in 2.1.0 (bug 334372) since the properties file was localized as "_en". This caused the "not found" message for other locales (DE or BG for instance).