The first thing what the portal does it looks at the DB. Jun 1 ’12 at Cannot resolve reference t o bean ‘indexableAdvice’ while setting bean property ‘nextMethodInterceptor’; nested exception is or g. I will post the solution when I get there. Last acquisition attempt exception: Canno t resolve reference to bean ‘liferayHibernateSessionFactory’ while setting constructor argument; nes ted exception is org.

Uploader: Dular
Date Added: 25 August 2009
File Size: 22.38 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 55213
Price: Free* [*Free Regsitration Required]

Did you check to insure Maven including the dependencies in the.

Cannot resolve reference to bean ‘liferayTransactionManager’ while setting bean property ‘platformTransactionManager’; nested exception is org. Table of contents 0. Cannot resolve reference to bean ‘tran sactionAdvice’ while setting bean property ‘nextMethodInterceptor’; nested exception hava.sql.sqlexception org.

Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

No suitable driver Regular Member Posts: Cannot resolve reference to bean ‘asyncAdvice’ while setting bean property ‘nextMethodInterceptor’; nested exception is org. What connection pool are you using? Liferay can also be used with a DB2 sitable. Sign up or log in Sign up using Google.


While trying to acquire a needed new resource, we failed to succee d more than the maximum number of allowed acquisition attempts 3. Connections could n ot be acquired from the underlying database! SQLServerDriver after migration to liferay 7 from liferay 6.


Liferay provides automatically the postgreSQL driver jar. Jun 4 ’12 at 9: You are running into this problem because there are two classpaths you are dealing with. Although the solutions proposed didn’t solve my problem directly, they provided some ideas to reach this alternative solution.

N o dialect found java. I think usually the 3.

I test java.sql.slexception connection without any container you noticed about web containerjust via POC pure old console. I’ve read from several sources, that problem can be in connection url syntax and driver mismatch.

Email Required, but never shown. In general, the changeover to the lifeeay SGBD is following these next steps:. I assume that this is a driver that worked for you in 6. Create a blank database called lportal. Cannot resolve reference to bean ‘indexab leAdvice’ while setting bean property ‘nextMethodInterceptor’; nested exception is org.


To prevent this I added the following line to my c3p0-config. Yes i use service builder. Jun 1 ’12 at Starting service Catalina May 24, 7: Class not found exception while creating datasource. With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.

eption: No suitable driver (JDBC and Relational Databases forum at Coderanch)

A ResourcePool could not acqu ire a resource from its primary factory or source. I have the similiar problem. But my goal is to use type 2. In this tutorial, we will see how to switch java.sql.sqlexcfption to one of the following SGBD:.

Also, can you include a stack trace?