August 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Thread usage in AIO layer

by timfox

I'm looking at AsynchronousFileImpl and notice that it maintains a Thread per instance. This worries me, if we have a lot of files. Can't these be pooled somehow? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173270#4173270 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173270

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message Chunking Performance problems

by timfox

Mind you, I've just realised you're using TCP loopback, so all these discussions about MTU are moot. http://en.wikipedia.org/wiki/Jumbo_Frame View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173257#4173257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173257

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Thread usage in paging

by timfox

I've just noticed that paging uses a new thread per address. This isn't going to work, since we may have many thousands or tens of thousands of addresses. Instead you could get a thread from a cached thread pool to perform the depage when PagerImpl::messageDone is called. Also having many different PagingStores paging/depaging concurrently to the file system may provide perf problems. I'd really like to see some results of this performance. It might be a better to make sure only one page/or depage is done at a time (queue them for all destinations and use a single thread?), otherwise the disk head will be skipping all over the place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173254#4173254 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173254

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Global Limit for Paging?

by timfox

"clebert.suconic(a)jboss.com" wrote : Do we really want a global limit for paging? | Yes. anonymous wrote : | Say... A single destination is responsible for consuming the whole memory defined by the global limit, so you set everything in page mode after that point. | | All the other minor destinations will be set in page-mode, hence we will feed the pageStores instead of the Routing and queuing them. | Yes. anonymous wrote : | Setting a global limit is easy, the problem is how and when to start depaging when the global limit was achieved. | You can start depaging when total memory size drops to MAX_GLOBAL_MEMORY_SIZE - PAGE_SIZE View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173251#4173251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173251

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: runServer is broken on trunk...

by timfox

"timfox" wrote : This is not fixed in trunk. I meant this is *now* fixed in trunk ;) It's amazing how much difference a single letter can make. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173247#4173247 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173247

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: runServer is broken on trunk...

by timfox

This is not fixed in trunk. Remoting configuration like host, port etc is now specific to the transport (see config). The old jndi server was assuming to use the same old host attribute for its own server (which no longer exists). The jndi server host/port config is now separate - we can't really assume that they're the same anyway. Also I renamed the "Main" bean to "JNDIServer" to make it clearer what it is. Since we allow system property substitution, the user could use ${host.name} (or whatever it is called these days) to use the same host value for jndi server and transport config if they wanted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173245#4173245 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173245

16 years

1
0
0 / 0

[Design of EJB 3.0] - Depends metadata ignored if no xml file present

by bstansberry＠jboss.com

Been working on adding dependencies on the specified HAPartition for clustered EJB2/3 beans (https://jira.jboss.org/jira/browse/JBAS-4952 ) and am seeing an issue with EJB3. The way I'm doing this is with a deployer that add an item to the JBossEnterpriseBeanMetaData.getDepends() set for clustered beans. This works fine for EJB2 beans and for EJB3 jars with an xml descriptor. But it doesn't work if there is no xml descriptor. I tracked the issue down to this in Ejb3Deployment: | protected void deployElement(Ejb3HandlerFactory factory, ClassFile cf, InitialContext ctx) throws Exception | { | Ejb3Handler handler = factory.createHandler(cf); | handler.setCtxProperties(unit.getJndiProperties()); | | if (handler.isEjb() || handler.isJBossBeanType()) | { | List<Container> containers = handler.getContainers(cf, this); | The handler.getContainers() call is what results in various metadata being converted into annotations on the container, including the conversion of JBossEnterpriseBeanMetaData.getDepends() into @Depends. The annotations are what ultimately drive the creation of MC dependencies. The problem is if there's no xml the "if (handler.isEjb() || handler.isJBossBeanType())" test returns false, and the whole thing is short-circuited. Besides impacting my particular task, I wonder if this is a general problem -- other types of metadata that deployers might add won't make it onto the annotations that drive actual behavior. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173223#4173223 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173223

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging discussion:

by clebert.suconic＠jboss.com

"clebert.suconic(a)jboss.com" wrote : I have configured a server with -Xms64M and -Xms64M, configured MaxSize at 10M on my destination and I was able to send 500K messages to the server, without having a consumer, and later consume then as nothing special was happening. | I had the server throwing an OME at one of my tests today, because of the big buffer allocated on .load(). I will probably change load to just use a FileChannel. (I see no reason to read the whole file in memory). I think it is so cool to have the possibility of running the server under low memory. If it was a big change I wouldn't consider it but since it is a simple one, I will do it. (Unless anyone sees any problems) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173192#4173192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173192

16 years

1
0
0 / 0

[Design of JBoss jBPM] - mavenize enterprise

by alex.guizar＠jboss.com

This post is about JBPM-1268 and JBPM-1287. In jBPM 3.2.3 the enterprise modules consisted of: jbpm-enterprise.jar - enterprise services and their backing EJBs. jbpm-console.war the JSF-based console modified to reference the above EJBs. jbpm-enterprise.ear a container for the above two. In addition, the Cactus test framework required a jbpm-test.ear to run tests from inside the app server. Only jbpm-enterprise.jar was mavenized, though the other enterprise modules had to be mavenized as well. Was there a reason not to do so? If not, JBPM-1268 needs to be reopened. Given the deadline for 3.3.0.CR1 it would have to be scheduled for a later version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173188#4173188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173188

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - runServer is broken on trunk...

by clebert.suconic＠jboss.com

As part of my merge and work on paging on trunk, I'm trying to run the server, perfSender.. etc. ant runServer is broken: runServer: | [java] 15:34:48,145 ERROR @main [AbstractKernelController] Error installing to Configured: name=Main state=Instantiated | [java] java.lang.IllegalArgumentException: No such property host for bean org.jboss.messaging.core.config.impl.FileConfiguration available [journalSyncTransactional, packetConfirmationBatchSize, bindingsDirectory, requireDestinations, interceptorClassNames, journalMinFiles, createJournalDir, createBindingsDir, class, securityEnabled, journalFileSize, journalType, securityInvalidationInterval, journalMaxAIO, configurationUrl, connectionScanPeriod, pagingDirectory, callTimeout, backup, scheduledThreadPoolMaxSize, acceptorInfos, journalSyncNonTransactional, JMXManagementEnabled, journalDirectory, clustered] | [java] at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:160) | [java] at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:237) | [java] at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.get(AbstractKernelControllerContext.java:226) | [java] at org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData.getValue(AbstractDependencyValueMetaData.java:171) | | I had to add the property host on ConfigurationImpl to make the server start. After I made it start, but then perfSender/perfListener is not working. The JNDI is refusing the connection: | [java] at org.jboss.jms.example.PerfExample.runSender(PerfExample.java:128) | [java] at org.jboss.jms.example.PerfExample.main(PerfExample.java:102) | [java] Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] | [java] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:276) | [java] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1572) | [java] ... 6 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173182#4173182 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173182

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2008