> I'd like to report the problem with jboss.jcml that discourages me
> (I use the current CVS build).
> Namely, sometimes "URL" attribute for "XADataSource" service sometimes
> disappears (the others remain in place).
> I believe that it is concerned to the load of the server or some kind
> of timeout.
> This effect is stable when I run jBoss with a remote debugger and some
> breakpoints are turned on (thus, jBoss runs slower).
> I tried to trace what happens and found out that in
> ConfigurationService.save() in the line
>
> if (attributes[i].isReadable() && attributes[i].isWritable())
>
> attributes[i].isWritable() for "URL" is evaluated as "false"
> (of course, should be "true", since XADataSourceLoader.setURL() method
> exists).
> Any ideas?
I to have experienced this.
I tracked it down on my installation to the JVM type being used when
launching JBoss. I have my own shell script which launches JBoss, and
when I downloaded the latest version this past weekend, the URL as
described above would not get written to jboss.jcml, making the second
invokation of JBoss not work.
I finally reproduced it with the standard run.sh file by replacing the
"-server" option with "-classic". With this in place, one can reproduce
this problem with the CVS version of JBoss.
I am running JBoss on Linux with the following "java -version" output:
java version "1.3.0beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.3.0beta_refresh-b09)
Java HotSpot(TM) Client VM (build 1.3.0beta-b07, mixed mode)
Since this is an out of date beta, I didn't bother to report this issue
earlier.
Pat McNerthney
Icicle Software, Inc.
