Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Problems with Struts DataSources ?!

 
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ranchers,
Has anyone encountered the problem with the Struts DataSources connection wherein it does not execute any SQL query at all? This happens when you try to execute a second SQL query on the same connection object. The first query runs fine, but the second doesn't. But there were really some weird instances where any SQL query doesn't execute at all
Any replies would be greatly appreciated. Thanks a lot!
-- Ex Animo Java!
-- Val
 
Ranch Hand
Posts: 2166
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Val,
I am using first
- SQL query
- SQL insert
- SQL insert
in the same connection.
I have encountered no problems. I use access as a database (not a good idea btw. will change to mysql soon. A lot of stuff is not supported by ODBC-Bridge, like forward navigating in resultsets, or how its called).
Have you checked the log-file. Maybe there is another problem?
Axel
 
Val Pecaoco
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Axel,
Thanks for the reply. Unfortunately the logs have been replaced with new entries after I restarted Tomcat (checking the log files is one thing I overlooked ). I'm using the following sequence:
1) SQL query
2) SQL update
It's in the update that the connection chokes. When I test it with the conventional way of obtaining the Connection object, it works fine. BTW I'm using SQL Server 7.0. I'm thinking of Using PoolMan or DBConnectionBroker instead.
Ex Animo Java!
-- Val
 
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic