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

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite issues with multicast routing (JBAS-4939)

by akostadinov

I've started a topic in the clustering forum http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123075 And I verified that JBoss AS 4.2 doesn't have any issues with the clustering test suite on RHEL 4U5. That was run on dev03 with command "./build.sh tests-clustering -Dnode0=localhost -Dnode1=`hostname` -DudpGroup=$MCAST_ADDR" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102193#4102193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102193

18 years, 5 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - JBoss server mcast socket bound to network interface

by akostadinov

Hallo, We currently have an issue with running JBoss AS 5 test suite on RHEL 4U5 and above with one node bound to localhost. Please see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123056 for full details. Generally On RHEL 4U5 and above when a multicast listener binds to a network interface and a sender is bound to the same interface, the listener can't see any messages unless the multicast route goes through the same interface. (that is not the case with RHEL 4U4 where listener sees messages) I think because of that if a server is bound to localhost, it can't see mcast messages sent by himself. Thus AS 5 is starting very slowly. So what I suggest is setting IP_MULTICAST_LOOP on the jgroups mcast socket so it hopefully fix that issue. As well not bind the mcast socket to the interface where server was specified to bind with the "-b" option. That way listener will see mcast messages no matter what multicast route the host has. That is a better behavior besides that it makes test suite runs much more convenient and less error prone. When for example a network admin reroutes the network he will expect that the running AS server will not stop sending/receiving multicast messages properly without needing to add special parameters. As well I don't see any disadvantages in not specifying network interface to bind to. And if there are rare cases with such, the user can specify a startup option to fix that. And behavior will not be much different compared with that on RHEL 4U4 and below. Please let me know what do you think about that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102190#4102190 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102190

18 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: re: Feedback requested on throttling ejb calls

by ScottMarlowNovell

The org.jboss.aspects.concurrent Semaphore aspect does what I had in mind. I would also like a way to share the Semaphore instances (used internally by the Semaphore aspect) between multiple components. For example, I might want immutable application components to share a named Semaphore that has 64 permits and mutable components to share a named Semaphore that has 8 permits. Sound like a good enhancement? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102188#4102188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102188

18 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Extension of the Designer

by magro1202

Hi my first approach works now. i can select elements in a tree, change or add values and send the XML to the processdefinition within the action node. the problem now is, that i have no semantic information about the custom elements, e.g. for validation or choose the elements via content assistent in the editor. So what i need is to extend the XML Schema of the processdefinition by the custom elements. is it possible to extend the Schema dynamically during runtime by loading a custom Schema and add the additional information? Regards Matthias View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102187#4102187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102187

18 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Failing FileVFSUnitTestCase.testVFSFileURIFactory in VFS

by alesj

What needs to be closed here | public void testFileExists() | throws Exception | { | File tmpRoot = File.createTempFile("vfs", ".root"); | tmpRoot.delete(); | tmpRoot.mkdir(); | File tmp = File.createTempFile("testFileExists", null, tmpRoot); | log.info("+++ testFileExists, tmp="+tmp.getCanonicalPath()); | | URL rootURL = tmpRoot.toURL(); | VFS vfs = VFS.getVFS(rootURL); | VirtualFile tmpVF = vfs.findChild(tmp.getName()); | assertTrue(tmpVF.getPathName()+".exists()", tmpVF.exists()); | assertTrue("tmp.delete()", tmp.delete()); | assertFalse(tmpVF.getPathName()+".exists()", tmpVF.exists()); | assertTrue(tmpRoot+".delete()", tmpRoot.delete()); | } | in order to be able to delete tmp file on Winz? This worked for the URLConnection test case: | InputStream in = conn.getInputStream(); | long lastModified; | try | { | lastModified = conn.getLastModified(); | System.out.println("lastModified, "+lastModified); | assertNotSame("lastModified", 0, lastModified); | } | finally | { | in.close(); | } | assertTrue(tmp.getAbsolutePath()+" deleted", tmp.delete()); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102184#4102184 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102184

18 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: re: Feedback requested on throttling ejb calls

by kabir.khan＠jboss.com

Such an aspect should be part of the https://svn.jboss.org/repos/jbossas/projects/aop/trunk/aspects/ project. The org.jboss.aspects.concurrent package contains some Semaphore aspects, but I am not sure what they do View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102169#4102169 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102169

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Instance annotations from Object Models

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : | I'm still not clear on what is needed for the aop aspects configuration. | The idea is to replace this code + related methods: | private void addEjbAnnotations(EJBContainer container, | JBossEnterpriseBeanMetaData enterpriseBean) throws Exception | { | if (enterpriseBean != null) | { | if (enterpriseBean instanceof JBossSessionBeanMetaData) | { | addHomeAnnotations(container, (JBossSessionBeanMetaData) enterpriseBean); | | addJndiAnnotations(container, (JBossSessionBeanMetaData) enterpriseBean); | } | | addInterceptorMethodAnnotations(container, enterpriseBean); | | handleResourceRefs(container, enterpriseBean.getResourceReferences()); | | addMessageDestinationAnnotations(container, enterpriseBean.getMessageDestinationReferences()); | | addSecurityIdentityAnnotation(container, enterpriseBean.getSecurityIdentity()); | | addDependencies(container, enterpriseBean); | | addPoolAnnotations(container, enterpriseBean); | | addXmlAnnotations(container, enterpriseBean); | | if (enterpriseBean instanceof JBossSessionBeanMetaData) | { | addConcurrentAnnotations(container, (JBossSessionBeanMetaData)enterpriseBean); | addClusterAnnotations(container, (JBossSessionBeanMetaData)enterpriseBean); | addCacheAnnotations(container, (JBossSessionBeanMetaData)enterpriseBean); | } | } | } | with something that loads into the INSTANCE mutable metadata. My preference would be to make this a visitor pattern over the metadata itself, e.g. | MutableMetaData mmd = deploymentUnit.getMutableMetaData(); | MetaDataVisitor visitor = new MetaDataVisitor(mmd, ...); | visitor.visit(enterpriseBean); | Which is much more extensible/maintainable and OO than the current EJB3 sutff. Each part of the JavaEE/JBoss metadata can decide if/where it goes in the annotation view. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102164#4102164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102164

18 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Initial Implementation Merged to Trunk

by richard.opalka＠jboss.com

Sure, I'm going to create the WiKi document(s) for that now. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102159#4102159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102159

18 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Initial Implementation Merged to Trunk

by thomas.diesler＠jboss.com

Thanks Richard. Could you please create a wiki page that explains how your implementation is designed and how it is supposed to work? I believe you already did something similar in the dev forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102156#4102156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102156

18 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - WS-RM Initial Implementation Merged to Trunk

by richard.opalka＠jboss.com

Hi Folks, I have merged ropalka branch to the trunk on Thomas request so now you can evaluate the current state of WS-RM prototype. To execute the WS-RM tests just issue the following command: ./build.sh -Dtest=jaxws/wsrm test In test.log you can see the exchanged messages. Just FYI WS-RM tests are executed agains WS-RM endpoint emulator and there's no RM message store there yet. Any comments, suggestions and criticism is welcome ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102151#4102151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102151

18 years, 5 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 November 2007