Thanks for the response. Those settings have already been previously
applied as we are not experiencing issues with getting the Type 4
driver connected. The issues we are experiencing involves getting
connections consistently from the connection pool after connecting
the driver (timeouts, not being able to get valid connections from
the pool after a period of time, etc.). I have cataloged the
majority of our issues and detail in the bug:
https://glassfish.dev.java.net/issues/show_bug.cgi?submit=Go+to&id=1377
I have also updated it to include some of the information from the
forum posts.
Regards,
Iran.
On Nov 14, 2006, at 12:25 PM, Lance J. Andersen wrote:
> Make sure you set the DB2 driver property driverType = 4 when you
> configure the DB2 driver connection pool as i believe this defaults
> to 2 (type 2).
>
> Shreedhar Ganapathy wrote:
>> cc'ing the dev and users aliases for broader audience and any
>> further ideas.
>>
>> Shreedhar Ganapathy wrote:
>>> Hi Iran
>>> Could you try the solution in this forum entry?
>>> http://forum.java.sun.com/thread.jspa?
>>> threadID=730463&messageID=4203771
>>>
>>> If it works please let us know, I will follow up with the
>>> appropriate team for doc updates.
>>>
>>> regards
>>> Shreedhar
>>>
>>> iran_at_nc.rr.com wrote:
>>>> Thanks for the reply. We are already familiar with the Type 2
>>>> driver
>>>> documentation. It requires you to catalog your DB2 database on the
>>>> application server machine and have the native driver *.so or *.dll
>>>> available in the application server classpath. This is not our
>>>> desired
>>>> configuration. The only listed Type 4 driver is the Sun driver
>>>> made
>>>> from Data Direct drivers. Those drivers are only available for
>>>> client
>>>> development stations unless we are missing something. From our
>>>> research, it seems you'd have to buy server licenses which we
>>>> are trying
>>>> to avoid as we have the DB2 drivers that work elsewhere.
>>>>
>>>> Iran.
>>>>
>>>> ----- Original Message -----
>>>> From: sreeni <smunnangi_at_gmail.com>
>>>> Date: Sunday, November 12, 2006 8:29 pm
>>>> Subject: Re: DB2 JDBC Type 4 Support?
>>>> To: issues_at_glassfish.dev.java.net
>>>> Cc: quality_at_glassfish.dev.java.net
>>>>
>>>>
>>>>> Pl. refer to Sun Java System Application Server 9.0 doc.
>>>>> specifically on
>>>>> support for
>>>>> IBM DB2 8.1 and 8.2 Type 2 Driver
>>>>>
>>>>> http://docs.sun.com/app/docs/doc/819-3658/6n5s5nklf?a=view
>>>>>
>>>>> thanks
>>>>> sreeni
>>>>>
>>>>>
>>>>> Iran Hutchinson wrote:
>>>>>
>>>>>> We are trying to use GlassFish for several large projects(ranging
>>>>>>
>>>>> from
>>>>>
>>>>>> 3,000 users to > 200,000) and one database we have to connect to
>>>>>>
>>>>> is
>>>>>
>>>>>> DB2 8.2. The URL:
>>>>>>
>>>>> https://glassfish.dev.java.net/quality/matrix.html
>>>>>
>>>>>> says this has been tested but there is no documentation for
>>>>>> configuring a Type 4 JDBC driver for DB2 only a Type 2 driver
>>>>>>
>>>>> which we
>>>>>
>>>>>> don't use. We are experiencing several issues with connection
>>>>>> pooling configuration and usage ranging from timeouts on
>>>>>>
>>>>> connections
>>>>>
>>>>>> where there should be none to not being able to get a new
>>>>>>
>>>>> connection
>>>>>
>>>>>> after a period of time. One killer is that we cannot connect to
>>>>>>
>>>>> a
>>>>>
>>>>>> database that we only have access to stored procedures, we cannot
>>>>>> configure it to validate on "table" as we have no access to
>>>>>>
>>>>> tables.
>>>>>
>>>>>> All the other validation methods lead to a myriad TCP/IP
>>>>>>
>>>>> disconnect
>>>>>
>>>>>> errors.
>>>>>>
>>>>>> We filed a bug to document some of what we are experiencing:
>>>>>>
>>>>>>
>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?submit=Go
>>>>> +to&id=1377
>>>>>
>>>>>> . Is the DB2 JDBC Type 4 driver supported for connection pooling
>>>>>>
>>>>> or
>>>>>
>>>>>> will it be supported? We are hoping it is a configuration issue,
>>>>>>
>>>>> but
>>>>>
>>>>>> can't get confirmation on that either. We have not had this
>>>>>>
>>>>> issue on
>>>>>
>>>>>> the other application servers with the IBM DB2 driver, so we were
>>>>>> assuming either a bug or a miss-configuration. We'd be willing
>>>>>>
>>>>> to
>>>>>
>>>>>> help in anyway needed.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Iran.
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -
>>>>>>
>>>>> ---
>>>>>
>>>>>> To unsubscribe, e-mail: issues-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: issues-
>>>>>> help_at_glassfish.dev.java.net
>>>>>>
>>>>>>
>>>>> ------------------------------------------------------------------
>>>>> --
>>>>> -
>>>>> To unsubscribe, e-mail: issues-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: issues-
>>>>> help_at_glassfish.dev.java.net
>>>>>
>>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: issues-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: issues-help_at_glassfish.dev.java.net
>>>>
>>>>