[JBoss Messaging] - Re: Poor performance after replacing JBossMQ
by omerlin
Thank you for your interrest !
Messages sent by the client to the shared Queue are group by a hash code.
The message unique identifier is named MSISDN.
For example, each message with attribute MSISDN (a long) finishing by 0 will be carried to the sequencer 0
each message with attribute MSISDN (a long) finishing by 1 will be carried to the sequencer 1
(...)
each message with attribute MSISDN (a long) finishing by N will be carried to the sequencer N
We have N sequencer Staleless SB - each sequencer drives a protocol exchange and read a message based on the hash code (between 0 and N)
I hope i'm clear : each sequence get its batch of message for processing.
The objective is to do batch processing.
I understand that this is an anti-pattern as we have to scan the shared queue (in fact there is 2 queues like this) and this is perhaps even worse as many threads do the same scan.
One solution we imagine is to fix the batching size to 10 for instance and to create 10 destination queues and 10 sequencers - we can do this configuration quite quickly
Do you have any suggestion of another pattern that may help to solve our problem ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974314#3974314
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974314
19 years, 7 months
[JBoss Seam] - Many clicks cause touchConversationStack to NPE
by pbrewer_uk
I've got a strange bug in my seam application. If a user clicks on many different links in quick succession then they can frequently get seam to break with the stacktrace below.
Any ideas why this may be happening and how to prevent it? I'm using Seam 1.0.1GA in tomcat without using pageflows. Any help would be appreciated on this one.
Cheers, Peter.
| java.lang.NullPointerException
| at org.jboss.seam.core.Manager.touchConversationStack(Manager.java:181)
| at org.jboss.seam.core.Manager.storeConversation(Manager.java:368)
| at org.jboss.seam.jsf.AbstractSeamPhaseListener.storeAnyConversationContext(AbstractSeamPhaseListener.java:69)
| at org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:45)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45)
| 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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
| at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
| at java.lang.Thread.run(Thread.java:595)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974309#3974309
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974309
19 years, 7 months
[JBoss Portal] - DefaultPortal shows instead of actual portal
by portalgeek
Hi,
I have developed portlets and placed them in the protal i have developed. The build is successful and i have deployed in the server ( no problems).
but when i try open this portal by saying http://localhost:8080/portal/portal/PortalTexas the default JBoss portal shows up instead of portal i have developed.
I have tried several things, but no progress. I need somehelp, can someone throw some light here.
my *-object.xml looks as follows:
| <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
| <deployments>
| <deployment>
| <if-exists>overwrite</if-exists>
| <parent-ref />
| <portal>
| <portal-name>PortalTexas</portal-name>
| <properties>
| <property>
| <name>portal.defaultObjectName</name>
| <value>Page1</value>
| </property>
| <property>
| <name>layout.id</name>
| <value>generic</value>
| </property>
| <property>
| <name>theme.id</name>
| <value>Nphalanx</value>
| </property>
| <property>
| <name>theme.renderSetId</name>
| <value>divRenderer</value>
| </property>
| <property>
| <name>layout.strategyId</name>
| <value>maximizedRegion</value>
| </property>
| </properties>
| <supported-modes>
| <mode>view</mode>
| <mode>edit</mode>
| <mode>help</mode>
| </supported-modes>
| <supported-window-states>
| <window-state>normal</window-state>
| <window-state>minimized</window-state>
| <window-state>maximized</window-state>
| </supported-window-states>
| <page>
| <page-name>Business</page-name>
| <window>
| <window-name>Navigation</window-name>
| <instance-ref>NavigationPortletInstance</instance-ref>
| <region>navigation</region>
| <height>0</height>
| <properties>
| <property>
| <name>theme.windowRendererId</name>
| <value>emptyRenderer</value>
| </property>
| <property>
| <name>theme.decorationRendererId</name>
| <value>emptyRenderer</value>
| </property>
| <property>
| <name>theme.portletRendererId</name>
| <value>emptyRenderer</value>
| </property>
| </properties>
| </window>
| </page>
| <page>
| <page-name>Monitoring</page-name>
| <window>
| <window-name>Navigation</window-name>
| <instance-ref>NavigationPortletInstance</instance-ref>
| <region>navigation</region>
| <height>0</height>
| <properties>
| <property>
| <name>theme.windowRendererId</name>
| <value>emptyRenderer</value>
| </property>
| <property>
| <name>theme.decorationRendererId</name>
| <value>emptyRenderer</value>
| </property>
| <property>
| <name>theme.portletRendererId</name>
| <value>emptyRenderer</value>
| </property>
| </properties>
| </window>
| <window>
| <window-name>SamplePortlet</window-name>
| <instance-ref>SamplePortletInstance</instance-ref>
| <region>center</region>
| <height>0</height>
| </window>
| </page>
| </portal>
| </deployment>
| </deployments>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974308#3974308
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974308
19 years, 7 months