[hibernate-dev] hibernate-mysql-testsuite Build Timed Out
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061106010001 BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 11/06/2006 01:00:01Time to build: Last changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 2088)10717added[EMAIL PROTECTED]//trunk/Hibernate3/lib/ehcache-1.2.3.jarHHH-2209 ehcache.jar is old and does not contain the SingletonCacheProvider which are advised in exception messages10717modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/cache/EhCache.javaHHH-2209 ehcache.jar is old and does not contain the SingletonCacheProvider which are advised in exception messages10717modified[EMAIL PROTECTED]//trunk/Hibernate3/lib/version.propertiesHHH-2209 ehcache.jar is old and does not contain the SingletonCacheProvider which are advised in exception messages10715added[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/jdbc/ConnectionWrapper.javaHHH-1737 : ConnectionWrapper10715modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/jdbc/BorrowedConnectionProxy.javaHHH-1737 : ConnectionWrapper10713added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/tool/Team.javamerged HHH-1629 and HHH-2208 from 3.210713modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/tool/hbm2ddl/DatabaseMetadata.javamerged HHH-1629 and HHH-2208 from 3.210713added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/tool/Team.hbm.xmlmerged HHH-1629 and HHH-2208 from 3.210713modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/tool/hbm2ddl/TableMetadata.javamerged HHH-1629 and HHH-2208 from 3.210713added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/toolmerged HHH-1629 and HHH-2208 from 3.210713added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/tool/TestSchemaTools.javamerged HHH-1629 and HHH-2208 from 3.210713modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/cfg/Configuration.javamerged HHH-1629 and HHH-2208 from 3.210712added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/cfg/CacheableFileTest.javaHHH-2108 : fixed cacheable files10712added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/cfg/Cacheable.hbm.xmlHHH-2108 : fixed cacheable files10712added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/cfgHHH-2108 : fixed cacheable files10711modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/cfg/Configuration.javaHHH-2108 : fixed cacheable files10704modified[EMAIL PROTECTED]//trunk/Hibernate3/doc/reference/en/modules/filters.xmlHHH-2127 : document default filter conditions10698modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SessionFactoryImpl.javaHHH-1767 : incorrect warnings when building collection caches10696modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/engine/StatefulPersistenceContext.javaHHH-1756 : BatchFetchQueue and evicted proxies10694added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/domain/Problematic.hbm.xmladded tests specific for lazy properties using user-type mappings10694added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestLazyPropertyCustomTypeExecutable.javaadded tests specific for lazy properties using user-type mappings10694added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/domain/CustomBlobType.javaadded tests specific for lazy properties using user-type mappings10694modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase.javaadded tests specific for lazy properties using user-type mappings10694modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/AbstractExecutable.javaadded tests specific for lazy properties using user-type mappings10694added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/domain/Problematic.javaadded tests specific for lazy properties using user-type mappings10690modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/type/SerializableType.javaHHH-2135 : SerializableType change for Terradata support10688modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SessionImpl.javaHHH-2206 - SessionImpl serialization10680modifiedepbernard//trunk/Hibernate3/src/org/hibernate/action/EntityDeleteAction.javaHHH-2203 make Post*Event extends AbstractEvent10680modifiedepbernard//trunk/Hibernate3/src/org/hibernate/event/PostDeleteEvent.javaHHH-2203 make Post*Event extends AbstractEvent10680modifiedepbernard//trunk/Hibernate3/src/org/hibernate/action/EntityInsertAction.javaHHH-2203 make Post*Event extends AbstractEvent10680modifiedepbernard//trunk/Hibernate3/src/org/hibernate/event/PostInsertEvent.javaHHH-2203 make Post*Event extends AbstractE
[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061106040010 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 11/06/2006 04:00:10Time to build: 11 minutes 5 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (915) Total Errors and Failures: (141)testRefreshCascadeorg.hibernate.test.cascade.RefreshTesttestBorrowedConnectionsorg.hibernate.test.connections.AggressiveReleaseTesttestBorrowedConnectionsorg.hibernate.test.connections.CurrentSessionConnectionTesttestPojoRetreivalorg.hibernate.test.entity.MultiRepresentationTesttestDom4jRetreivalorg.hibernate.test.entity.MultiRepresentationTesttestDom4jSaveorg.hibernate.test.entity.MultiRepresentationTesttestDom4jHQLorg.hibernate.test.entity.MultiRepresentationTesttestIntegrityViolationorg.hibernate.test.exception.SQLExceptionConversionTesttestBadGrammarorg.hibernate.test.exception.SQLExceptionConversionTesttestSequentialSelectsOptionalDataorg.hibernate.test.join.JoinTesttestJoinedSubclassorg.hibernate.test.joinedsubclass.JoinedSubclassTesttestCreateorg.hibernate.test.legacy.FooBarTesttestUpdateOrderorg.hibernate.test.legacy.FooBarTesttestPolymorphismorg.hibernate.test.legacy.FooBarTesttestFetchListorg.hibernate.test.legacy.FooBarTesttestOrderByorg.hibernate.test.legacy.FooBarTesttestJoinorg.hibernate.test.legacy.FooBarTesttestSaveOrUpdateCopyAnyorg.hibernate.test.legacy.FooBarTesttestRefreshProxyorg.hibernate.test.legacy.FooBarTesttestOnCascadeDeleteorg.hibernate.test.legacy.FooBarTesttestRemoveFromIdbagorg.hibernate.test.legacy.FooBarTesttestLoadorg.hibernate.test.legacy.FooBarTesttestDereferenceLazyCollectionorg.hibernate.test.legacy.FooBarTesttestMoveLazyCollectionorg.hibernate.test.legacy.FooBarTesttestCriteriaCollectionorg.hibernate.test.legacy.FooBarTesttestCascadeDeleteDetachedorg.hibernate.test.legacy.FooBarTesttestForeignKeysorg.hibernate.test.legacy.FooBarTesttestNonlazyCollectionorg.hibernate.test.legacy.FooBarTesttestReuseDeletedCollectionorg.hibernate.test.legacy.FooBarTesttestPropertyReforg.hibernate.test.legacy.FooBarTesttestQueryCollectionOfValuesorg.hibernate.test.legacy.FooBarTesttestBatchLoadorg.hibernate.test.legacy.FooBarTesttestFetchInitializedCollectionorg.hibernate.test.legacy.FooBarTesttestLateCollectionAddorg.hibernate.test.legacy.FooBarTesttestUpdateorg.hibernate.test.legacy.FooBarTesttestListRemoveorg.hibernate.test.legacy.FooBarTesttestFetchInitializedCollectionDupeorg.hibernate.test.legacy.FooBarTesttestSortablesorg.hibernate.test.legacy.FooBarTesttestBagOneToManyorg.hibernate.test.legacy.FooBarTesttestManyToManyBagorg.hibernate.test.legacy.FooBarTesttestIdBagorg.hibernate.test.legacy.FooBarTesttestForceOuterJoinorg.hibernate.test.legacy.FooBarTesttestEmptyCollectionorg.hibernate.test.legacy.FooBarTesttestOneToOneGeneratororg.hibernate.test.legacy.FooBarTesttestCustomorg.hibernate.test.legacy.FooBarTesttestSaveAddDeleteorg.hibernate.test.legacy.FooBarTesttestDynaorg.hibernate.test.legacy.FooBarTesttestAfterDeleteorg.hibernate.test.legacy.FooBarTesttestCollectionWhereorg.hibernate.test.legacy.FooBarTesttestCollectionCacheorg.hibernate.test.legacy.FooBarTesttestPersistCollectionsorg.hibernate.test.legacy.FooBarTesttestSaveFlushorg.hibernate.test.legacy.FooBarTesttestCreateUpdateorg.hibernate.test.legacy.FooBarTesttestUpdateCollectionsorg.hibernate.test.legacy.FooBarTesttestCallbackorg.hibernate.test.legacy.FooBarTesttestRemoveContainsorg.hibernate.test.legacy.FooBarTesttestCollectionOfSelforg.hibernate.test.legacy.FooBarTesttestDeleteRecursiveorg.hibernate.test.legacy.FooBarTesttestReachabilityorg.hibernate.test.legacy.FooBarTesttestPersistentLifecycleorg.hibernate.test.legacy.FooBarTesttestIteratorsorg.hibernate.test.legacy.FooBarTesttestVersionedCollectionsorg.hibernate.test.legacy.FooBarTesttestUpdateFromTransientorg.hibernate.test.legacy.FooBarTesttestArraysOfTimesorg.hibernate.test.legacy.FooBarTesttestNoForeignKeyViolationsorg.hibernate.test.legacy.FooBarTesttestLazyCollectionsorg.hibernate.test.legacy.FooBarTesttestNewSessionLifecycleorg.hibernate.test.legacy.FooBarTesttestDisconnectorg.hibernate.test.legacy.FooBarTesttestManyToOneorg.hibernate.test.legacy.FooBarTesttestSaveDeleteorg.hibernate.test.legacy.FooBarTesttestProxyArrayorg.hibernate.test.legacy.FooBarTesttestCacheorg.hibernate.test.legacy.FooBarTesttestFindLoadorg.hibernate.test.legacy.FooBarTesttestRefreshorg.hibernate.test.legacy.FooBarTesttestVetoorg.hibernate.test.legacy.FooBarTesttestSerializableTypeorg.hibernate.test.legacy.FooBarTesttestCachedCollectionorg.hibernat
[hibernate-dev] Connection proxy error
Hi Steve,
After updating from svn I get the following in alot of tests:
java.lang.IllegalArgumentException: interface
org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
at
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnectionProxy.java:56)
at
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.java:163)
at org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
at
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnections(AggressiveReleaseTest.java:210)
I fixed it by changing:
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Connection.class.getClassLoader(),
PROXY_INTERFACES,
handler
);
}
to
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Thread.currentThread().getContextClassLoader(),
PROXY_INTERFACES,
handler
);
}
Connection.class is always loaded via the boot/system clasloader so I
don't get how using its classloader
when generating the proxy would ever work ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] Connection proxy error
Context classloader can be null...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
Andersen
Sent: Monday, November 06, 2006 5:54 AM
To: hibernate-dev@lists.jboss.org
Subject: [hibernate-dev] Connection proxy error
Hi Steve,
After updating from svn I get the following in alot of tests:
java.lang.IllegalArgumentException: interface
org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
at
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
ionProxy.java:56)
at
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
java:163)
at
org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
at
org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
at
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
ions(AggressiveReleaseTest.java:210)
I fixed it by changing:
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Connection.class.getClassLoader(),
PROXY_INTERFACES,
handler
);
}
to
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Thread.currentThread().getContextClassLoader(),
PROXY_INTERFACES,
handler
);
}
Connection.class is always loaded via the boot/system clasloader so I
don't get how using its classloader
when generating the proxy would ever work ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] ant junitreport: Success rate 79.56%
As part of release engineering, are the junit tests run in at least one configuration (JVM, Java version, JDBC driver, SQL server implementation) to prove they pass ? If so what configuration is used ? Many of the tests fail for my configuration, Success rate 79.56%, is this to be expected ? My configuration: * Hibernate 3.2.0-ga * JVM: Sun 1.5.0 x86_64/Linux * JDBC Driver: mysql-connector-java-3.1.12-bin.jar * SQL Server: MySQL 4.1.15 Out of the box, with Hypersonic SQL Success rate is 7.33%. What is the purpose of the unit tests that are shipped with the product and are the quality of those tests currently meeting the goals of that purpose ? I would like to think that if a unit test makes it into the distribution to be shipped with the product that as a user I could gain some confidence in knowing that the specific scenario that the unit test embodies is verified as working against each subsequent release of the product. Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Connection proxy error
On Mon, 06 Nov 2006 14:11:46 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
Context classloader can be null...
But it should then be done in the classloader that loaded hibernate; not
the system classpath loader which Connection.class will be.
You don't get this error at your end ?
At least i'm not the only one
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1629#action_25145
;)
/max
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
Andersen
Sent: Monday, November 06, 2006 5:54 AM
To: hibernate-dev@lists.jboss.org
Subject: [hibernate-dev] Connection proxy error
Hi Steve,
After updating from svn I get the following in alot of tests:
java.lang.IllegalArgumentException: interface
org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
at
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
ionProxy.java:56)
at
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
java:163)
at
org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
at
org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
at
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
ions(AggressiveReleaseTest.java:210)
I fixed it by changing:
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Connection.class.getClassLoader(),
PROXY_INTERFACES,
handler
);
}
to
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Thread.currentThread().getContextClassLoader(),
PROXY_INTERFACES,
handler
);
}
Connection.class is always loaded via the boot/system clasloader so I
don't get how using its classloader
when generating the proxy would ever work ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] Connection proxy error
I committed the fix. Just pointing out that your solution dangerously
looks correct...
-Original Message-
From: Max Andersen
Sent: Monday, November 06, 2006 7:28 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxy error
On Mon, 06 Nov 2006 14:11:46 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
> Context classloader can be null...
But it should then be done in the classloader that loaded hibernate; not
the system classpath loader which Connection.class will be.
You don't get this error at your end ?
At least i'm not the only one
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1629#actio
n_25145
;)
/max
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
> Andersen
> Sent: Monday, November 06, 2006 5:54 AM
> To: hibernate-dev@lists.jboss.org
> Subject: [hibernate-dev] Connection proxy error
>
> Hi Steve,
>
> After updating from svn I get the following in alot of tests:
>
> java.lang.IllegalArgumentException: interface
> org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
> at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
> at
>
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
> ionProxy.java:56)
> at
>
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
> java:163)
> at
> org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
> at
> org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
> at
>
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
> ions(AggressiveReleaseTest.java:210)
>
> I fixed it by changing:
>
> public static Connection generateProxy(ConnectionManager
> connectionManager) {
> BorrowedConnectionProxy handler = new
> BorrowedConnectionProxy( connectionManager );
> return ( Connection ) Proxy.newProxyInstance(
> Connection.class.getClassLoader(),
> PROXY_INTERFACES,
> handler
> );
> }
>
> to
>
> public static Connection generateProxy(ConnectionManager
> connectionManager) {
> BorrowedConnectionProxy handler = new
> BorrowedConnectionProxy( connectionManager );
> return ( Connection ) Proxy.newProxyInstance(
>
> Thread.currentThread().getContextClassLoader(),
> PROXY_INTERFACES,
> handler
> );
> }
>
> Connection.class is always loaded via the boot/system clasloader so I
> don't get how using its classloader
> when generating the proxy would ever work ?
>
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] ant junitreport: Success rate 79.56%
Thee pass rate for tests that is not named *FailureExpected is 100% on hsql. Same for alot of other db's. (i recently ran the testsuite against oracle, mysql and postgresql) And the test suite is constantly maintained. /max As part of release engineering, are the junit tests run in at least one configuration (JVM, Java version, JDBC driver, SQL server implementation) to prove they pass ? If so what configuration is used ? Many of the tests fail for my configuration, Success rate 79.56%, is this to be expected ? My configuration: * Hibernate 3.2.0-ga * JVM: Sun 1.5.0 x86_64/Linux * JDBC Driver: mysql-connector-java-3.1.12-bin.jar * SQL Server: MySQL 4.1.15 Out of the box, with Hypersonic SQL Success rate is 7.33%. What is the purpose of the unit tests that are shipped with the product and are the quality of those tests currently meeting the goals of that purpose ? I would like to think that if a unit test makes it into the distribution to be shipped with the product that as a user I could gain some confidence in knowing that the specific scenario that the unit test embodies is verified as working against each subsequent release of the product. Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Connection proxy error
if we want to be completely safe then
Thread.currentThread().getContextClassLoader()==null?Environment.class.getClassLoader():Thread.currentThread().getContextClassLoader()
would be better since in the case contextclassloader == null then
Connection.class.getClassLoader() is most likely null or point to a
"too-high"
classloader thus using the classloader of Hibernate self would be the best
fallback.
/max
I committed the fix. Just pointing out that your solution dangerously
looks correct...
-Original Message-
From: Max Andersen
Sent: Monday, November 06, 2006 7:28 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxy error
On Mon, 06 Nov 2006 14:11:46 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
Context classloader can be null...
But it should then be done in the classloader that loaded hibernate; not
the system classpath loader which Connection.class will be.
You don't get this error at your end ?
At least i'm not the only one
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1629#actio
n_25145
;)
/max
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
Andersen
Sent: Monday, November 06, 2006 5:54 AM
To: hibernate-dev@lists.jboss.org
Subject: [hibernate-dev] Connection proxy error
Hi Steve,
After updating from svn I get the following in alot of tests:
java.lang.IllegalArgumentException: interface
org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
at
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
ionProxy.java:56)
at
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
java:163)
at
org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
at
org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
at
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
ions(AggressiveReleaseTest.java:210)
I fixed it by changing:
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Connection.class.getClassLoader(),
PROXY_INTERFACES,
handler
);
}
to
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Thread.currentThread().getContextClassLoader(),
PROXY_INTERFACES,
handler
);
}
Connection.class is always loaded via the boot/system clasloader so I
don't get how using its classloader
when generating the proxy would ever work ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] Connection proxy error
Umm, why not have a look at the fix?
-Original Message-
From: Max Andersen
Sent: Monday, November 06, 2006 7:34 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxy error
if we want to be completely safe then
Thread.currentThread().getContextClassLoader()==null?Environment.class.g
etClassLoader():Thread.currentThread().getContextClassLoader()
would be better since in the case contextclassloader == null then
Connection.class.getClassLoader() is most likely null or point to a
"too-high"
classloader thus using the classloader of Hibernate self would be the
best
fallback.
/max
> I committed the fix. Just pointing out that your solution dangerously
> looks correct...
>
> -Original Message-
> From: Max Andersen
> Sent: Monday, November 06, 2006 7:28 AM
> To: Steve Ebersole; hibernate-dev@lists.jboss.org
> Subject: Re: [hibernate-dev] Connection proxy error
>
> On Mon, 06 Nov 2006 14:11:46 +0100, Steve Ebersole
> <[EMAIL PROTECTED]> wrote:
>
>> Context classloader can be null...
>
> But it should then be done in the classloader that loaded hibernate;
not
>
> the system classpath loader which Connection.class will be.
>
> You don't get this error at your end ?
>
> At least i'm not the only one
>
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1629#actio
> n_25145
> ;)
>
> /max
>
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl
>> Andersen
>> Sent: Monday, November 06, 2006 5:54 AM
>> To: hibernate-dev@lists.jboss.org
>> Subject: [hibernate-dev] Connection proxy error
>>
>> Hi Steve,
>>
>> After updating from svn I get the following in alot of tests:
>>
>> java.lang.IllegalArgumentException: interface
>> org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
>> at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
>> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
>> at
>>
>
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
>> ionProxy.java:56)
>> at
>>
>
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
>> java:163)
>> at
>> org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
>> at
>> org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
>> at
>>
>
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
>> ions(AggressiveReleaseTest.java:210)
>>
>> I fixed it by changing:
>>
>> public static Connection generateProxy(ConnectionManager
>> connectionManager) {
>> BorrowedConnectionProxy handler = new
>> BorrowedConnectionProxy( connectionManager );
>> return ( Connection ) Proxy.newProxyInstance(
>> Connection.class.getClassLoader(),
>> PROXY_INTERFACES,
>> handler
>> );
>> }
>>
>> to
>>
>> public static Connection generateProxy(ConnectionManager
>> connectionManager) {
>> BorrowedConnectionProxy handler = new
>> BorrowedConnectionProxy( connectionManager );
>> return ( Connection ) Proxy.newProxyInstance(
>>
>> Thread.currentThread().getContextClassLoader(),
>> PROXY_INTERFACES,
>> handler
>> );
>> }
>>
>> Connection.class is always loaded via the boot/system clasloader so I
>> don't get how using its classloader
>> when generating the proxy would ever work ?
>>
>
>
>
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Connection proxy error
too easy.
Umm, why not have a look at the fix?
-Original Message-
From: Max Andersen
Sent: Monday, November 06, 2006 7:34 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxy error
if we want to be completely safe then
Thread.currentThread().getContextClassLoader()==null?Environment.class.g
etClassLoader():Thread.currentThread().getContextClassLoader()
would be better since in the case contextclassloader == null then
Connection.class.getClassLoader() is most likely null or point to a
"too-high"
classloader thus using the classloader of Hibernate self would be the
best
fallback.
/max
I committed the fix. Just pointing out that your solution dangerously
looks correct...
-Original Message-
From: Max Andersen
Sent: Monday, November 06, 2006 7:28 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxy error
On Mon, 06 Nov 2006 14:11:46 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
Context classloader can be null...
But it should then be done in the classloader that loaded hibernate;
not
the system classpath loader which Connection.class will be.
You don't get this error at your end ?
At least i'm not the only one
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1629#actio
n_25145
;)
/max
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl
Andersen
Sent: Monday, November 06, 2006 5:54 AM
To: hibernate-dev@lists.jboss.org
Subject: [hibernate-dev] Connection proxy error
Hi Steve,
After updating from svn I get the following in alot of tests:
java.lang.IllegalArgumentException: interface
org.hibernate.jdbc.ConnectionWrapper is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)
at
org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnect
ionProxy.java:56)
at
org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.
java:163)
at
org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111)
at
org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359)
at
org.hibernate.test.connections.AggressiveReleaseTest.testBorrowedConnect
ions(AggressiveReleaseTest.java:210)
I fixed it by changing:
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Connection.class.getClassLoader(),
PROXY_INTERFACES,
handler
);
}
to
public static Connection generateProxy(ConnectionManager
connectionManager) {
BorrowedConnectionProxy handler = new
BorrowedConnectionProxy( connectionManager );
return ( Connection ) Proxy.newProxyInstance(
Thread.currentThread().getContextClassLoader(),
PROXY_INTERFACES,
handler
);
}
Connection.class is always loaded via the boot/system clasloader so I
don't get how using its classloader
when generating the proxy would ever work ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] ant junitreport: Success rate 79.56%
My 7.33% Hypersonic SQL was bogus, after installing the driver results are upto 93.3% now which is confidence gaining. (Failures=36, Errors=22 out of 906) For Mysql 79.56% (Failures=30, Errors=156 out of 910) So from this I can say that Hypersonic SQL is the best reference configuration for the test. I would like to re-create your 100%, so maybe your overall configuration is different to mine, would you be kind enough to confirm the details of your configuration. There are 14 tests named *FailureExpected. Max Rydahl Andersen wrote: Thee pass rate for tests that is not named *FailureExpected is 100% on hsql. Same for alot of other db's. (i recently ran the testsuite against oracle, mysql and postgresql) And the test suite is constantly maintained. /max My configuration: * Hibernate 3.2.0-ga * JVM: Sun 1.5.0u8 x86_64/Linux * JDBC Driver: mysql-connector-java-3.1.12-bin.jar * SQL Server: MySQL 4.1.15 * HSQL: 1.8.0 (I Think) ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] JDK 1.4 and hibernate
To all, total newbie to Hibernate. Does hibernate have any limitations running against KDK 1.4 and JRE 1.4? If so, is there a version that does? Thanks Reza ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] ant junitreport: Success rate 79.56%
My hsql setup is simply what comes with Hibernate, nothing fancy. Note that svn had a bug the last 24 hours which have been fixed now that would cause alot of tests to fail. /max My 7.33% Hypersonic SQL was bogus, after installing the driver results are upto 93.3% now which is confidence gaining. (Failures=36, Errors=22 out of 906) For Mysql 79.56% (Failures=30, Errors=156 out of 910) So from this I can say that Hypersonic SQL is the best reference configuration for the test. I would like to re-create your 100%, so maybe your overall configuration is different to mine, would you be kind enough to confirm the details of your configuration. There are 14 tests named *FailureExpected. Max Rydahl Andersen wrote: Thee pass rate for tests that is not named *FailureExpected is 100% on hsql. Same for alot of other db's. (i recently ran the testsuite against oracle, mysql and postgresql) And the test suite is constantly maintained. /max My configuration: * Hibernate 3.2.0-ga * JVM: Sun 1.5.0u8 x86_64/Linux * JDBC Driver: mysql-connector-java-3.1.12-bin.jar * SQL Server: MySQL 4.1.15 * HSQL: 1.8.0 (I Think) -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] JDK 1.4 and hibernate
No, no. Please use the user forum: http://forum.hibernate.org Reza Razavipour wrote: To all, total newbie to Hibernate. Does hibernate have any limitations running against KDK 1.4 and JRE 1.4? If so, is there a version that does? Thanks Reza ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Revision 9989 of AbstractStatementExecutor and MySQL
Hi everyone, I've been looking at the most recent change to AbstractStatementExecutor and it seems to assume that if a DDL statement, in general, results in a commit that this will also happen for a temporary table. In the case of MySQL, at least, this is not the case. The code in AbstractStatementExecutor goes and creates the temporary table in a new connection, which, in the case of MySQL, will not be visible in the current transaction. http://fisheye.jboss.com/browse/Hibernate/branches/Branch_3_2/Hibernate3/src/org/hibernate/hql/ast/exec/AbstractStatementExecutor.java?r1=9262&r2=9989 If this turns out to be a bug, I will create an isolated test case for it and log a bug in JIRA. Donnchadh ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061106220003 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 11/06/2006 22:00:03Time to build: 9 minutes 10 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (922) Total Errors and Failures: (6)testJoinedSubclassorg.hibernate.test.joinedsubclass.JoinedSubclassTesttestCompositeIDsorg.hibernate.test.legacy.FumTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestUnionSubclassorg.hibernate.test.unionsubclass2.UnionSubclassTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2129)10740modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/type/CollectionType.javaHHH-1401 : merge operation casuing unecessary updates10740modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/ops/VersionedEntity.javaHHH-1401 : merge operation casuing unecessary updates10740modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/ops/OptLockEntity.hbm.xmlHHH-1401 : merge operation casuing unecessary updates10740modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/ops/MergeTest.javaHHH-1401 : merge operation casuing unecessary updates10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/idbag/Mappings.hbm.xmlHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/bagHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/list/Mappings.hbm.xmlHHH-2217 : PersistentCollection mutation methods and dirtying10738modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/collection/PersistentList.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/idbagHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/idbag/IdbagOwner.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/bag/Mappings.hbm.xmlHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/listHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/bag/BagOwner.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/idbag/PersistentIdBagTest.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/list/ListOwner.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/collection/PersistentBag.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/bag/PersistentBagTest.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/CollectionSuite.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/collection/PersistentIdentifierBag.javaHHH-2217 : PersistentCollection mutation methods and dirtying10738added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/collection/list/PersistentListTest.javaHHH-2217 : PersistentCollection mutation methods and dirtying10736modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javaFixed Javadoc10735modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javaFixed Javadoc10733modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/jpa/AbstractJPATest.javatesting user assertion that JPA case insensitivity support breaks class-name -> discriminator value resolution10733modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/jpa/ql/JPAQLComplianceTest.javatesting user assertion that JPA case insensitivity support breaks class-name -> discrim
