Smalltalk › Instantiations

NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

jtuchel

NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

What is the best way to find the cause of these messages?

I remember spending a fair amount of time hunting for these - most of the times, the only thing that helped was trial and error.

It's being written to the console by a Linux Runtime image. I'd like to find out what is missing.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/gE9wCSOn_CoJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Louis LaBrunda

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

Hi Joachim,

I'm not sure I fully understand your question but it seems like you are missing an NLS file. I either include all the NLS files when I distribute a system or I use the packaging option (I forget exactly whet it is call) that binds the needed NLS data in the packaged image. As long as the resultant size isn't a problem, I don't have to think about what NLF files are required.

Lou

On Tuesday, July 17, 2012 3:13:43 PM UTC-4, [hidden email] wrote:

What is the best way to find the cause of these messages?

I remember spending a fair amount of time hunting for these - most of the times, the only thing that helped was trial and error.
It's being written to the console by a Linux Runtime image. I'd like to find out what is missing.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/oreSfuWPN4UJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

John O'Keefe-3

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

Lou -

Yes, that is the common cause of this message. But the difference here is the nil. For .mpr files, the nls pool dictionary maps a message id (name) to a number. Since the number is nil, it most likely means that there is a mismatch between the actual .mpr file and its nls pool dictionary.

Joachim -

Is the problem really with AbtMsgBase or did you just use that as an example?

John

On Wednesday, July 18, 2012 10:54:17 AM UTC-4, Louis LaBrunda wrote:

Hi Joachim,

I'm not sure I fully understand your question but it seems like you are missing an NLS file. I either include all the NLS files when I distribute a system or I use the packaging option (I forget exactly whet it is call) that binds the needed NLS data in the packaged image. As long as the resultant size isn't a problem, I don't have to think about what NLF files are required.

Lou

On Tuesday, July 17, 2012 3:13:43 PM UTC-4, [hidden email] wrote:
What is the best way to find the cause of these messages?

I remember spending a fair amount of time hunting for these - most of the times, the only thing that helped was trial and error.
It's being written to the console by a Linux Runtime image. I'd like to find out what is missing.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/SQ3S2SNQ5tQJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

jtuchel

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

Hi Lou and John,

it is the real message, I get it on my Ubuntu development machine on which I also develop and package. The runtime image resides in the same directory as the development image and the start batch files point to the same act directory location.

The only difference is the Locale setting.

A side effect that may be related is that on that machine, I get dates converted to american formats (12/31/2012) instead of German (31.12.2012) and the development image complains about an unsupported Locale. So this may or may not be a message related to Locales and the AbtDateConverter or some errors related to that one.

Interestingly, on a real web server that runs openSuSE, there is neither a problem with date conversion nor the missing nil in AbtMsgBase message show up... Since it runs on the production server (it is in fact a pre-beta machine), the issue is not pressing, but I'd like to understand it to avoid it on other systems or at least know what to look after...

So how would I find out what exactly is wrong? How can I find the places where AbtMsgBase is referenced and how could I possibly find out what the nil would normally be supposed to be?

Lou: the idea of internalizing Message catalogs (I guess that is the option you were talking about) sounds like a good idea. Image size is not important, this is a Seaside-based web application, so a few megs more or less don't really make a difference.

Joachim

Am Mittwoch, 18. Juli 2012 20:31:47 UTC+2 schrieb John O'Keefe:

Lou -

Yes, that is the common cause of this message. But the difference here is the nil. For .mpr files, the nls pool dictionary maps a message id (name) to a number. Since the number is nil, it most likely means that there is a mismatch between the actual .mpr file and its nls pool dictionary.

Joachim -

Is the problem really with AbtMsgBase or did you just use that as an example?

John

On Wednesday, July 18, 2012 10:54:17 AM UTC-4, Louis LaBrunda wrote:
Hi Joachim,

I'm not sure I fully understand your question but it seems like you are missing an NLS file. I either include all the NLS files when I distribute a system or I use the packaging option (I forget exactly whet it is call) that binds the needed NLS data in the packaged image. As long as the resultant size isn't a problem, I don't have to think about what NLF files are required.

Lou

On Tuesday, July 17, 2012 3:13:43 PM UTC-4, [hidden email] wrote:
What is the best way to find the cause of these messages?

I remember spending a fair amount of time hunting for these - most of the times, the only thing that helped was trial and error.
It's being written to the console by a Linux Runtime image. I'd like to find out what is missing.

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/B-eP5Klx7UoJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Louis LaBrunda

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

In reply to this post by jtuchel

Hi John and Joachim,

Good point about the nil. The message is probably coming from AbtNlsIndexedStrings>logMissingId:withinGroupNamed:, whose first parameter should be an integer. The integer is usually from methods that are looking up an NLS message. Those methods often use a constant defined in a pool dictionary, to pass the integer. I think the most likely way the integer would be nil and not an integer is if the pool dictionary was not included when packaged.

Joachim - When this works, is it with the exact same packaged image? If so, my analysis would seem incorrect.

Lou

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/1oHIdatbNBMJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

jtuchel

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

Lou,

it is indeed the very same image. On our inhouse Ubuntu machine, we get these errors, on the production SuSE Server all is fine.

So what you are suggesting is putting a halt into AbtNlsIndexedStrings>logMissingId:withinGroupNamed: and see what sender the nil is coming from...?

Joachim

Am Donnerstag, 19. Juli 2012 17:15:29 UTC+2 schrieb Louis LaBrunda:

Hi John and Joachim,

Good point about the nil. The message is probably coming from AbtNlsIndexedStrings>logMissingId:withinGroupNamed:, whose first parameter should be an integer. The integer is usually from methods that are looking up an NLS message. Those methods often use a constant defined in a pool dictionary, to pass the integer. I think the most likely way the integer would be nil and not an integer is if the pool dictionary was not included when packaged.

Joachim - When this works, is it with the exact same packaged image? If so, my analysis would seem incorrect.

Lou

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/87jTko1H7jsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Louis LaBrunda

Re: NLS Warning (VA). Missing nil in group 'AbtMsgBase'.

Hi Joachim,

On Tuesday, September 18, 2012 8:32:03 AM UTC-4, [hidden email] wrote:

Lou,

it is indeed the very same image. On our inhouse Ubuntu machine, we get these errors, on the production SuSE Server all is fine.

Being the same image eliminates a packaging problem.

So what you are suggesting is putting a halt into AbtNlsIndexedStrings>logMissingId:withinGroupNamed: and see what sender the nil is coming from...?

You could give that a try but after re-reading your posts I think the problem with an unsupported Locale is the key to this. If the Locale is unsupported (could be a typo in the ini file) there could be a problem with linking up the the NLS files or some other MRI stuff. Trying to create a message (using NLS) about not being able to get to the NLS data could lead to the error message.

Lou

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/XGkLSlX4lCoJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.