[JBoss Portal] - Re: JBP 2.6 RC2 : Pb starting service portal.wsrp:service=Co
by chris.laprunï¼ jboss.com
"Antoine_h" wrote :
| As it is a jdbc mysql problem : I use the latest version of Hibernate, ie 3.2.4sp1.
| The "caused by" second exception is:
|
| 18:32:28,796 WARN [ServiceController] Problem starting service portal.wsrp:service=ConsumerRegistry
| | org.hibernate.exception.GenericJDBCException: could not execute query using iterate
| | at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
| | at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
| | ....
| | ....
| | Caused by: java.sql.SQLException: Invalid value for getLong() - 'self'
| | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:910)
| | at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2768)
| | at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2666)
| | at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2791)
| | at org.jboss.resource.adapter.jdbc.WrappedResultSet.getLong(WrappedResultSet.java:718)
| | at org.hibernate.type.LongType.get(LongType.java:28)
| | at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:163)
| | at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:154)
| | at org.hibernate.type.ManyToOneType.hydrate(ManyToOneType.java:103)
| | at org.hibernate.type.EntityType.nullSafeGet(EntityType.java:204)
| | at org.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:93)
| | at org.hibernate.impl.IteratorImpl.<init>(IteratorImpl.java:58)
| | at org.hibernate.loader.hql.QueryLoader.iterate(QueryLoader.java:405)
| | ... 132 more
| |
|
Yes, this has been fixed. See: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=7351. This is due to a problem with Hibernate 3.2.3 and above. Note that you'll need to wipe out the WSRP-related tables in your DB when you upgrade to a version containing the fix as one table field has been renamed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056612#4056612
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056612
18Â years, 10Â months
[Installation, Configuration & Deployment] - Re: Influencing classpath order
by ljnelson
I should have said that I tried to use the (left angle bracket) classpath (right angle bracket) element in jboss-4.0.5/server/myServer/conf/jboss-service.xml. I put in three such elements, like this:
| <classpath codebase="${jboss.server.lib.url:lib}" archives="shadow.jar"/>
| <classpath codebase="${jboss.server.lib.url:lib}" archives="base.jar"/>
| <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
|
I would think that would make it so that the various JBoss classloaders in effect would get Foo.class from shadow.jar, not base.jar. I have reports from users that this is not consistent across systems, which makes me think that this is not the way to do it.
Also, in the case of a web application deployed later on, will it--when its loader comes up to this parent in search of Foo.class--will the parent loader in such a case respect this order? The mind-bending diagram in the classloader use cases topic would appear to say yes, this is the case, but that's not the behavior being seen.
Finally, if in my code I ask a UCL for its URLs, I take it their order is absolutely and entirely insignificant, and that it is actually impossible to tell who will load a given class.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056609#4056609
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056609
18Â years, 10Â months
[JBoss Portal] - Re: initial default page not displayed from source build
by Antoine_h
Hello,
I got the same problem : minimal portal
but with JBoss AS 4.0.5 and the nightly build of portal (of june 20th).
I took the JBoss Portal bundled with JBoss AS (4.0.5), installed it.
After, I took the nightly build of portal and did the "build deploy" in the build folder.
I got a new jboss-portal.sar, in the deploy folder.
but :
- only 4.9 Mo instead of about 12Mo
- a lot of war and sar were missing inside it (no portal-admin.sar, as an example).
- only the "minimal portal" : login page, userportlet, like you
So it is not because of JSF !
It is because the war and sar are not there...
I thaught I had missed something in deploying the nigthly build, so I went back to the regular release package.
So it seem there is a problem there.
May be the way I did the deploy : the doc may lack something ? an option ?
About EJB3 :
My portal is working with EJB3, with jboss 4.0.4GA and JBP 2.4.1SP1.
I did the installation of jboss 4.0.4GA and JBP XXX (I don't remember which one it was) with the jems installer
note : ask for the option of EJB3 when installing.
Then I updated the portal with JBP 2.4.1SP1 (when it was released).
it works fine.
I remember also I added the latest Hibernate version (that was 3.2.3ga) with also the jars for annotation and persistence manager etc... to use annotation in the EJB3 way.
All worked fine.
And with MyFace 1.1.5.
So : jboss 4.0.4GA and JBP 2.4.1SP1 and MyFace 1.1.5 are ok with EJB3
after : I am now upgrading with JBP 2.6... don't know yet. It should be ok for EJB3, as this is quiet separate from the way the portal run.
But there are still some little things that may be a problem with JBP2.6 (like the myface stuff... that will be resolved soon I hope...).
Hope it helps...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056608#4056608
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056608
18Â years, 10Â months
[JBoss Seam] - Re: Glassfish example and the entity converter.
by sahoo
Yes, it is a bug - a bug in the spec supplied javax.persistence.Persistence.class. There is a work around available for you. Instead of packaging Hibernate classes in the ear file, please put them in GlassFish/lib directory and restart the server. That will fix the issue. Now read on, what is the bug...
The spec supplied javax.persistence.Persistence.class (https://glassfish.dev.java.net/source/browse/glassfish/persistence-api/sr...) has a static variable defined like this:
protected static final Set<PersistenceProvider> providers = new HashSet<PersistenceProvider>();
|
In createEntityManagerFactory() method, it uses currentThread.getContextClassLoaded() to search for all the persistence providers and stores them in that variable. Obviously, this is an optimization attempt, but it is not free from trouble. One of the scenarios where it does not always work is in your case, where the providers are bundled in the application ear/jar/war.
First time, you deploy the app, providers variable is populated with HibernatePersistence.class loaded by the application class-loader that the app was associated with at that point of time. When you redeploy, the app is now associated with a new class loader, and we expect the old class loader to be garbage collected. But, because of this providers variable, the old HibernatePersistence.class is used. GlassFish is written to protect against it, so we detect the situation and disallow the class loading. Hence you see that exception.
I have been able to fix this issue by patching Persistence.class. I will file an issue in GlassFish and see how we can address the spec supplied class. In the mean while, you should be able to use the work around suggested earlier.
Thanks,
Sahoo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056607#4056607
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056607
18Â years, 10Â months