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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Weird deadlock I had today... (Repost)

by clebert.suconic＠jboss.com

To replicate this: I - Open org.jboss.messaging.tests.performance.paging.MeasurePagingMultiThreadTest II - Change testPagingMultipleSenders to: | public void testPagingMultipleSenders() throws Throwable | { | | final int NUMBER_OF_THREADS = 18; | final int NUMBER_OF_MESSAGES = 100; | final int SIZE_OF_MESSAGE = 1024; | | Configuration config = createDefaultConfig(); | | HashMap<String, QueueSettings> settings = new HashMap<String, QueueSettings>(); | | config.setPagingMaxGlobalSizeBytes(20 * 1024); | config.setJournalSyncNonTransactional(true); | III - run the test inside Eclipse. Wait some time...., and call the kill -3 on the process. (I aways do killall -3 java) My disk is somewhat slow at sync, maybe because it is really syncing and not using any caching. If you don't get the deadlock, use a higher number of Messages as your disk may be faster. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194201#4194201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194201

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Weird deadlock I had today...

by clebert.suconic＠jboss.com

To replicate this: I - Open org.jboss.messaging.tests.performance.paging.MeasurePagingMultiThreadTest II - Change testPagingMultipleSenders to: | public void testPagingMultipleSenders() throws Throwable | { | | final int NUMBER_OF_THREADS = 18; | final int NUMBER_OF_MESSAGES = 100; | final int SIZE_OF_MESSAGE = 1024; | | Configuration config = createDefaultConfig(); | | HashMap<String, QueueSettings> settings = new HashMap<String, QueueSettings>(); | | config.setPagingMaxGlobalSizeBytes(20 * 1024); | config.setJournalSyncTransactional(true); | III - run the test inside Eclipse. Wait some time...., and call the kill -3 on the process. (I aways do killall -3 java) My disk is somewhat slow at sync, maybe because it is really syncing and not using any caching. If you don't get the deadlock, use a higher number of Messages as your disk may be faster. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194201#4194201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194201

17 years, 4 months

1
0
0 / 0

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

by clebert.suconic＠jboss.com

The only missing parts now are: 13) Add a limit number of Threads limit on the Main Executor for depage. (Which is a very minor task) 8-9) it will be made as part of another task and 10) Which is not directly related to Paging itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194198#4194198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194198

17 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - JBAS-6188, track-connection-by-tx

by scott.stark＠jboss.org

https://jira.jboss.org/jira/browse/JBAS-6188, and issue showing up with the deprecated track-connection-by-tx property is that its only allowed value for a local tx ds is true. Should this property be dropped from the management interface? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194191#4194191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194191

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Weird deadlock I had today...

by clebert.suconic＠jboss.com

What happened on my test was a call to close taking longer than PING_TIME. The test was sending 100 messages, in 10 threads. All the sends were being performed asynchronously, and every PersistentMessage sent was syncing the page (it would be same effect on Journal if using NIO). When close was called, it had to wait the pending commands to finish, what took longer than the PING_TIME. But you shouldn't have a DeadLock on that case.. right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194180#4194180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194180

17 years, 4 months

1
0
0 / 0

[JBoss Portal Documentation] - Dcoumentation on configuring richfaces in Admin portlet of J

by jmaan

Can somebody suggest the documentation on how to configure and implement richfaces in Admin portlet of JBoss Portal. I found the info in bits and pieces that did not help to correctly configure and implement it in admin portlet (i.e. user specific personalized dashboard) Any help, thanks in advance. JMN View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194176#4194176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194176

17 years, 4 months

1
0
0 / 0

[Other JBoss Development Design] - Call custom run.conf during startup

by napwill

Does anyone know how to call a custom run.conf at startup? I'm running multiple profiles/jvms on the same server. I use a separate script to start each jvm, that all share the same run.conf. There is one jvm that requires a separate run.conf file because of additional variables that are being loaded during startup. Therefore I need to call that custom run.conf separately. Is that possible? ex. jvm1, jvm2, jvm3 all use scripts that call a shared run.conf at startup ; jvm4 needs to call custom_run.conf at startup. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194163#4194163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194163

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Weird deadlock I had today...

by clebert.suconic＠jboss.com

Can I be an user for one second? :-) I need help! now! Urgent! (Hopefully you won't send me to the user's forum :-P ) Jokes apart: I wrote a test on trunk that was using a lot of disk (doing too many syncs), what left my box at some unusable state. (I couldn't even click anywhere). When the test was over, it dead locked on the following condition, which I wanted to share with you guys. I didn't do any investigation yet.. just registering for future investigations for now. | Found one Java-level deadlock: | ============================= | "Thread-4 (group:jbm-pinger-threads-1418257117)": | waiting to lock monitor 0x00007f514714fc28 (object 0x00007f5177468c88, a java.lang.Object), | which is held by "Thread-0 (group:jbm-pinger-threads-1418257117)" | "Thread-0 (group:jbm-pinger-threads-1418257117)": | waiting to lock monitor 0x00007f5147204e48 (object 0x00007f51774c80c0, a java.lang.Object), | which is held by "Thread-4 (group:jbm-pinger-threads-1418257117)" | | Java stack information for the threads listed above: | =================================================== | "Thread-4 (group:jbm-pinger-threads-1418257117)": | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.destroy(RemotingConnectionImpl.java:446) | - waiting to lock <0x00007f5177468c88> (a java.lang.Object) | at org.jboss.messaging.core.client.impl.ConnectionManagerImpl.connectionFailed(ConnectionManagerImpl.java:545) | - locked <0x00007f51774c80c0> (a java.lang.Object) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.callListeners(RemotingConnectionImpl.java:544) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.fail(RemotingConnectionImpl.java:431) | - locked <0x00007f517740f448> (a java.lang.Object) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$Pinger.run(RemotingConnectionImpl.java:1557) | - locked <0x00007f517740f350> (a org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$Pinger) | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) | at java.lang.Thread.run(Thread.java:619) | "Thread-0 (group:jbm-pinger-threads-1418257117)": | at org.jboss.messaging.core.client.impl.ConnectionManagerImpl.connectionFailed(ConnectionManagerImpl.java:436) | - waiting to lock <0x00007f51774c80c0> (a java.lang.Object) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.callListeners(RemotingConnectionImpl.java:544) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.fail(RemotingConnectionImpl.java:431) | - locked <0x00007f5177468c88> (a java.lang.Object) | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$Pinger.run(RemotingConnectionImpl.java:1557) | - locked <0x00007f5177449738> (a org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$Pinger) | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) | at java.lang.Thread.run(Thread.java:619) | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194161#4194161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194161

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 Strict ordering via ordering groups

by ataylor

Ive written some tests to verify that the current GroupingRoundRobinDistributionPolicy will provide strict ordering. Apart from one slight problem it does. The problem is that the GroupingRoundRobinDistributionPolicy tries available consumers until it finds one it can use. If one is busy then it tries the next available. If a queue holds a set of messages that belong to two different groups, and the queue has 2 consumers, as soon as consumer 1 is started it will try to deliver the messages and both groups can be pinned to the first consumer before the second consumer can be started. Of course The user could make sure that the session is started before any messages are delivered to the queue, but since the session:start method is non blocking the first messages could still arrive before all consumers are started. making the start method a blocking call would fix this tho. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194151#4194151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194151

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging code review (Repost)

by clebert.suconic＠jboss.com

5) The tricky part on paging is to let depage happen at the same time messages are being paged. Depage will aways return old pages, but when depageRate>pageRate, we will eventually be depaging the currentPage, on which case I open a newPage and return the current one. But if no messages were produced on that new page, it will be empty. When we return that empty page, we will exit the pageMode and from that point we will start using the journal again. This is done this way because I can't lock page while depaging records. It all happens concurrently. Once an address enters in pageMode, it will be in pageMode until the rate of removing messages on page is higher the rate on adding messages from page. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194097#4194097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194097

17 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2008