Problem initializing ConnectionPool with Login Failed

Hi, we are using weblogic 8.1 on solaris with sybase 12.5, Our application initialize
several connection pools to several sybase databases. We are having problem only
with one of connection pool, we always get "JZ00L: Login failed. Examine the
SQLWarnings chained to this exception for the reason(s)." We are pretty sure the
user id and password is correct, they are all the same as other databases which
we don't have problem. The setting is pretty much the same other than hostName,
port and database name. we even set initialCapacity to 1, it still failed? What
could be the reeason? and how can make weblogic spit out the Syabse specific SQLWarning
which could give us some clue?

Any help is appreciated!

Thanks,


Kevin

Kevin wrote:
[color=blue]
> Hi, we are using weblogic 8.1 on solaris with sybase 12.5, Our application initialize
> several connection pools to several sybase databases. We are having problem only
> with one of connection pool, we always get "JZ00L: Login failed. Examine the
> SQLWarnings chained to this exception for the reason(s)." We are pretty sure the
> user id and password is correct, they are all the same as other databases which
> we don't have problem. The setting is pretty much the same other than hostName,
> port and database name. we even set initialCapacity to 1, it still failed? What
> could be the reeason? and how can make weblogic spit out the Syabse specific SQLWarning
> which could give us some clue?
>
> Any help is appreciated![/color]

That is coming straight from the DBMS, meaning the user/password is most likelly incorrect.
Joe
[color=blue]
>
> Thanks,
>
>
> Kevin[/color]

We can login using the same user id and password through syabse's SQL window. That
Error not neccessarily means userid and password problem. We had experience when
there weren't enough connections for initial connection allocation we got the
same error. That's why it would be helpful to see the real SQLWarning msg. Is
there anyway to make Weblogic to print out that?

Kevin
Joe Weinstein <joeNOSPAM@bea.com> wrote:[color=blue]
>
>
>Kevin wrote:
>[color=green]
>> Hi, we are using weblogic 8.1 on solaris with sybase 12.5, Our application[/color]
>initialize[color=green]
>> several connection pools to several sybase databases. We are having[/color]
>problem only[color=green]
>> with one of connection pool, we always get "JZ00L: Login failed. Examine[/color]
>the[color=green]
>> SQLWarnings chained to this exception for the reason(s)." We are pretty[/color]
>sure the[color=green]
>> user id and password is correct, they are all the same as other databases[/color]
>which[color=green]
>> we don't have problem. The setting is pretty much the same other than[/color]
>hostName,[color=green]
>> port and database name. we even set initialCapacity to 1, it still[/color]
>failed? What[color=green]
>> could be the reeason? and how can make weblogic spit out the Syabse[/color]
>specific SQLWarning[color=green]
>> which could give us some clue?
>>
>> Any help is appreciated![/color]
>
>That is coming straight from the DBMS, meaning the user/password is
>most likelly incorrect.
>Joe
>[color=green]
>>
>> Thanks,
>>
>>
>> Kevin[/color]
>[/color]

Kevin wrote:
[color=blue]
> We can login using the same user id and password through syabse's SQL window. That
> Error not neccessarily means userid and password problem. We had experience when
> there weren't enough connections for initial connection allocation we got the
> same error. That's why it would be helpful to see the real SQLWarning msg. Is
> there anyway to make Weblogic to print out that?[/color]

Interesting... What does a tiny standalone program using sybase's driver alone
show with those connection properties? Unfortunately, that error message from the
Sybase driver is a bit silly if it says to check the SQLWarning, because the
only access to SQLWarnings in JDBC is via the Connection.getWarnings() call,
which we wouldn't need to call if the driver returned us a connection to make
the call ;)...

Joe
[color=blue]
>
> Kevin
> Joe Weinstein <joeNOSPAM@bea.com> wrote:
>[color=green]
>>
>>Kevin wrote:
>>
>>[color=darkred]
>>>Hi, we are using weblogic 8.1 on solaris with sybase 12.5, Our application[/color]
>>
>>initialize
>>[color=darkred]
>>>several connection pools to several sybase databases. We are having[/color]
>>
>>problem only
>>[color=darkred]
>>>with one of connection pool, we always get "JZ00L: Login failed. Examine[/color]
>>
>>the
>>[color=darkred]
>>>SQLWarnings chained to this exception for the reason(s)." We are pretty[/color]
>>
>>sure the
>>[color=darkred]
>>>user id and password is correct, they are all the same as other databases[/color]
>>
>>which
>>[color=darkred]
>>>we don't have problem. The setting is pretty much the same other than[/color]
>>
>>hostName,
>>[color=darkred]
>>>port and database name. we even set initialCapacity to 1, it still[/color]
>>
>>failed? What
>>[color=darkred]
>>>could be the reeason? and how can make weblogic spit out the Syabse[/color]
>>
>>specific SQLWarning
>>[color=darkred]
>>>which could give us some clue?
>>>
>>>Any help is appreciated![/color]
>>
>>That is coming straight from the DBMS, meaning the user/password is
>>most likelly incorrect.
>>Joe
>>
>>[color=darkred]
>>>Thanks,
>>>
>>>
>>>Kevin[/color]
>>[/color]
>[/color]

It turns out there are something in the "Properties" attrib that this Sybase server
didn't like. After we took out most of the them, (only leave the user, sqlinitstr,
applicationname) , then it starts to work.

Thanks,


Joe Weinstein <joeNOSPAM@bea.com> wrote:[color=blue]
>
>
>Kevin wrote:
>[color=green]
>> We can login using the same user id and password through syabse's SQL[/color]
>window. That[color=green]
>> Error not neccessarily means userid and password problem. We had experience[/color]
>when[color=green]
>> there weren't enough connections for initial connection allocation[/color]
>we got the[color=green]
>> same error. That's why it would be helpful to see the real SQLWarning[/color]
>msg. Is[color=green]
>> there anyway to make Weblogic to print out that?[/color]
>
>Interesting... What does a tiny standalone program using sybase's driver
>alone
>show with those connection properties? Unfortunately, that error message
>from the
>Sybase driver is a bit silly if it says to check the SQLWarning, because
>the
>only access to SQLWarnings in JDBC is via the Connection.getWarnings()
>call,
>which we wouldn't need to call if the driver returned us a connection
>to make
>the call ;)...
>
>Joe
>[color=green]
>>
>> Kevin
>> Joe Weinstein <joeNOSPAM@bea.com> wrote:
>>[color=darkred]
>>>
>>>Kevin wrote:
>>>
>>>
>>>>Hi, we are using weblogic 8.1 on solaris with sybase 12.5, Our application
>>>
>>>initialize
>>>
>>>>several connection pools to several sybase databases. We are having
>>>
>>>problem only
>>>
>>>>with one of connection pool, we always get "JZ00L: Login failed.[/color][/color]
>Examine[color=green][color=darkred]
>>>
>>>the
>>>
>>>>SQLWarnings chained to this exception for the reason(s)." We are pretty
>>>
>>>sure the
>>>
>>>>user id and password is correct, they are all the same as other databases
>>>
>>>which
>>>
>>>>we don't have problem. The setting is pretty much the same other than
>>>
>>>hostName,
>>>
>>>>port and database name. we even set initialCapacity to 1, it still
>>>
>>>failed? What
>>>
>>>>could be the reeason? and how can make weblogic spit out the Syabse
>>>
>>>specific SQLWarning
>>>
>>>>which could give us some clue?
>>>>
>>>>Any help is appreciated!
>>>
>>>That is coming straight from the DBMS, meaning the user/password is
>>>most likelly incorrect.
>>>Joe
>>>
>>>
>>>>Thanks,
>>>>
>>>>
>>>>Kevin
>>>[/color]
>>[/color]
>[/color]

Thanks for the comments, It helped us narrowed down the cause of a similar issue (if not the same?) to the packet size set in the weblogic jdbc configuration xml being larger than the allowed packet size on the database server.