Closed slamont closed 9 years ago
Hey, cheers for reporting...
Are you using forge release, or from GH?
Will take a look tomorrow and let you know what I find..
Cheers Gav
Ah, looks like I fixed it in https://github.com/fatmcgav/fatmcgav-glassfish/commit/b39403471fd600a0758c0c3509eeecf5bfcc5d5d Can you try using the develop branch from Git?
Cheers Gav
I am using the forge release. Will try with the latest code tomorrow and comment back :-)
I've tried with bd85e2f485b85c75620c78f27ad8147bdff8445f (latest master) and I got the same error
Ok I've just see that you have a Develop branch ! Sorry I was slow to realize thats what you were saying. I'll try with the tip of this branch.
Yeh, give develop a spin and see if that works :)
I've tried develop and it worked perfectly ! Thank You ! Do you think about reintegrating develop in master and release to the forge soon ?
Yeh, I'm planning on getting a new release out soon.. Keep an eye on the forge/twitter... :-) On 1 Aug 2014 18:57, "slamont" notifications@github.com wrote:
I've tried develop and it worked perfectly ! Thank You ! Do you think about reintegrating develop in master and release to the forge soon ?
— Reply to this email directly or view it on GitHub https://github.com/fatmcgav/fatmcgav-glassfish/issues/31#issuecomment-50915062 .
@slamont Have just pushed v0.3.0 to the forge.
When a first puppet run is done and have configured a jdbcconnectionpool, the second puppet run will fail saying that the jdbcconnectionpool already exist.
First puppet run:
Second Puppet run:
It seems that the execution of "asadmin --port 4848 --user asci list-jdbc-connection-pools" returned correctly the pool that was created in the first run, but it still try to create it.
I'm running un Ubuntu 14.04, if you need anything else let me know.