[JBoss Seam] - ArrayIndexOutOfBounds in MultipartRequest
by dilator
I've not been able to recreate this error - it obviously depends very much on the multipart form data!
But it definitely looks like a bug.
java.lang.ArrayIndexOutOfBoundsException: 2048
| at org.jboss.seam.web.MultipartRequest.checkSequence(MultipartRequest.java:466)
| at org.jboss.seam.web.MultipartRequest.parseRequest(MultipartRequest.java:333)
| at org.jboss.seam.web.MultipartRequest.getParam(MultipartRequest.java:507)
| at org.jboss.seam.web.MultipartRequest.getParameter(MultipartRequest.java:558)
| at org.apache.myfaces.context.servlet.RequestParameterMap.getAttribute(RequestParameterMap.java:39)
| at org.apache.myfaces.context.servlet.AbstractAttributeMap.get(AbstractAttributeMap.java:87)
| at com.sun.facelets.tag.ui.UIDebug.debugRequest(UIDebug.java:119)
| at com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:305)
| at org.ajax4jsf.framework.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:116)
| at org.ajax4jsf.framework.ajax.AjaxViewHandler.restoreView(AjaxViewHandler.java:147)
| at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:141)
| at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
| at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
| at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
| at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
| at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
| at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
| at java.lang.Thread.run(Thread.java:595)
Cheers - Ben
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045912#4045912
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045912
19 years, 1 month
[Installation, Configuration & Deployment] - Problem with uuid-key-generator.sar
by apk2072
We are using jboss-4.0.4.GA as our application server, the default installation contains uuid-key-generator.sar in the default/deploy folder. uuid-key-generator.sar uses "DefaultDS" data source inside their its implementation.
My issues is, I changed the DefaultDS to our database which is Oracle. The reason I kept the data source name same as we are using the JBoss messaging and most of the config scripts use the DefalutDS as data source name.
But uuid-key-generator.sar internally drops and recreates the HILOSEQUENCE table whenever the JBoss server restarts. Generally we don't see this is an issue as JBoss uses hsqldb, in my case I changed hsqldb to oracle and the oracle user id I use does not have drop and recreate privileges. Because of this I do see the following error on start up:
[org.jboss.system.ServiceController.start:] Problem starting service jboss:service=KeyGeneratorFactory,type=HiLo
java.sql.SQLException: ORA-00942: table or view does not exist
There are couple of things I can think of to address this issue:
1. Remove the uuid-key-generator.sar from the deploy folder, however, I am not sure what are other implications the JBoss server will have by removing it.
2. Keep the hsqldb and configure the DefaultDS to point to hsqldb and rename my oracle data source to somethign else.
Can I safely remove uuid-key-generator.sar from JBoss deploy folder and won't have any issues?
-Praveen.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045911#4045911
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045911
19 years, 1 month
[JBoss Messaging] - Re: Message receiver connot reconnect after the messaging se
by cresny
It was clustered, changed to non-clustered ds.
The behavior is different , but still not correct. It now repeatedly recreates a control connection, trying various local ports.
Remote Consumer still does not pick up messages, still no Exception thrown, so still hangs on receive.
repeats (with different local ports):
| 13:53:55,959 WARN [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@1c09624: detected failure on control connection Thread[control: Socket[addr=/159.125.154.138,port=3685,localport=3907],5,main]: requesting new control connection
| 13:53:55,959 DEBUG [BisocketClientInvoker] getting secondary locator
| 13:53:55,959 DEBUG [BisocketClientInvoker] secondary locator: InvokerLocator [null://159.125.154.138:3685/null]
| 13:53:55,959 DEBUG [BisocketServerInvoker] creating control connection: InvokerLocator [null://159.125.154.138:3685/null]
| 13:53:55,974 DEBUG [BisocketServerInvoker] created control connection: Socket[addr=/159.125.154.138,port=3685,localport=3913]
|
finally it, too, errors out:
| 13:56:56,014 WARN [BisocketServerInvoker] Control connection 4f3h4a3u-oowm7j-f1qnw10s-1-f1qnw1qt-7 has been recreated 10 times.
| 13:56:56,014 WARN [BisocketServerInvoker] Assuming it is a connection to an old server, and will not restart
|
Regarding clustering, I'm hoping you can clear something up for me. We planned to deploy JBM in its own cluster, apart from an application cluster, mostly for failover purposes.
All queues would be distributed across the JBM cluster, and remote lookups would be using HAJNDI.
However, your above comments indicate deploying JBM instances and Application instances in a single cluster. Is this the recommended configuration?
BTW, thanks for your time and effort on this, it's much appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045910#4045910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045910
19 years, 1 month