[JBoss-user] [Messaging, JMS JBossMQ] - Re: Memory problems starting JBossmq with DB2
For those of you out there unfortunately enough to run DB2 I have the solution to this problem. The solution to the problem as suggested in http://jira.jboss.com/jira/browse/JBAS-1891 (and parent) do not work with DB2. Setting fetch direction, concurrent read mode or fetch size will not let you load the JBoss messaging service with a large number of messages in a single queue. The proposed solution http://jboss.org/index.html?module=bbop=viewtopict=46186 wouldn't work either since you still try to load all messages in a destination in a single sql. In DB2 memory for LOB records are freed only when the statement handle is dropped. This meens that you have to split the fetch sequence into several sqls where each sql only return a smaller amount of messages (In my case less than 1600 messages). However it is an obscure workaround for this problem. Setting the patch2=50 in your db2cli.ini solves these issues. By setting this you tell DB2 to free memory after each fetch. This file really is an ODBC config file. Go figure. Se http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/ad/c0007882.htm for further explanation on this and other obscure settings. I hope no one else have to use as much time as me on this issue. Oystein View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3909328#3909328 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3909328 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Re: Memory problems starting JBossmq with DB2
Thanks Adrian I obviously searched the wrong categories. I'll do a followup in the subtask in Jira. Oystein View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3908122#3908122 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3908122 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS JBossMQ] - Memory problems starting JBossmq with DB2
Hi I have an application running on JBoss 3.2.7 using the JBossmq the comes with the installation of JBoss. We've been running this over half a year with almost no problems (At least not releated to JBoss code). A short time ago however, we had trouble starting the JBoss instance again after a planned down period. After searching for the cause we found the problem to be related to loading for messages from a JMS destination. When trying to load the messages DB2 threw an exception complaining about out of memory (APP_CTL_HEAP_SZ set to low). In the JBossmq code the messages are loded with this sql: SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=? The loading code is located in the loadFromStorage method in org.jboss.mq.pm.jdbc2.PersistenceManager We checked out how many messages could be loaded this way with the default setting of DB2. The anwere where 1600 messages. So if there are more messages in a single destination then the mq service wouldn't start. We have discussed this with IBM support and they are telling us that DB2 works as designed. According to them the heap is cleared when the transaction commits. In my opinion this is pretty stupid since you cannot navigate backwards in the recordset, and already read rows could be garbagecollected at once. The interesting thing here is that there isn't any memory problems at the applicationserver, but only in DB2. Adjusting the APP_CTL_HEAP_SZ to higher levels cannot solve our problem since it doesn't scale well. My questions are: Have anyone else had similar problems either with DB2 or other databases? Do anyone have a solution to how to get around this? A rather simple solution (I think) for us would be to modify the loading code i JBossmq to load fewer messages in one transaction, and repeat until all messages are loaded. But we would prefere not to do this unless this is accepted into the JBossmq code. Thank you. Oystein Aadland PS: I tried to search for similar posts in the forum and the bug database without finding anything. If I missed it I apologise for the inconvenience. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3907660#3907660 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3907660 --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss.NET] - Nullpointer in JBoss.net 3.2.6
Hi I've been uning JBoss 3.2.1 for some time with the JBoss.net axis webservice integration. And this worked ok. We want to upgrade to 3.2.6 because of a path to the UnifiedClassloader. However when we try to run the same webservice on 3.2.6 we get a NullpointerException in org.jboss.net.axis.Deployment.oldGetService. Full stactrace: java.lang.NullPointerException at org.jboss.net.axis.Deployment.oldGetService(Deployment.java:255) at org.jboss.net.axis.Deployment.getService(Deployment.java:275) at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:290) at org.apache.axis.AxisEngine.getService(AxisEngine.java:302) at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:900) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:372) 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:158) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) 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) I looked at the code where the Nullpointer originates, and it looks like the MessageContext isn't initialised at the time of the call. When I look at the code in AxisServlet.doPost is seems that the initialisation of this context is done after the call to getService(). To me it looks like this cannot work. Does anyone know if this is a bug, or if there is a workarond for it? I also noticed that the WSDL generated from the 3.2.6 differs fra the one from 3.2.1. Snippet from 3.2.1: wsdl:operation name=execute wsdlsoap:operation soapAction=Manager/ wsdl:input name=executeRequest wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://localhost:8080/jboss-net/services/Manager; use=encoded/ /wsdl:input wsdl:output name=executeResponse wsdlsoap:body
[JBoss-user] [JBoss.NET] - Re: Nullpointer in JBoss.net 3.2.6
I found a bug the Nullpointer issue in the bugtracking system. http://sourceforge.net/tracker/?group_id=22866atid=376685func=detailaid=1042176 It looks like the same problem. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860873#3860873 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860873 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss.NET] - Re: Nullpointer in JBoss.net 3.2.6
The patch for bug 1042176 worked for the NullpoiterException. About the namespace Error?. It doesn't affect the calls. EOF. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3860887#3860887 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3860887 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Persistence CMP/JBoss] - Caching of entity beans
Hi I'm trying to figure out how the caching for cmp entity beans works in JBoss. I had this (maybee naive) idea that if an entity bean was loaded the cmp engine would load this bean only once from the database (One time for each transaction for commit option B). This is the scenario: I repeatedly call a findBySomeParameter(xxx) within one transaction with the same parameters. So the result set is the same each time. The parameters are not the primary key. This results in db access for each find. So it obviously does not use the cache even if it sustains one. I'm using standard entity cmp 2.0 configuration with commit option B and read-ahead 100 on-load. I could of course cache this in my own application but isn't this what cmp should be good at? I do see that it can be difficult for the container to do this, but all this talk about the wonders of the EJB and caches has led me to believe that there where a solution to this. I would really apretiate if someone could explain this to me. How can I code my application to make any use of the bean cache? Best regards Oystein View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3844240#3844240 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3844240 --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
