When I saved the datasource, it failed validation saying that it
couldn't find the specified Postgres driver. I downloaded the latest
JDBC 4 drivers and put the JAR file in Tomcat's lib folder and
restarted Tomcat.
After that the datasource validates okay but some of my queries are
returning syntax errors whenever I enable the JDBC wrapper (simple
stuff like SELECT count(field) FROM table ).
My question is, ColdFusion obviously was able to run these queries
before I downloaded the JDBC drivers. Does anyone know if there's a
different driver class name that I should be using in the last part of
the connection string that I could test out to see if it's an issue
with FR or an issue with the JDBC driver I'm telling it to use?
As for your challenge, I realize that getting a message saying the driver couldn't be found might drive you to get new drivers, but that really wasn't the answer, so you can likely undo that. :-) In fact, you could be having a clash between those and the PostGres driver that come with CF.
Instead, you've hit a problem for which there is a known issue and solution. Check out this technote:
As for how you (or anyone with an error like this) might find such a solution, I'll point out that the FR site has a support section (http://www.fusion-reactor.com/fr/support.cfm), where you could for instance drop in the error you got, which may have found it (whether in the technotes or in this google group). (I appreciate you may well have tried it with some specific error you got and found no answer. Indeed, I was surprised to see that searching there for just "postgres" found only your new google group message.)
You can also see a discussion of this issue above (again, not related to Postgres) in the first few messages in this thread:
Finally, as for the technote, you may notice that it says that it's usually due to using drivers other than those built-in to CF. But I realize you likely started out using the Postgres one that is built-in (meaning, when you originally created the datasource in the CF Admin Datasource page, I assume you selected postgres from the drop-down offered there.) In that case, you were not in fact using a "third party driver", which you would do if you had selected "other" form the drop down (though again, when you went and downloaded the new drivers, you did then switch to using such an "other", third-party driver. To be clear, I'm not referring to the creation of the "wrapped" version of the datasource, which of course does use the "other" driver option.)
But I see that it also says that this problem can happen when one has manually installed FR. Did you by any chance do that? Just curious.
Either way, let's see if that technote's solution solves the problem for you. If so, let us know.
And then do let us know also if it's that you had installed CF manually, or perhaps you had originally used an "other" driver before ever trying to wrap the DSN.
> When I saved the datasource, it failed validation saying that it > couldn't find the specified Postgres driver. I downloaded the latest > JDBC 4 drivers and put the JAR file in Tomcat's lib folder and > restarted Tomcat.
> After that the datasource validates okay but some of my queries are > returning syntax errors whenever I enable the JDBC wrapper (simple > stuff like SELECT count(field) FROM table ).
> My question is, ColdFusion obviously was able to run these queries > before I downloaded the JDBC drivers. Does anyone know if there's a > different driver class name that I should be using in the last part of > the connection string that I could test out to see if it's an issue > with FR or an issue with the JDBC driver I'm telling it to use?
> Thanks for any assistance.
> Dan
> -- > You received this message because you are subscribed to the Google > Groups "FusionReactor" group. > To post to this group, send email to fusionreactor@googlegroups.com. > To unsubscribe from this group, send email to > fusionreactor+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/fusionreactor?hl=en.
I originally created the DSNs with CF's built-in Postgres option. It
was only when I tried to wrap them by manually configuring the "other"
type that I got the error.
The other point in the tech note though does apply to me. I have ACF9
deployed as a WAR file to Tomcat 7. I installed FR with the Linux
shell script as per the instructions but I had to manually configure
the new FR instance for my application to get it up and running.
I'll buzz through the tech note here in a bit and see if the steps in
there solve the issue for me.
<charlie_li...@carehart.org> wrote:
> Hey Dan, welcome to the list.
> As for your challenge, I realize that getting a message saying the driver
> couldn't be found might drive you to get new drivers, but that really wasn't
> the answer, so you can likely undo that. :-) In fact, you could be having a
> clash between those and the PostGres driver that come with CF.
> Instead, you've hit a problem for which there is a known issue and solution.
> Check out this technote:
> As for how you (or anyone with an error like this) might find such a
> solution, I'll point out that the FR site has a support section
> (http://www.fusion-reactor.com/fr/support.cfm), where you could for instance
> drop in the error you got, which may have found it (whether in the technotes
> or in this google group). (I appreciate you may well have tried it with some
> specific error you got and found no answer. Indeed, I was surprised to see
> that searching there for just "postgres" found only your new google group
> message.)
> You can also see a discussion of this issue above (again, not related to
> Postgres) in the first few messages in this thread:
> Finally, as for the technote, you may notice that it says that it's usually
> due to using drivers other than those built-in to CF. But I realize you
> likely started out using the Postgres one that is built-in (meaning, when
> you originally created the datasource in the CF Admin Datasource page, I
> assume you selected postgres from the drop-down offered there.) In that
> case, you were not in fact using a "third party driver", which you would do
> if you had selected "other" form the drop down (though again, when you went
> and downloaded the new drivers, you did then switch to using such an
> "other", third-party driver. To be clear, I'm not referring to the creation
> of the "wrapped" version of the datasource, which of course does use the
> "other" driver option.)
> But I see that it also says that this problem can happen when one has
> manually installed FR. Did you by any chance do that? Just curious.
> Either way, let's see if that technote's solution solves the problem for
> you. If so, let us know.
> And then do let us know also if it's that you had installed CF manually, or
> perhaps you had originally used an "other" driver before ever trying to wrap
> the DSN.
> Hope that's helpful.
> /charlie
> > -----Original Message-----
> > From: fusionreactor@googlegroups.com
> > [mailto:fusionreactor@googlegroups.com] On Behalf Of Dan Skaggs
> > Sent: Saturday, December 31, 2011 8:44 PM
> > To: FusionReactor
> > Subject: [fusionreactor] JDBC Wrapper format question
> > I'm having an issue with FR's JDBC wrapper. I'm using Postgresql and
> > have set up my datasource as such:
> > When I saved the datasource, it failed validation saying that it
> > couldn't find the specified Postgres driver. I downloaded the latest
> > JDBC 4 drivers and put the JAR file in Tomcat's lib folder and
> > restarted Tomcat.
> > After that the datasource validates okay but some of my queries are
> > returning syntax errors whenever I enable the JDBC wrapper (simple
> > stuff like SELECT count(field) FROM table ).
> > My question is, ColdFusion obviously was able to run these queries
> > before I downloaded the JDBC drivers. Does anyone know if there's a
> > different driver class name that I should be using in the last part of
> > the connection string that I could test out to see if it's an issue
> > with FR or an issue with the JDBC driver I'm telling it to use?
> > Thanks for any assistance.
> > Dan
> > --
> > You received this message because you are subscribed to the Google
> > Groups "FusionReactor" group.
> > To post to this group, send email to fusionreactor@googlegroups.com.
> > To unsubscribe from this group, send email to
> > fusionreactor+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/fusionreactor?hl=en.
I ran through the tech note earlier today and applied the fix as
specified there as well as removed the Postgres JDBC drivers I'd
downloaded. Once I restarted everything I started getting an Hibernate
error on every query (sorry, I don't have the exact error message
right now). Anyway, I decided to just roll back to my un-wrapped DSN
for now.We're going live with this application in the morning and you
know what the final hours before go-live are like.
I'll see about troubleshooting it further this week after the initial
crush from the launch has (hopefully) subsided. I may build a Linux VM
to test it later this week and will definitely let the list know if I
find anything useful.
<charlie_li...@carehart.org> wrote:
> Hey Dan, welcome to the list.
> As for your challenge, I realize that getting a message saying the driver
> couldn't be found might drive you to get new drivers, but that really wasn't
> the answer, so you can likely undo that. :-) In fact, you could be having a
> clash between those and the PostGres driver that come with CF.
> Instead, you've hit a problem for which there is a known issue and solution.
> Check out this technote:
> As for how you (or anyone with an error like this) might find such a
> solution, I'll point out that the FR site has a support section
> (http://www.fusion-reactor.com/fr/support.cfm), where you could for instance
> drop in the error you got, which may have found it (whether in the technotes
> or in this google group). (I appreciate you may well have tried it with some
> specific error you got and found no answer. Indeed, I was surprised to see
> that searching there for just "postgres" found only your new google group
> message.)
> You can also see a discussion of this issue above (again, not related to
> Postgres) in the first few messages in this thread:
> Finally, as for the technote, you may notice that it says that it's usually
> due to using drivers other than those built-in to CF. But I realize you
> likely started out using the Postgres one that is built-in (meaning, when
> you originally created the datasource in the CF Admin Datasource page, I
> assume you selected postgres from the drop-down offered there.) In that
> case, you were not in fact using a "third party driver", which you would do
> if you had selected "other" form the drop down (though again, when you went
> and downloaded the new drivers, you did then switch to using such an
> "other", third-party driver. To be clear, I'm not referring to the creation
> of the "wrapped" version of the datasource, which of course does use the
> "other" driver option.)
> But I see that it also says that this problem can happen when one has
> manually installed FR. Did you by any chance do that? Just curious.
> Either way, let's see if that technote's solution solves the problem for
> you. If so, let us know.
> And then do let us know also if it's that you had installed CF manually, or
> perhaps you had originally used an "other" driver before ever trying to wrap
> the DSN.
> Hope that's helpful.
> /charlie
> > -----Original Message-----
> > From: fusionreactor@googlegroups.com
> > [mailto:fusionreactor@googlegroups.com] On Behalf Of Dan Skaggs
> > Sent: Saturday, December 31, 2011 8:44 PM
> > To: FusionReactor
> > Subject: [fusionreactor] JDBC Wrapper format question
> > I'm having an issue with FR's JDBC wrapper. I'm using Postgresql and
> > have set up my datasource as such:
> > When I saved the datasource, it failed validation saying that it
> > couldn't find the specified Postgres driver. I downloaded the latest
> > JDBC 4 drivers and put the JAR file in Tomcat's lib folder and
> > restarted Tomcat.
> > After that the datasource validates okay but some of my queries are
> > returning syntax errors whenever I enable the JDBC wrapper (simple
> > stuff like SELECT count(field) FROM table ).
> > My question is, ColdFusion obviously was able to run these queries
> > before I downloaded the JDBC drivers. Does anyone know if there's a
> > different driver class name that I should be using in the last part of
> > the connection string that I could test out to see if it's an issue
> > with FR or an issue with the JDBC driver I'm telling it to use?
> > Thanks for any assistance.
> > Dan
> > --
> > You received this message because you are subscribed to the Google
> > Groups "FusionReactor" group.
> > To post to this group, send email to fusionreactor@googlegroups.com.
> > To unsubscribe from this group, send email to
> > fusionreactor+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/fusionreactor?hl=en.
OK, thanks for the update, Dan. Sorry that it didn't work out. It's possible that in trying to get the split jar setup working (per the technote), while under the crush of preparing for your prod rollout, you may have missed something.
If you have time when things settle, yes it will be great to hear if first you can recreate the original problem you had, and then can apply the split-jar solution to make it go away. Certainly if you try it and still can't get it working, do just share more info. You'll find that the Intergral support folks here are wonderful. I don't think I've seen a problem presented yet that they couldn't solve. :-)
> -----Original Message----- > From: fusionreactor@googlegroups.com > [mailto:fusionreactor@googlegroups.com] On Behalf Of Dan Skaggs > Sent: Sunday, January 01, 2012 7:17 PM > To: FusionReactor > Subject: [fusionreactor] Re: JDBC Wrapper format question
> Charlie...
> I ran through the tech note earlier today and applied the fix as > specified there as well as removed the Postgres JDBC drivers I'd > downloaded. Once I restarted everything I started getting an Hibernate > error on every query (sorry, I don't have the exact error message right > now). Anyway, I decided to just roll back to my un-wrapped DSN for > now.We're going live with this application in the morning and you know > what the final hours before go-live are like.
> I'll see about troubleshooting it further this week after the initial > crush from the launch has (hopefully) subsided. I may build a Linux VM > to test it later this week and will definitely let the list know if I > find anything useful.
