[EJB 3.0] - EJB3, Sybase database, MappingException: Dialect does not su
by yujianming
We are using Jboss4.2.1GA. I am adding a new Sybase data source. But when I start Jboss, the error message is as following. The .ear is not even deployed. May I know how to solve this problem?
Thank you very much!
James
**************************************Error Message***********************
Caused by: org.hibernate.MappingException: could not instantiate id generator
at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:98)
at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:152)
at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:192)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730)
... 145 more
Caused by: org.hibernate.MappingException: Dialect does not support sequences
at org.hibernate.dialect.Dialect.getSequenceNextValString(Dialect.java:596)
at org.hibernate.id.SequenceGenerator.configure(SequenceGenerator.java:65)
at org.hibernate.id.SequenceHiLoGenerator.configure(SequenceHiLoGenerator.java:43)
at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:94)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118119#4118119
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118119
18 years, 3 months
[JBossCache] - Re: newbie question - ReplicationException
by manik.surtani@jboss.com
Not necessarily heavily updated, but more importantly concurrently updated, which is what you described.
In your case though, perhaps a good approach may be for both caches to attempt to write the change, and if one cache fails to write, assume that this is because the other has completed the write and hence it would not be necessary?
Also, I find it odd that *both nodes* fail. I guess with P/L and identical lock acquisition timeouts bean that this may happen. If your setup is a master/backup, perhaps your backup cache could have a much shorter lock acquisition timeout so it would always fail first, allowing the other cache to continue?
Both caches failing should almost certainly not happen with optimistic locking - let me know if it does and we can investigate that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118110#4118110
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118110
18 years, 3 months