[Persistence, JBoss/CMP, Hibernate, Database] - Heavy load results in: IllegalArgumentException: Illegal loa
by mroosendaal
Hi,
We have an application that uses JMS/MDB to send messages, processes these messages and persists derived (from messages) Hibernate-objects. Running a heavy load synchornise works fine but now that we use JMS/MDB on JBoss 4.0.2 we get the following errors which occurs now and again:
java.lang.IllegalArgumentException: Illegal load factor: 0.75
at java.util.HashMap.(HashMap.java:168)
at java.util.HashMap.(HashMap.java:190)
at org.hibernate.engine.PersistenceContext.(PersistenceContext.java:171)
at org.hibernate.impl.SessionImpl.(SessionImpl.java:225)
at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:462)
at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:486)
at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:494)
at sun.reflect.GeneratedMethodAccessor237.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.springframework.orm.hibernate3.LocalSessionFactoryBean$TransactionAwareInvocationHandler.invoke(LocalSessionFactoryBean.java:988)
at $Proxy64.openSession(Unknown Source)
at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:395)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:281)
at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:217)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:174)
at $Proxy68.findBerichtByActiviteitId(Unknown Source)
at nl.ictu.spg.service.lo3.gbanetwork.LO3BerichtUtil.locateLO3Bericht(LO3BerichtUtil.java:421)
at nl.ictu.spg.service.lo3.gbanetwork.LO3BerichtActiviteit.(LO3BerichtActiviteit.java:129)
at nl.ictu.spg.domain.activityflow.ActivityflowFactory.initializeWorkFlowActiviteit(ActivityflowFactory.java:160)
at nl.ictu.spg.domain.activityflow.ActivityflowFactory.loadWorkFlowActiviteit(ActivityflowFactory.java:136)
at nl.ictu.spg.service.lo3.gbanetwork.LO3BerichtDispatcher.dispatch(LO3BerichtDispatcher.java:37)
at nl.ictu.spg.integration.idvmessageprocessing.ejb.SpGBerichtDispatcherMDB.dispatchIndividualId(SpGBerichtDispatcherMDB.java:98)
at nl.ictu.spg.integration.idvmessageprocessing.ejb.SpGBerichtDispatcherMDB.dispatchArrayOfIds(SpGBerichtDispatcherMDB.java:108)
at nl.ictu.spg.integration.idvmessageprocessing.ejb.SpGBerichtDispatcherMDB.onMessage(SpGBerichtDispatcherMDB.java:79)
at sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:475)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:153)
at org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT.invoke(MessageDrivenTxInterceptorBMT.java:32)
at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:87)
at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:94)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
at org.jboss.ejb.Container.invoke(Container.java:873)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:1090)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1392)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
at org.jboss.mq.SpySession.run(SpySession.java:333)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:534)
.
What could be the problem? Memory shortage on JBoss, not using Hibernate or Spring correctly?
Hibernate 3.0.5
Spring 1.2.3
JBoss 4.0.2
JDK 1.4.2_08
Any ideas or suggestions?
Thanks,
Maarten
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968832#3968832
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968832
19 years, 1 month
[J2EE Design Patterns] - Download Volume 01 of Eclipse Magazine for FREE
by hinags2002
Software & Support Media, an associate member of the Eclipse Foundation, has announced the new Eclipse Magazine (English Edition). The new initiative is part of Software & Support Media?s mission to power the Eclipse ecosystem with top-class information that will promote and hone the use of Eclipse worldwide. Published in a digital format, the magazine will cover a broad range of vibrant Eclipse-based topics each month, encompassing the entire software development lifecycle. It will endeavor to offer in-depth examinations of Eclipse sub-projects, feature-rich case studies by cutting-edge Eclipse teams and users, and articles covering the entire application lifecycle using the Eclipse IDE and other code from the Eclipse Foundation, Eclipse-based tools and plug-ins for Eclipse.
The inaugural issue of the magazine is available for FREE. You can download it from here: http://www.eclipsemag.net/ecm/ecmservices/psecom,id,5,nodeid,4.html. Once you register, you also have FREE access to the magazine for the months of September, October, and November 2006.
In the cover story this issue, Tom Eicher, Markus Keller, and Christof Marti detail how to build an editor and integrate it into the Eclipse workbench. They demonstrate how a source code editor ? with functions such as syntax coloring, model synchronization, content assist including templates, and folding ? can be created and embedded within the Eclipse environment.
Tobias Widmer sheds light on the services offered by the Eclipse Java Development Tools (JDT) and the Refactoring Language Toolkit (LTK) to support automated Java refactorings. To demonstrate the combination of Java-specific and language-neutral frameworks, Tobias presents a refactoring implementation for an Introduce Indirection refactoring that is designed to introduce an indirection method for existing method invocations.
Jason Weathersby explains how to use the enhanced features of Eclipse BIRT 2.1 to effectively create business reports. This issue also features an interview with Kent Beck and two exclusive features that focus on the good and bad in Eclipse 3.2 and how Eclipse is being used in your mobile, in banks and in space. The Plug-in-Parade details the SWT/Swing Designer, WindowBuilder Pro.
Eclipse magazine is aimed at software development practitioners, development managers, architects, test and QA managers, and others who use Eclipse and related technologies in their development projects. Our aim is to help the community with as much quality information on Eclipse as possible. Towards this end, we are running a promotion until November to give you a chance to send us that Eclipse article/tutorial that you've always wanted to write and share with the larger community. In return, you stand a chance to win BIG! For more details, head over to the promotion page: http://www.eclipsemag.net/ecm/ecmservices/psecom,id,16,nodeid,4.html. Otherwise, we hope you enjoy reading the inaugural issue of this magazine. Please send in your feedback and requests on what you'd like to see covered in the magazine to : editors(a)eclipsemag.net.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968830#3968830
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968830
19 years, 1 month
[Tomcat, HTTPD, Servlets & JSP] - jboss giving the following jsp/servlet exception
by mahanare
Hi, what could be the problem with the following exception.
we are trying to work with axis web service on jboss 4.0.1.
Same application is working fine with corresponding tomcat version wihtout any problem.
but when we deploy it the application on jboss we are getting the following exception.
| IdleRemover notifying pools, interval: 150000 162481719 ERROR [http-0.0.0.0-8080-Processor23] org.jboss.web.localhost.Engine - StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception java.lang.VerifyError: (class: org/apache/jsp/logon_jsp, method: _jspService signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Incompatible object argument for function call at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618) at java.lang.Class.getConstructor0(Class.java:1930) at java.lang.Class.newInstance0(Class.java:278) at java.lang.Class.newInstance(Class.java:261) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:137) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:307) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) 162542313 DEBUG [IdleRemover] org.jboss.resource.connectionmanager.IdleRemover - run: IdleRemover notifying pools, interval: 150000
any info about this exception will be of great use for me.
Thanks
Harinath
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968827#3968827
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968827
19 years, 1 month
[JBoss Seam] - Re: Problem: Custom validate methods in EJBs crash
by raja05
"bfo81" wrote :
| But when you create a new person all its properties are null. And when you fill in the fields in a form and click save, then the persons properties are still null during validation (phase 3). They get their concrete values later, in phase 4 (update model values). And, alas, you cannot compare something to null.
|
Take a look at the ModelValidator class in org.jboss.seam.ui. That does its validation at the process Validation phase by using the model class (and the validators that go along with it) and the values that are in the request.
One other way is that since the values are updated in the model only later(after the processValidations), you could queue a new type of event and set the phaseid of that to be UPDATE_MODEL_VALUES. That way the event will be queued during validations but will only be processed after the model values are updated. Thats still ugly(as you are validating in a phase thats not meant for that ) but will work.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968824#3968824
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968824
19 years, 1 month