Sounds like it. But then again it seems to only occur on a certain page.
Mind posting the code? Is there a large object tree pulled in? Or do you
have a SessionState object in your page which grows and gets referenced too
long?
2009/8/19 martijn.list <martijn.l...@gmail.com>
> Could the NPE be caused by an out-of-memory? A NPE can sometimes be thrown
> on an out of memory.
>
> Martijn
>
>
> zack1403 wrote:
>
>> The page works fine for ~24 hours before this exception starts to show up.
>> If
>> the user.home property was not set it would probably error out first
>> thing. I am not setting it anywhere else either.
>>
>> Thanks,
>> Zack
>>
>>
>> martijn.list wrote:
>>
>>> Afaics resolve only throws a NullPointerException when either parent or
>>> child is null. The line numbers from the Stack trace do not exactly line up
>>> with my Java so I don't know at what line the exception actually occurs. I
>>> don't think child can be null because it is is the result of File.getPath().
>>> So, parent must be null (I guess :). That would suggest that
>>> System.getProperty("user.dir") returns null (this is the parent from the
>>> overloaded resolve(File f)).
>>>
>>> Just a wild guess
>>>
>>> Could it be that somewhere, somehow inside your code or code from a
>>> library user.dir is set to null?
>>>
>>> Martijn Brinkers
>>>
>>> --
>>> Djigzo open source email encryption
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>
>>>
>>>
>>>
>>
>
> --
> Djigzo open source email encryption
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
