I do not know, if you can generate a reproducible testcase that
demonstrates the behavior we might be able to determine the answers.
One thing to check on is that there is adequate disk space. This
has in the past lead to files getting truncated. You need plenty of
free disk space on the file system GlassFish is installed on, on
the system /tmp and on the home directory of the person that GlassFish
is installed as. We have seen that sometimes these can fill up for
reasons outside of GlassFish control and when that happens files
can become truncated. (used to happen with domain.xml during reconfig
and deployments for example)
I don't know if this is related to your issue or not, but it is definitely
something to look for and verify you have adequate free disk space.
> Oops - It seems that the jbi-registry.xml file had become truncated (zero
> length). The one that I validated was obviously the wrong one.
>
> However, the original questions remain:-
>
>
> 1) Why does GlassFish continually report upon an error that it can not resolve
> and should therefore shut down?
> 2) What could have caused the jbi-registry.xml file to be truncated?
>
>
> I have discovered that removing the zero length file allows it to be regenerated
> and the server starts.
>
>
> Andy Knight
> Principal Engineer,
> Sun Microsystems, Inc.
> Java House, Guillemont Park, Minley Road,
> Camberley, Surrey GU17 9QG United Kingdom
> Home office: +44 1494 462438
> Mobile: +44 7775 583415
> Skype: aprknight
> Email: Andy.Knight@Sun.COM
>
>
> On 18 Jan 2010, at 08:43, Andy Knight wrote:
>
>> My GlassFish v2.1 server was running perfectly 2 days ago. It was shut down
>> normally.
>>
>> I have just tried starting it today and the error that is the subject of this
>> email is produced. Over and over and over again. [ Does GlassFish think that
>> the file will fix itself? If it's broken, then it's broken. So stop! ]
>>
>> However, I can't figure out why this file is (allegedly) causing a problem.
>> I've certainly not edited it. I've also checked that it is well-formed (and it
>> is). According to XMLSpy it's not strictly valid but I doubt if that's the
>> problem.
>>
>>
>> What could I possibly have done to cause this? More importantly, what do I do
>> to fix it?
>>
>>
> <jbi-registry.xml>
>>
>>
> <server.log.zip>
>>
>>
> Andy Knight
> Principal Engineer,
> Sun Microsystems, Inc.
> Java House, Guillemont Park, Minley Road,
> Camberley, Surrey GU17 9QG United Kingdom
> Home office: +44 1494 462438
> Mobile: +44 7775 583415
> Skype: aprknight
> Email: Andy.Knight@Sun.COM