February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-323) Fault tolerant FSSlaveDirectoryProvider

by Oliver Siegmar (JIRA)

Fault tolerant FSSlaveDirectoryProvider --------------------------------------- Key: HSEARCH-323 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-323 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.1.0.GA Reporter: Oliver Siegmar The current implementation of FSSlaveDirectoryProvider requires an existent master repository at startup. In our environment it could happen, that the master repository is built some time after the clients (using the FSSlaveDirectoryProvider) are being started. It'd be good to have a more fault tolerant FSSlaveDirectoryProvider, that would retry to initialize itself (using a TimerTask for example). The configuration should allow to enable/disable this feature and to specify the retry interval and period. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
17
0 / 0

[Hibernate-JIRA] Created: (HHH-5940) @MapKeyJoinColumns always throws an exception

by Bob Reynolds (JIRA)

@MapKeyJoinColumns always throws an exception --------------------------------------------- Key: HHH-5940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5940 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.6 Reporter: Bob Reynolds Using the annotation @MapKeyJoinColumns always throws an exception, which is obvious when you look at AnnotationBinder.java (line 1772 in 3.5.6): if ( property.isAnnotationPresent( MapKeyJoinColumns.class ) ) { stuff... joinKeyColumns = new JoinColumn[mapKeyJoinColumns.length]; stuff... if ( joinKeyColumns != null ) { throw new AnnotationException( "@MapKeyJoinColumn and @MapKeyJoinColumns used on the same property: " + BinderHelper.getPath( propertyHolder, inferredData ) ); } } The problem here is that the if statement is always true because joinKeyColumns was created as non-null above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2587) There is an attempt to set more parameters on a prepared statement than the latter can hold

by Zied Hamdi (JIRA)

There is an attempt to set more parameters on a prepared statement than the latter can hold ------------------------------------------------------------------------------------------- Key: HHH-2587 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2587 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.3 Environment: JPA through hibernate Reporter: Zied Hamdi Priority: Blocker Attachments: IntoCore.zip You can directly import the zip content into netBeans 5.5 the just launch: the test is executed at the home page servlet call. I have an index that doesn't exist : 11 (the total count of columns is 10) : Hibernate: insert into BasicPersonArchiveEntry (endDate, entryPerformer_revision, entryPerformer_id, lastOccurence, note, startDate, source_revision, source_id, revision, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) could not bind value '0' to parameter: 11; Invalid argument: parameter index 11 is out of range. SQL Error: -99999, SQLState: null Invalid argument: parameter index 11 is out of range. Could not synchronize database state with session org.hibernate.exception.GenericJDBCException: could not insert: [com.homeservices.model.impl.BasicPersonArchiveEntry] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2267) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2660) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:52) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:516) at com.sun.enterprise.distributedtx.J2EETransaction.commit(J2EETransaction.java:395) at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:357) at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3653) at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3431) at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1247) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:192) at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:118) at $Proxy49.create(Unknown Source) at tests.entities.TestArchiveServlet.processRequest(TestArchiveServlet.java:46) at tests.entities.TestArchiveServlet.doGet(TestArchiveServlet.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: org.apache.derby.client.am.SqlException: Invalid argument: parameter index 11 is out of range. at org.apache.derby.client.am.PreparedStatement.checkForValidParameterIndex(Unknown Source) at org.apache.derby.client.am.PreparedStatement.checkSetterPreconditions(Unknown Source) at org.apache.derby.client.am.PreparedStatement.setLong(Unknown Source) at org.hibernate.type.LongType.set(LongType.java:42) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:136) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:116) at org.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:284) at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:2008) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2243) ... 46 more EJB5018: An exception was thrown during an ejb invocation on [ArchivableFacadeStatelessBean] javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-436) The annotation processor should check @GroupSequenceProvider

by Gunnar Morling (JIRA)

The annotation processor should check @GroupSequenceProvider ------------------------------------------------------------ Key: HV-436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-436 Project: Hibernate Validator Issue Type: New Feature Components: annotation-processor Reporter: Gunnar Morling Fix For: 4.x The AP should check whether the sequence provider given for a type using @GroupSequenceProvider is parametrized with that same type. To extend the AP with new annotation checks as this one, the following has to be done: * create a new implementation of [ConstraintCheck|https://github.com/hibernate/hibernate-validator/blob/mas...] * register it with [ConstraintCheckFactory|https://github.com/hibernate/hibernate-validator/b...] * extend [ConstraintHelper||https://github.com/hibernate/hibernate-validator/blob/m... to recognize the new supported annotation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2736) support for native/SQL query hints in HQL/Criteria (Oracle SELECT hints for example)

by Adam Wozniak (JIRA)

support for native/SQL query hints in HQL/Criteria (Oracle SELECT hints for example) ------------------------------------------------------------------------------------ Key: HHH-2736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2736 Project: Hibernate3 Issue Type: New Feature Components: query-criteria, query-hql Affects Versions: 3.2.4.sp1 Reporter: Adam Wozniak Hello Everybody In 2004 Gavin said: "I think we plan to add a Query.setQueryHint() method" (hibernate forum: http://forum.hibernate.org/viewtopic.php?p=2193761&sid=5cf2ec711851f726c7... ). But I still cannot find it in Hibernate Core/Hib. Annotation/Hib. EntityManager. Can this enhancement request be opened / reopened? It would be great for us to have such possibility. Kind Regards, Adam Wozniak -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
4
0 / 0

[Hibernate-JIRA] Created: (HV-406) URL Validator not effective

by Marc Schipperheyn (JIRA)

URL Validator not effective --------------------------- Key: HV-406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-406 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0.Final Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik Priority: Minor The supplied URL Validator basically doesn't work. Or at least not as expected. It creates a URL against the URL class and if it fails this, it returns false. There are multiple problems with this: * A URL like http://bljdlfghjdlgjlfd is perfectly valid according to the URL class (intranet domains can be anything) * It's not the most efficient way to test this (generating an error etc) In order to retain backward compatibility I would suggest adding an "internet" attribute, which would force the validator to really check for minimally one dot, maximum 3 characters in the domain extension, etc. Because that is what you would normally want from a validator like this. Also, I would not use the URL class, but use a regular expression. A more elegant way to check this. The URL class approach could be retained for when the "internet" attribute is false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
8
0 / 0

[Hibernate-JIRA] Created: (HV-437) Improve the javocs of the URL constraints

by Hardy Ferentschik (JIRA)

Improve the javocs of the URL constraints ----------------------------------------- Key: HV-437 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-437 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.2.0.Beta1 Reporter: Hardy Ferentschik Fix For: 4.2.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
3
0 / 0

[Hibernate-JIRA] Created: (EJB-408) c3p0 not working with hibernate-entitymanager 3.4.0.GA

by Marcelo Romulo Fernandes (JIRA)

c3p0 not working with hibernate-entitymanager 3.4.0.GA ------------------------------------------------------ Key: EJB-408 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-408 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: windows xp sp2; java sun 1.6.0_10; tomcat 6.0.18; maven 2.0.9 Reporter: Marcelo Romulo Fernandes Priority: Minor I was using hibernate-entitymanager 3.2.6.GA and c3p0 well, but I cannot run c3p0 with hibernate-entitymanager 3.4.0.GA. c3p0 is never called!!! Below, follows persistence.xml, maven dependencies working with hibernate-entitymanager 3.2.6.GA, maven dependencies not woking with hibernate-entitymanager 3.4.0.GA persistence.xml: <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="SystemDDD" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <properties>  <property name="hibernate.connection.username" value="DDD"/> <property name="hibernate.connection.password" value="DDD"/> <property name="hibernate.default_schema" value="DDD"/> <property name="hibernate.connection.url" value="jdbc:oracle:thin:@//YYY:1521/ZZZ"/> <property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver"/> <property name="hibernate.dialect" value="org.hibernate.dialect.OracleDialect"/>  <property name="hibernate.c3p0.min_size" value="1"/> <property name="hibernate.c3p0.max_size" value="10"/> <property name="hibernate.c3p0.timeout" value="5000"/> <property name="hibernate.c3p0.max_statements" value="50"/> <property name="hibernate.c3p0.idle_test_period" value="60000"/>  <property name="hibernate.cache.use_second_level_cache" value="true"/> <property name="hibernate.cache.provider_class" value="org.hibernate.cache.EhCacheProvider"/>  <property name="hibernate.show_sql" value="true"/> <property name="hibernate.format_sql" value="true"/> <property name="hibernate.archive.autodetection" value="class, hbm"/> <property name="hibernate.hbm2ddl.auto" value="none"/> </properties> </persistence-unit> </persistence> maven dependencies working with hibernate-entitymanager 3.2.6.GA <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>3.3.2.GA</version> <type>jar</type> <scope>compile</scope> </dependency> <dependency> <groupId>c3p0</groupId> <artifactId>c3p0</artifactId> <version>0.9.1.2</version> <type>jar</type> <scope>compile</scope> </dependency> maven dependencies not woking with hibernate-entitymanager 3.4.0.GA <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>3.4.0.GA</version> <type>jar</type> <scope>compile</scope> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-ehcache</artifactId> <version>3.3.0.SP1</version> <type>jar</type> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.2</version> <type>jar</type> <scope>runtime</scope> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-c3p0</artifactId> <version>3.3.0.SP1</version> <type>jar</type> <scope>runtime</scope> </dependency> What is wrong or missing? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

7
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3572) Create versioned entities groups

by Adam Warski (JIRA)

Create versioned entities groups -------------------------------- Key: HHH-3572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3572 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136878 Each group would have its own versions table. This could speed up the system when there are a lot of versioned entities, as the versions tables would be less contested. However, if two versioned entities are connected by a (versioned) relation, they would have to be in the same group. So groups could minimally be strongly connected components of the relations graphs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-695) Remove deprecated constructor form DocumentExtractor

by Sanne Grinovero (JIRA)

Remove deprecated constructor form DocumentExtractor ---------------------------------------------------- Key: HSEARCH-695 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-695 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.4.0.Beta1 Basically, revert HSEARCH-694 (and check Infinispan Query build fine) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2011