Saturday, 14 February 2009

No PasswordCredential found

I got the exception below while trying to set up a JNDI database configuration in glasshish to point to my local Oracle XE installation. Google didn't help so I'm posting it here for in case it happens to me again.
I didn't actually figure out how to resolve it. I fiddled around in domains/domain1/config/domain.xml a little, but in the end I think restarting Glassfish did the trick for me.


INFO: RAR7099: The mcf being used to allocate the connection and the MCF in the pool are not equal.
WARNING: RAR5038:Unexpected exception while creating resource for pool aum_pool. Exception : No PasswordCredential found
WARNING: RAR5117 : Failed to obtain/create connection from connection pool [ aum_pool ]. Reason : No PasswordCredential found
WARNING: RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: No PasswordCredential found]
WARNING: java.sql.SQLException: Error in allocating a connection. Cause: No PasswordCredential found
at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:115)
Posted by Unknown at 03:01
Labels: , ,

30 comments:

  1. Anonymous19 May, 2009 15:15

    How something so simple can solve a unknown problem - thanks for the help. Right, back to deploying my war's :)

    ReplyDelete
  2. Matt19 May, 2009 17:49

    Of course restarting works, why didn't I think of it? Thanks for the post.

    ReplyDelete
  3. Anonymous29 July, 2009 15:20

    Even though I wasn't having the same problem you had, I'd just like to express appreciation that reading your post did give me an idea how to address my problem and reconfigure settings to find the solution. Thanks!

    ReplyDelete
  4. Anonymous28 August, 2009 14:34

    I thought Glassfish will handle a change in the connection wihtout a restart and got the same problem. This message is really tricky and only thanks to your post I found a quick solution.

    ReplyDelete
  5. Gili30 September, 2009 01:59

    Thanks for the head's up!

    ReplyDelete
  6. Anonymous15 February, 2010 04:52

    Rest worked for me too. Nice post :). Would have been better if glassfish warned us that we may need to restart the server for the changes we made.

    ReplyDelete
  7. Anonymous31 March, 2010 19:24

    Thanks, hadn't assumed this would be necessary but apparently it is!

    ReplyDelete
  8. Anonymous06 April, 2010 16:21

    Great man, it worked for me. I am still wondering how this worked? actually I made changes through GF admin console pinged successfully datasource. then tried from application. May be the changes are not bind to the application without server restart!!!!

    -Ravi.

    ReplyDelete
  9. Anonymous09 April, 2010 14:10

    Thanks, I wish I had found your site earlier! I would have saved some time. I wish others would post their solutions when they find answers to issue such as this.

    ReplyDelete
  10. stanb10 April, 2010 01:53

    Thanks! You saved me a lot of time.

    ReplyDelete
  11. Anonymous06 May, 2010 07:39

    Quick thanks

    ReplyDelete
  12. Anonymous27 October, 2010 06:57

    Thanks dude. This has been a long and frustrating battle (getting hibernate to work with itself - let alone with Glassfish)

    ReplyDelete
  13. Anonymous27 October, 2010 09:13

    Thank you! Worked!

    ReplyDelete
  14. Anonymous22 February, 2011 11:40

    good one :)

    ReplyDelete
  15. Anonymous06 May, 2011 11:20

    thanks !!!

    ReplyDelete
  16. anty06 June, 2011 14:27

    Thank you, "asadmin restart-domain" worked for me!

    ReplyDelete
  17. Anonymous27 July, 2011 21:00

    Usually, when the system properties are changed, Glassfish prompts a "Restart Required" warning message. In this case it didn't and I assumed that it was OK with it. Apparently not! Thanks for the post!

    ReplyDelete
  18. Anonymous11 October, 2011 15:08

    Cheers for posting it.

    ReplyDelete
  19. Nacho18 January, 2012 22:25

    +1 to restart

    ReplyDelete
  20. Anonymous13 February, 2012 18:18

    Hehe - Nice! Saved me a lot of work. :)

    ReplyDelete
  21. Unknown19 March, 2012 18:56

    Thanks! This did the trick for us too!

    ReplyDelete
  22. Anonymous25 March, 2012 18:25

    I added the property "PasswordCredential" to the list of properties, with the value being my database password. That worked for me. I'm using GlassFish Server Open Source Edition 3

    ReplyDelete
  23. Anonymous29 March, 2012 04:37

    Restarting Glassfish? That's not an answer because it doesn't actually figure out what was wrong. I had a problem where the password on my database was blank. In this case I needed to follow the directions here. https://blogs.oracle.com/vkraemer/entry/no_passwordcredential_found

    ReplyDelete
  24. Anonymous25 April, 2012 02:00

    Great job!! This worked for me. I had to change the url property and when I ran the application I received the "java.sql.SQLException: Error in allocating a connection. Cause: No PasswordCredential found" message. A simple restart fixed it. Thanks!!

    ReplyDelete
  25. Anonymous06 June, 2012 14:18

    thanks man... *facepalm to myself*

    ReplyDelete
  26. Anonymous11 July, 2012 13:13

    Thank you...

    ReplyDelete
  27. Anonymous25 July, 2012 10:20

    Restart for NoPasswordCredential? Yeah, right... Hey! It works!

    ReplyDelete
  28. Anonymous07 September, 2012 10:49

    Just setting the PasswordCredantial in the Pool-configuration fixed the problem without restart.

    ReplyDelete
  29. Anonymous20 September, 2013 18:01

    Awesome! Thanks! :)

    ReplyDelete
  30. Anshul21 October, 2013 04:37

    Related Post explaining that a restart in fact is required if you update the connection pool settings.
    https://netbeans.org/bugzilla/show_bug.cgi?id=150051#c19

    ReplyDelete

Subscribe to: Post Comments (Atom)