September 2006 - jboss-dev-forums

[Design of JBoss jBPM] - Re: bpel build script updates

by alex.guizar＠jboss.com

It still works. While I checked, I noticed the library build does not work outside Eclipse because my external dependencies are not in the compile path. I added commons-lang, jboss-jaxrpc, jboss-saaj and wsdl4j. I also updated jaxen to beta10 as the current beta6 causes my tests to fail and missing bpel artifact references. Finally, I changed the console and service builds to use project-local artifacts. Tom, let me know if the dependency updates cause your builds to fail. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974724#3974724 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974724

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

If a session executor's thread is currently executing onMessage() and close() is called on the consumer from a different thread, the closing thread is put on wait until the listener code execution completes. Take a look at MessasgeCallbackHandler.waitForOnMessageToComplete() (the method body, and also, its invocation point) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974709#3974709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974709

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

"tim_fox" wrote : ... when you close a consumer, closing() first gets called on the ServerConsumerEndpoint, this causes stop() to be called, which waits for any deliveries of messages to the client which might be in progress to complete first. | | Once that is done, the actual client consumer is closed and removed from the callback manager. Looking a the code again, I noticed something I missed the first time around. When MessageCallbackHandler gets a message, it does one of two things: 1. If a thread is blocked in receive(), it wakes up the thread and returns. 2. If a MessageListener is registered, it queues up a Runnable to call onMessage(). Now, 1 is irrelevant if the MessageConsumer has called close(), so I thought the point was to make sure that a MessageConsumer didn't close while a listener was in onMessage(). But it looks like that could still happen. Is that ok? Just curious. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974707#3974707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974707

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: PropertyManager

by mark.little＠jboss.com

Here's an updated config file: | <?xml version="1.0" encoding="ISO-8859-1"?> |  |  |  | <esb | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:noNamespaceSchemaLocation="jbossesb-1_0.xsd"> | <properties name="core"> | <property name="org.jboss.soa.esb.jndi.server.type" value="jboss"/> | <property name="org.jboss.soa.esb.jndi.server.url" value="localhost"/> |  |  |  | </properties> | <properties name="transports" depends="core"> | <property name="org.jboss.soa.esb.mail.smtp.host" value="localhost"/> | <property name="org.jboss.soa.esb.mail.smtp.user" value=""/> | <property name="org.jboss.soa.esb.mail.smtp.password" value=""/> | <property name="org.jboss.soa.esb.mail.smtp.port" value="25"/> |  |  | </properties> | <properties name="connection"> |  |  | <property name="min-pool-size" value="5"/> | <property name="max-pool=size" value="10"/> | <property name="blocking-timeout-millis" value="5000"/> |  |  |  |  | <property name="abandoned-connection-timeout" value="10000"/> | <property name="abandoned-connection-time-interval" value="30000"/> | </properties> | </esb> | I've broken the properties into different modules, with associated dependencies. The way the PropertyManager works means that it builds up a list of dependant modules in a directed acyclic graph. This means that there is a root, which can see every property below it, but nodes below cannot see properties above them: there is a level of isolation. When creating PropertyManagers, you need to specify where in the graph it is to "tie in". This obviously has an affect on what that instance can then see or do: if it goes in at the wrong level, it won't be able to see properties it may need (unless they were defined to be "system" properties, and in which case they are globally accessible.) This means that we now have isolated PropertyManagers for each module. It helps the management side of things a lot, but does mean that we have to consider where in the graph a property needs to be, or which PropertyManager we want to use to try to access it. What we have at the moment in terms of properties is pretty basic, so this 3 module approach seems about right to me. I'll check the code in now (along with some tests!) and we can discuss the structuring tomorrow. It's fairly trivial to change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974702#3974702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974702

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Rearchitecture underway

by mark.little＠jboss.com

A clarification: the rearchitecture branch is only concerned with EPRs and Message formats. No other work is being (or should be) conducted within this branch. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974700#3974700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974700

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Registry Service Design

by mark.little＠jboss.com

Given the current nature of our deployments, that sounds reasonable. Not sure about longer term, but that's something we can revisit when/if necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974697#3974697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974697

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Two PostOffices?

by timfox

Yes, one is for queues and the other is for topics. We need two since it's possible to install a queue and a topic with the same name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974696#3974696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974696

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Two PostOffices?

by clebert.suconic＠jboss.com

Why do we need to PostOffices on new configurations? Looking at /src/etc/server/default/deploy/clustered-mysql-persistence-service.xml, it looks like are two PostOffices needed. One for Topics and another one for Queues. Is there any reason for this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974691#3974691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974691

19 years, 6 months

1
0
0 / 0

[Design of JCA on JBoss] - JBAS-1429 ReAuthentication Support

by weston.price＠jboss.com

I have been working on this, and am at the point where I need to start testing...that's where the problem comes in :-) Hypersonic doesn't support changing the user identity of a connection and since this is our default, using HyperSonic for this isn't really adequate. While I can mock something up to test the mechanisms which the underlying identity changes, we need some specific JCBC vendor testsuite to really test the conditions against valid RDMBS installations. This would actually be useful for a few things ValidConnectionChecker ExceptionSorter StaleConnectionChecker (for 4.0.6) Further, we really need something like this for our JMS integration strategies with varying providers (notably WebSphereMQ). Have we ever done, thought about, anything like this beyond the installations in the labs for specific support issues? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974686#3974686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974686

19 years, 6 months

1
0
0 / 0

list error and undelivered messages

by Eric Brown

Due to a configuration error on this list[1], no email was delivered to this list which originated from the the JBoss Website Forums[2] between 7pm EST Saturday Sept 23rd, 2006 and approximately 2pm EST today, Wednesday, Sept 27th, 2006. The problem has been corrected and email is now flowing between the forums and email list as expected. Sorry for the inconvenience. [1] https://lists.jboss.org/mailman/listinfo/jboss-dev-forums [2] http://www.jboss.com/index.html?module=bb -- Eric

19 years, 6 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 September 2006