Jboss 6 Admin Console Issue : Cannot update Datasource Configurations

[abduljaleelch]

Hi All,

        I am a newbee in Jboss(Using version 6). I am facing a problem when i enter the Datasource Configurations using Admin Console. The modifications are not getting reflected.I have to make modifications in xml file directly. As my organization need more than 50 different datasources running in the application server , we certainly need an interface to manage these configurations. Please help..

[bcn]

I observe something similar: username and password are not saved. The fields are unset again.

[wdfink]

Modification via jmx- or management-console are temporary. The only way to survive the next restart is to change the XML files.

Also you might have to flush the connection pool to activate the console changes. be aware that this kill all active transactions related to this datasource.

[bcn]

Is this on purpose or is it a bug? If I save a configuration change, I expect it to be persistent. In my case, it is not even saved during the same session.

[wdfink]

It is not a bug.

If you change via management console nothing will be persistent.

[abduljaleelch]

Thank you for your reply...  We are using Weblogic as Server.More than 10 different applications are deployed in it. The thing is i am asked to make an R&D of using Jboss for intra organization applications. But I don't think i can make use of Jboss for this purpose. Restarting the server for every change is not practical in my case since i will have frequent changes in datasources..

[wdfink]

This doesn't mean that you have to restart the server.

If you want have a temporary change unti the next restart, you might use the console to change.

But if you try to change the configuration you have to change the configuration file.

If you have hotdeployment configured the change become active without restarting the server.

[bcn]

Oracle AS handles it like this: changes are saved, but you get a message that the changes are only applied after restarting the server instance. I think this is a good solution. But enabling the Save button and just ignoring the changes is really confusing for the user. In my case, when I change user and password, after save the page is reloaded and the changes are lost.

So I think the console should at least inform the user with a message about how it works.

[shelly.mcgowan]

The changes done via the Administration Console *are* persistent.  However, the changes do *not* get written back to the original .xml file.   From the Chapter 10 of the Administration Console Guide:

Warning

If a resource was previously deployed and modified via the Console, the administration of the resource should continue to be done via the Console. The resource modifications are persistent but will not be reflected in the resources original configuration file. This means that changes between manual edits to configuration files and changes performed via the Console are not interchangeable. If you make a change to a configuration file outside of the Administration Console it will override and replace any changes you have previously made via the Console.

[wdfink]

Hi Shelly,

but this is exactly what I meant in different words.

The change don by console is persistent as long as the server is restarted and read the configuration from XML, or even if you change (or touch) the XML file an hotdeployment is active.

[ma3145tt]

Since the admin console does not update the xml file, where is the new information stored?  I'm particularly concerned with the location of the password data.

[efrinmn]

Changes made using the admin console are persisted in the /data directory.  For more detail refer to:  http://community.jboss.org/thread/153394