Torquebox 2.0.3 and oracle_enhanced 1.4.1

82 views
Skip to first unread message

pberg

unread,
Dec 4, 2012, 10:43:21 AM12/4/12
to oracle-...@googlegroups.com
Hi,

I want to run my application in torquebox 2.0.3 and I use activerecord-oracle_enhanced-adapter (1.4.1).

I get the following error at runtime:
16:23:24,151 ERROR [org.torquebox.web.servlet.RackFilter] (http--127.0.0.1-8080-2) Error invoking Rack filter: org.jruby.exceptions.RaiseExcep
tion: Native Exception: 'class java.sql.SQLException'; Message: No suitable driver found for jdbc:oracle:thin:@XXXXX
; StackTrace: java.sql.SQLException: No suitable driver found for jdbc:oracle:thin:@XXXXX
        at java.sql.DriverManager.getConnection(DriverManager.java:602)

I copied the ojdbc6.jar in the lib directory of my rails application and to several directories of $TORQUEBOX_HOME.

Has anyone experience with the torquebox/activerecord-oracle_enhanced-adapter duo?

I found this link: https://issues.jboss.org/browse/TORQUE-762

but it seems not to work.

Thomas

Yasuo Honda

unread,
Dec 5, 2012, 2:26:14 PM12/5/12
to oracle-...@googlegroups.com
Hi,

Please give it a try to use `1.4.2.rc` which includes following fix.

https://github.com/rsim/oracle-enhanced/issues/163

--
Yasuo Honda
> --
> You received this message because you are subscribed to the Google Groups
> "Oracle enhanced adapter for ActiveRecord" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/oracle-enhanced/-/TrXn0hl9S30J.
> To post to this group, send email to oracle-...@googlegroups.com.
> To unsubscribe from this group, send email to
> oracle-enhanc...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/oracle-enhanced?hl=en.

tho...@randspringer.de

unread,
Dec 7, 2012, 11:15:20 AM12/7/12
to oracle-...@googlegroups.com
Hi,
 
just for your info: The workaround https://gist.github.com/2471698 did work for me.
 
But I could not install the gem-version you suggested:
 
~/bin$ gem install activerecord-oracle_enhanced-adapter -v 1.4.2.rc
ERROR:  Could not find a valid gem 'activerecord-oracle_enhanced-adapter' (= 1.4.2.rc) in any repository
~/bin$ gem install activerecord-oracle_enhanced-adapter -v 1.4.2
ERROR:  Could not find a valid gem 'activerecord-oracle_enhanced-adapter' (= 1.4.2) in any repository
ERROR:  Possible alternatives: activerecord-oracle_enhanced-adapter
~/bin$ gem install activerecord-oracle_enhanced-adapter -v 1.4.2rc
ERROR:  Could not find a valid gem 'activerecord-oracle_enhanced-adapter' (= 1.4.2rc) in any repository
ERROR:  Possible alternatives: activerecord-oracle_enhanced-adapter
~/bin$ gem install activerecord-oracle_enhanced-adapter -v 1.4.1
Successfully installed activerecord-oracle_enhanced-adapter-1.4.1
1 gem installed
 
?!
 
Thomas

Yasuo Honda <yasuo...@gmail.com> hat am 5. Dezember 2012 um 20:26 geschrieben:

Benjamin Ortega

unread,
Dec 7, 2012, 11:23:00 AM12/7/12
to oracle-...@googlegroups.com
Thomas, "1.4.2.rc1" is what you are looking for.

Any word on what we're waiting for before a final 1.4.2 release? Besides merging my pull request, of course. :)

- Ben

Yasuo Honda

unread,
Dec 7, 2012, 11:24:45 AM12/7/12
to oracle-...@googlegroups.com
Sorry `1.4.2.rc1` I meant to say.

https://groups.google.com/forum/?fromgroups=#!topic/oracle-enhanced/mU37TyUdWJY
--
Yasuo Honda

tho...@randspringer.de

unread,
Dec 10, 2012, 1:48:28 AM12/10/12
to oracle-...@googlegroups.com
Hi,
 
now I installed the 1.4.2.rc but it did not work without the workaround:
 
 
Thomas

Benjamin Ortega <ben.o...@gmail.com> hat am 7. Dezember 2012 um 17:23 geschrieben:

Yasuo Honda

unread,
Dec 10, 2012, 1:20:51 PM12/10/12
to oracle-...@googlegroups.com, tho...@randspringer.de
Thanks for the update. 

If I understand correctly, the pull request https://github.com/rsim/oracle-enhanced/issues/163 should address the same issue what https://gist.github.com/2471698 did. Ping @bbrowning at github at the issue#163

Yasuo Honda

unread,
Dec 10, 2012, 3:15:21 PM12/10/12
to oracle-...@googlegroups.com, tho...@randspringer.de
According to @bbrowning at github, 

>> Yes - they both should solve this issue. I can't think of any reason why that workaround would fix things if the change in this pull request does not.

So I have no more information about this. 
Reply all
Reply to author
Forward
0 new messages