After synching up with the trunk/repository changes today, the jboss-all-config-tests is back to failing to run due to OMEs:
2007-03-22 14:07:53,513 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
Bringing up jconsole shows the heap to be full with plenty of perm gen memory. Another leak has crept in.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030855#4030855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030855
When I call MessageStoreFactory.getInstance() using the default configuration, an exception is thrown indicating the impl class is not found. I looked in the config and noticed the impl class referenced by org.jboss.soa.esb.persistence.connection.factory is not valid. It should be org.jboss.internal.soa.esb.persistence.format.MessageStoreFactoryImpl. After updating that, it gets further but crashes with a missing dependency on c3p0-0.9.1-pre9.jar. Copying that into jbossesb.sar/lib fixes the problem and everything seems to work fine.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030852#4030852
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030852
Great, thanks.
[OT] BTW, if an SFSB has a ref to an XPC and the bean fails over, Hibernate logs a WARN when the bean context is deserialized from the cache:
14:36:32,244 WARN [SessionFactoryObjectFactory] Not found: ff808081117aea3701117aea37d40000
If the session factory has a name, then the deserialization continues on and succeeds.
The WARN isn't a huge problem, since it only happens on failover, when a little bit of unusual stuff in the logs isn't terrible. But it's a rather cryptic message that's likely to lead to support questions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030834#4030834
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030834
"pgier" wrote :
| Metatype (API) and Spring (impl) only generate one artifact, should these be packaged as metatype-api and spring-impl? Or can they just use the default maven packaging to create a single jar?
|
What's the difference? Just name?
"pgier" wrote :
| The container sub-project has a lot of parts, is there a way to simplify this? Like having a single SPI artifact for all of this subproject?
|
I think not.
Since that is what we wanted - fine grained artifacts == use what you need.
"pgier" wrote :
| Also, I am planning to remove the ant build scripts from SVN tonight as long as there are no objections.
Np with me, as long as things work.
What's the deal with QA and MC - regarding microcontainer-head-testsuite?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030823#4030823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030823