Steve Ebersole wrote:
That or we could get these DB instances externally accessible rather
than needing VPN + tunneling + black-voodoo-magic ;)
Only VPN. Inside the VPN (currently JBoss, soon the Red Hat one) you can
directly access hosts in the QA lab on any port. No magic (only a great
luck ;)
Well, I'd need to know the test that locks up the DB (and the
results
are not pushing to the CC site). The strange part is that neither of
these tests is even testing concurrent access; they (should) deal with a
single connection at a time. Is locking in Sybase so good that a
connection can block itself ;)
hmmm... I can't imagine why. I see many connections, one of them in a
state "lock wait". Killing one by one and testsuite continues at some point.
I think it would be best to run the testsuite by yourself. If you need
any information about QA lab access, where to find jdbc drivers etc. you
may contact me.
-----Original Message-----
From: Aleksandar Kostadinov [mailto:akostadinov@jboss.org]
Sent: Wednesday, January 24, 2007 2:21 PM
To: Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] sybase
See answers below. btw if you are inside jboss VPN, you could run the
testsuite on the sybase db from your local computer or from one of the
QA machines.
Steve Ebersole wrote:
>Which specific test methods in the two tests you mention fail with
locking issues?
Don't know.
>Also what is the exact Sybase product and version you are using?
Adaptive Server Enterprise/12.5.2/EBF
>What is the isolation of the Sybase JDBC connections?
Default? We can add this to hibernate.properties
>-----Original Message-----
>From: Aleksandar Kostadinov [mailto:akostadinov@jboss.org]
>Sent: Wednesday, January 24, 2007 9:21 AM
>To: Steve Ebersole
>Cc: hibernate-dev(a)lists.jboss.org
>Subject: Re: [hibernate-dev] sybase
>
>Are you going to do something about sybase or leave it at least for
now?
>Thanks,
>Aleksandar
>
>---------------------------------------------
>I cleaned up database again and ran the following command:
>./build.sh
>-Djar.driver=/opt/jdbc-drivers/jConnect-6_0/classes/jconn3.jar
>-Dhibernate.test.validatefailureexpected=true junitreport
>
>The testsuite locked on these testsuites:
>org.hibernate.test.connections.SuppliedConnectionTest
>org.hibernate.test.connections.ThreadLocalCurrentSessionTest
>
>hibernate.properties contains:
>hibernate.dialect org.hibernate.dialect.SybaseDialect
>hibernate.connection.driver_class com.sybase.jdbc3.jdbc.SybDriver
>hibernate.connection.username <user>
>hibernate.connection.password <pass>
>hibernate.connection.url jdbc:sybase:Tds:dev01:4100/<db>
>
>btw. there were many failing tests
>
>Aleksandar Kostadinov wrote:
>
>
>
>>In the new year I could do more investigations about that. For now I
>>can only tell there are more than one.
>>
>>Steve Ebersole wrote:
>>
>>
>>
>>>I do not have a local Sybase install against which to test. However,
>>>that would not surprise me. Can you tell me the tests during which
it
>>>locks up?
>>>
>>>-----Original Message-----
>>>From: Aleksandar Kostadinov [mailto:akostadinov@jboss.org]
>>>Sent: Friday, December 22, 2006 1:13 PM
>>>To: Steve Ebersole
>>>Cc: hibernate-dev(a)lists.jboss.org
>>>Subject: Re: [hibernate-dev] sybase
>>>
>>>Using either 6.05 or 5.5 results in locks.
>>>Are you able to run the testsuite against sybase at all?
>>>
>>>Aleksandar Kostadinov wrote:
>>>
>>>
>>>
>>>
>>>
>>>>Should I use the latest jconnect6.05 for sybase tests?
>>>>
>>>>Thanks,
>>>>Aleksandar
>>>>_______________________________________________
>>>>hibernate-dev mailing list
>>>>hibernate-dev(a)lists.jboss.org
>>>>https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>----------------------------------------------------------------------
-
>-
>
>
>>_______________________________________________
>>hibernate-dev mailing list
>>hibernate-dev(a)lists.jboss.org
>>https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
>
>