May 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: ESB Monitoring and Metrics : what should be monitored?

by kukeltje

for each service: maximum time of processing a message average time of message processing standard deviation of message processing time messages/min over 1 minute period messages/min over 5 minute period messages/min over 60 minute period maximum wait time for a message to be processed ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050331#4050331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050331

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: task forms

by kukeltje

anonymous wrote : I also believe that any application we develop that is targeted towards participants/managers would at best be useful as a demo... I agree, but in the demo, you present it to management and they are very 'picky' on these simple kinds of things, so if it is possible (by just detecting the kind of role) to either presenting the form or a tasklist, we should do that. If the app becomes to complicated, we maybe should deploy to apps? One just for users and one for more stuff? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050323#4050323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050323

17 years, 7 months

1
0
0 / 0

[Design of JBossCache] - Re: Binding proxy to Cache in AS JNDI

by bstansberry＠jboss.com

End of my monologue... Coming off the above referenced forum thread, there's now an AS JIRA for solving the original problem: http://jira.jboss.com/jira/browse/JBAS-4456 Doubtful this will be done before JBC 2.0, so for the 2.0 doc section on JNDI binding, I'm just going to make a comment that the old method won't work and include a link to the JIRA issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050310#4050310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050310

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JRMPProxyFactory equivalent for POJO Services

by bstansberry＠jboss.com

Perfect. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050304#4050304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050304

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JRMPProxyFactory equivalent for POJO Services

by scott.stark＠jboss.org

No, its a remoting integration aspect that needs to be supplied. Its simple enough to create one as this example does. The based aspects for the client should be externalized though, and the jndi binding should be done via an aspect on this bean. I have created a jbas issue for the replacement. http://jira.jboss.com/jira/browse/JBAS-4456 | package org.jboss.profileservice.remoting; | | import java.util.ArrayList; | | import javax.naming.InitialContext; | | import org.jboss.aop.Dispatcher; | import org.jboss.aop.advice.Interceptor; | import org.jboss.aop.proxy.Proxy; | import org.jboss.aspects.remoting.InvokeRemoteInterceptor; | import org.jboss.aspects.remoting.MergeMetaDataInterceptor; | import org.jboss.aspects.remoting.Remoting; | import org.jboss.aspects.security.SecurityClientInterceptor; | import org.jboss.deployers.spi.management.ManagementView; | import org.jboss.logging.Logger; | import org.jboss.profileservice.spi.ProfileService; | import org.jboss.remoting.InvokerLocator; | import org.jboss.util.naming.Util; | | /** | * An aop/remoting proxy factory bean that exposes the ProfileService | * interfaces. | * | * @author Scott.Stark(a)jboss.org | * @version $Revision:$ | */ | public class ProxyFactory | { | private static final Logger log = Logger.getLogger(ProxyFactory.class); | private String dispatchName = "ProfileService"; | private String jndiName = "ProfileService"; | private InvokerLocator locator; | private ProfileService ps; | private ManagementView mgtView; | private Proxy psProxy; | private Proxy mgtViewProxy; | | public String getDispatchName() | { | return dispatchName; | } | | public void setDispatchName(String dispatchName) | { | this.dispatchName = dispatchName; | } | | public String getJndiName() | { | return jndiName; | } | | public void setJndiName(String jndiName) | { | this.jndiName = jndiName; | } | | public InvokerLocator getLocator() | { | return locator; | } | | public void setLocator(InvokerLocator locator) | { | this.locator = locator; | } | | public ProfileService getProfileService() | { | return ps; | } | | public void setProfileService(ProfileService ps) | { | this.ps = ps; | } | | public Proxy getProfileServiceProxy() | { | return psProxy; | } | | public ManagementView getViewManager() | { | return mgtView; | } | public void setViewManager(ManagementView mgtView) | { | this.mgtView = mgtView; | } | | public Proxy getManagementViewProxy() | { | return mgtViewProxy; | } | | public void start() | throws Exception | { | ClassLoader loader = Thread.currentThread().getContextClassLoader(); | Class[] ifaces = {ProfileService.class}; | | // Create the ProfileService proxy | Dispatcher.singleton.registerTarget(dispatchName, ps); | | ArrayList<Interceptor> interceptors = new ArrayList<Interceptor>(); | interceptors.add(SecurityClientInterceptor.singleton); | interceptors.add(MergeMetaDataInterceptor.singleton); | interceptors.add(InvokeRemoteInterceptor.singleton); | | psProxy = Remoting.createRemoteProxy(dispatchName, loader, ifaces, locator, | interceptors, "ProfileService"); | InitialContext ctx = new InitialContext(); | Util.bind(ctx, jndiName, psProxy); | | // Create the ManagementView proxy | Class[] mvIfaces = {ManagementView.class}; | String mvDispatchName = dispatchName+".ManagementView"; | Dispatcher.singleton.registerTarget(mvDispatchName, mgtView); | mgtViewProxy = Remoting.createRemoteProxy(mvDispatchName, loader, mvIfaces, locator, | interceptors, "ProfileService"); | log.debug("Bound ProfileService proxy"); | } | | public void stop() | throws Exception | { | ClassLoader loader = Thread.currentThread().getContextClassLoader(); | Dispatcher.singleton.unregisterTarget(dispatchName); | String mvDispatchName = dispatchName+".ManagementView"; | Dispatcher.singleton.unregisterTarget(mvDispatchName); | InitialContext ctx = new InitialContext(); | Util.unbind(ctx, jndiName); | log.debug("Unbound ProfileService proxy"); | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050299#4050299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050299

17 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB Monitoring and Metrics : what should be monitored?

by kurt.stam＠jboss.com

Monitoring and managing are two different things. I think management: - What listeners/services are running? - Recycle the listener/service both of which are close to what we already have for an .esb archive (See the jmx-console) monitoring: - Is the listener/service alive? - How many messages are waiting to be processed? - How old is the oldest message? and here I'd like to add: - Statistics/history on message processing over time: Messages/min for each service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050288#4050288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050288

17 years, 7 months

1
0
0 / 0

[Design of JBossCache] - Re: Binding proxy to Cache in AS JNDI

by bstansberry＠jboss.com

See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109907 for the better solution. But, here's a related issue.... Say we solve the Cache issue and a remote Cache proxy is available. Any API call that requires use of a Node will fail, since the Node won't be a remote object. The only available API will be those methods that don't involve a Node. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050284#4050284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050284

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - JRMPProxyFactory equivalent for POJO Services

by bstansberry＠jboss.com

Does AS 5 have any POJO equivalent to the JRMPProxyFactory? I.e. a service you can create where you inject some POJO service, an InvokerLocator, a JNDI name and an interface name, and it creates a Remoting proxy to your service and binds it in JNDI? Had a quick look at @JndiBinding but it seems that just does a simple binding. Looks like the needed stuff is there in org.jboss.aspects.remoting.Remoting, but wondered if there is work being done on /plan for a service or aspect that packages it all together. This is needed for JBC, which can no longer expose a Cache proxy via JNDI since no mbean service implements the Cache interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050282#4050282 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050282

17 years, 7 months

1
0
0 / 0

[Design of JBossCache] - Re: Binding proxy to Cache in AS JNDI

by bstansberry＠jboss.com

The JRMPProxyFactory does have one potentially useful config option. If your service (say CacheJmxWrapper) exposes this method in its mbean interface: public Object invoke(Invocation mi) throws Exception then you can set the "InvokeTargetMethod" attribute on JRMPProxyFactory to 'false'. If configured that way, the detached invoker won't try to invoke the target method (e.g. get(fqn, key)) but rather will invoke the invoke(Invocation mi) method. It is then the responsibility of your service to read the target method and args from the Invocation and decide how to deal with them. This is how EJB2 containers work. In the CacheJmxWrapper case, its implementation of invoke(Invocation mi) would read the method name/args from the invocation and use reflection to invoke on the wrapped Cache. Something like that could certainly be implemented, but not in the JBC code base. JBC does not have visibility to the Invocation class. I would have to implement it in the AS code base. Want to find a better solution, as this seems like a general AS 5 problem -- exposing Remoting-capable proxies for POJO services. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050279#4050279 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050279

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Topic filterSelector

by misge

Hello everybody, I would like to ask you if it is possible to have filter selectors in the Topic in order to dispatch messages into another Topic instead of an MDB. If yes can you please provide me with the appropriate configuration? Regards, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050278#4050278 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050278

17 years, 7 months

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 May 2007