March 2009 - jboss-dev-forums - Jboss List Archives

[Design of Management Features on JBoss] - Re: Connection Factory managed component types and templates

by charles.crouch＠jboss.com

Here is the jira I mentioned: https://jira.jboss.org/jira/browse/JBAS-6667 Rename managed component subtype on TxConnectionFactoryDeploymentMetaData.java to be "Tx" rather than "XA" View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220755#4220755 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220755

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: task attributes

by tom.baeyens＠jboss.com

handlers indeed make sense. that way we can avoid putting it in the public api and in jpdl. then we can go more slowly on introducing only the features that we know for sure are the right ones. and with handlers in the right place, we'll have more possibilities then in jbpm 3. i'll publish a task handler in the next beta release. ronald (and other community members), could you have a look after the release if the task handler and evaluate it for these criteria: 1) making jpdl simpler 2) delegating all complex things to a task handler 3) task handler covers more use cases then we can handle in jbpm 3 ronald, do you see a violation of what we did in relation to bpmn or ws-human-task ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220744#4220744 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220744

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Semantic on Session.stop and MessageHandler

by timfox

A couple of issues with the latest commit: 1) The logic in setMessageHandler() doesn't look right: When setting a non null message handler, then it remains stopped so any messages won't get delivered. Messages are being requeued if the previous handler was null but even if the current handler is null 2) receive() method: while ((stopped || (m = buffer.poll()) == null) && !closed && toWait > 0) It will stay in the loop as long as the consumer is stopped. This is not correct - receive should always return after timeout, it's just that if it's stopped then it should always return null. Can you make sure the above are captured in tests? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220738#4220738 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220738

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: intermittent failures i am seeing

by clebert.suconic＠jboss.com

+PagingFailoverTests (after the latest clustering changes). The stresstestsuite will confirm that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220732#4220732 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220732

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Error while using Wise Soap Client

by ashwindesikan

I asssume you are using eclipse, if so then do the following steps and you should able to add tools.jar to classpath 1. Open Preference dialog 2. choose java --> Installed JREs 3. Choose your preferred JRE and select edit 4. select the option Add External Jars and add to it tools.jar from your JDK's lib folder recycle your sever and you would see in the logs at bootup the classpath contains tools.jar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220731#4220731 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220731

16 years, 9 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: JBAS-6089: Disable Client Auto-Discovery By Default?

by galder.zamarreno＠jboss.com

https://jira.jboss.org/jira/browse/JBAS-6666 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220712#4220712 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220712

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: intermittent failures i am seeing

by timfox

"ataylor" wrote : | | | | 2. JMSFailoverTest. sometimes the wrong exception is thrown, but it may be valid | | | | I have run this over 600 times now in a loop with no failures. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220698#4220698 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220698

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: intermittent failures i am seeing

by clebert.suconic＠jboss.com

anonymous wrote : 1. MessageChunkTest This test will use a lot of disk. *Maybe* if you are using your disk for something else or if your disk is slow, this test could fail. I have ran it for 100 times.. no failures. But I will keep an eye on the test. 2) I have seen it on Hudson. We should investigate it. 3) This was raised as part of https://jira.jboss.org/jira/browse/JBMESSAGING-1551. It may be related to a different issue besides of Redistribution but we don't know yet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220694#4220694 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220694

16 years, 9 months

1
0
0 / 0

[Design of Management Features on JBoss] - Connection Factory managed component types and templates

by charles.crouch＠jboss.com

I wanted to start this thread to bring together a number of JIRAs and to clarify with how we're planning to proceed with managing Connection Factory's in Embedded Jopr and JON. First here are the jiras which seem to touch on this topic: https://jira.jboss.org/jira/browse/JOPR-108 Add support for local-tx connection factories https://jira.jboss.org/jira/browse/JBAS-6647 "XAConnectionFactoryTemplate" and possibly other templates are missing from ManagementView The path of least resistance seems to be for there to be two connection factory related management components: @ManagementComponent(type="ConnectionFactory",subtype="Tx") *Note the change from subtype="XA" today* @ManagementComponent(type="ConnectionFactory",subtype="NoTx") Where the "Tx" component would represent both local-tx and XA connection factories. The Tx component can have boolean config property for whether this is an XA connection factory. This approach also matches how the existing connection factory descriptors are laid out. It also means we don't need any new templates since the ones we have should be sufficient: ManagementView.getTemplateNames() returns the following Strings: [TxConnectionFactoryTemplate, NoTxConnectionFactoryTemplate, ...] Unless we hear otherwise we'll push ahead with this approach on our side and I'll raise a jira for changing the subtype from XA to Tx in... https://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/connector/src... Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220681#4220681 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220681

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - intermittent failures i am seeing

by ataylor

1. MessageChunkTest Timed out waiting for response when sending packet 43 | | MessagingException[errorCode=3 message=Timed out waiting for response when sending packet 43] | at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.sendBlocking(RemotingConnectionImpl.java:1107) | at org.jboss.messaging.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:500) | at org.jboss.messaging.tests.integration.chunkmessage.ChunkTestBase.testChunks(ChunkTestBase.java:191) | at org.jboss.messaging.tests.integration.chunkmessage.ChunkTestBase.testChunks(ChunkTestBase.java:94) | at org.jboss.messaging.tests.integration.chunkmessage.MessageChunkTest.testMessageChunkFilePersistenceBlocked(MessageChunkTest.java:300) | 2. JMSFailoverTest. sometimes the wrong exception is thrown, but it may be valid expected:<MessagingException[errorCode=2 message=null]> but was:<MessagingException[errorCode=102 message=The conn has been closed by the server]> | | junit.framework.AssertionFailedError: expected:<MessagingException[errorCode=2 message=null]> but was:<MessagingException[errorCode=102 message=The conn has been closed by the server]> | at org.jboss.messaging.tests.integration.jms.cluster.JMSFailoverTest.testManualFailover(JMSFailoverTest.java:283) | 3. SymmetricClusterWithDiscoveryTest (i see this on different tests) Timed out waiting for bindings (bindingCount = 23, totConsumers = 22 | | java.lang.IllegalStateException: Timed out waiting for bindings (bindingCount = 23, totConsumers = 22 | at org.jboss.messaging.tests.integration.cluster.distribution.ClusterTestBase.waitForBindings(ClusterTestBase.java:220) | at org.jboss.messaging.tests.integration.cluster.distribution.SymmetricClusterTest.testMixtureLoadBalancedAndNonLoadBalancedQueues(SymmetricClusterTest.java:428) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220671#4220671 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220671

16 years, 9 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 March 2009