struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Grigsby <strutsu...@tgrigsby.com>
Subject Re: "specified DSN contains an architecture mismatch"
Date Sun, 13 Dec 2009 21:13:00 GMT

The application runs on Oracle, MySQL, or SQL Server, depending on the 
distro, and on various versions of these depending on the version and 
type of OS.  MySQL is our preferred database.  We use JDBC to simplify 
the connection process.

TG

Wes Wannemacher wrote:
> Why use odbc? Mysql has a top notch jdbc driver.
>
> On 12/11/09, Todd Grigsby <strutsuser@tgrigsby.com> wrote:
>   
>> Yes, thank you, I know that.  My question has to do with the
>> architecture mismatch.  All the documentation I've seen on this
>> indicates that there is a 32-bit/64-bit issue, but I'll be darned if I
>> know which piece is at fault.  Given the versions of the various parts,
>> does anyone have any idea what I need to do to be able to talk to MySQL?
>>
>> TG
>>
>> Martin Gainty wrote:
>>     
>>> you're using InitialContext to lookup a DataSource registered to JNDI
>>> registry
>>>
>>> Martin Gainty
>>>
>>>       
>>>>>   Context context = new InitialContext();
>>>>>   DataSource ds =
>>>>> (DataSource)context.lookup("java:/comp/env/jdbc/odbc/tgecorp");
>>>>>   Connection conn = datasource.getConnection();
>>>>>
>>>>> ...
>>>>>
>>>>> The last line throws an exception with the following message:  "The
>>>>> specified DSN contains an architecture mismatch between the Driver and
>>>>> Application."
>>>>>
>>>>>           
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>     
>
>
>   


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message