This is the problem I had previously. I thought it went away when I
upgraded to the Sept 13th build, but I've had it one time since (bean
deployment problem at the same time). In a previous email, I detailed what
I saw occuring during the export of the .jcml file. Paraphrasing here,
there are two mbean attributes associated with the URL. Each contains the
same value. Neither gets past the test for isWriteable() and isReadable
inside of ConfigurationService.save(). Reference my email from 9/7/2000
entitled "Minerva, jboss.jcml, and XADataSourceLoader using PostgreSQL" for
as far as I went to figure this out.
I'm guessing a problem with minerva/mlet configuration or something weird
happening when a bean can't deploy. I saw this occur more when I had other
errors during startup.
Jeff Mc.
-----Original Message-----
From: Ole Husgaard [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 26, 2000 8:53 AM
To: jBoss
Subject: Re: [jBoss-User] Linux "url cannot be null" exception
Hi,
"Dubchak, John" wrote:
>
> Just as a follow up...
>
> What I have noticed, and it is consistent on both NT and Linux (Red Hat
6.2
> at least) is that the error can be repeated if the shutdown of the server,
> for whatever reason, is not successful.
>
> There have been instances when I have not had the Server shutdown properly
> when issuing either the "kill" Unix command, or CTRL-C in NT. The next
time
> I attempt to start up JBoss is when I encounter the error.
That may explain why this happened to me a lot a few days ago when I was
busy
finding a bug, and why I am unable to find a way to reproduce it now.
> Therefore, from what I can tell is that, the file "jboss.jcml" is
corrupted
> on an unclean exit.
I have noticed that jboss.jcml was OK before starting the server, and after
the server startup and deployment of default testbeans but before any
invokations the URL was missing in jboss.jcml. The server startup looked OK.
In this case the server may well have had an unclean shutdown just before I
tried to start it again (not quite sure, my memory fails me, unable to
reproduce today).
So maybe the jboss.jcml file is changed as a side effect to some kind of
repair that the server is doing when it starts up after an unclean shutdown.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
