September 2008 - jboss-dev-forums

[Design of JBoss Build System] - Re: Updating versions in AOP build

by kabir.khan＠jboss.com

Thanks, That works locally, but on Hudson I get the following error: http://hudson.qa.jboss.com/hudson/view/AOP/job/jboss-aop-head-testsuite/2... | et.proxy: | | createthirdparty: | [echo] Calling mvn command located in /qa/services/hudson/hudson_workspace/workspace/jboss-aop-head-testsuite/trunk/build/../tools/maven | [java] [INFO] Scanning for projects... | [java] WAGON_VERSION: 1.0-beta-2 | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Building JBoss AOP Thirdparty | [java] [INFO] task-segment: [package] | [java] [INFO] ------------------------------------------------------------------------ | [java] Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-buildmagic-th... | [java] Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-buildmagic-th... | [java] [INFO] ------------------------------------------------------------------------ | [java] [ERROR] BUILD ERROR | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Failed to resolve artifact. | | [java] GroupId: org.jboss.maven.plugins | [java] ArtifactId: maven-buildmagic-thirdparty-plugin | [java] Version: 2.1 | | [java] Reason: Unable to download the artifact from any repository | | [java] org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin:pom:2.1 | | [java] from the specified remote repositories: | [java] central (http://repo1.maven.org/maven2) | | | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] For more information, run Maven with the -e switch | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Total time: 2 seconds | [java] [INFO] Finished at: Tue Sep 09 10:59:46 EDT 2008 | [java] [INFO] Final Memory: 6M/67M | [java] [INFO] ------------------------------------------------------------------------ | [java] Java Result: 1 | | BUILD FAILED | /qa/services/hudson/hudson_workspace/workspace/jboss-aop-head-testsuite/trunk/build/build.xml:315: Unable to build thirdparty directory. See maven output for details. | | Total time: 4 seconds | ERROR: No artifacts found that match the file pattern "trunk/aop/output/reports/". Configuration error? | ERROR: 'trunk/aop/output/reports/' doesn't match anything, but '' does. Perhaps that's what you mean? | Recording test results | Sending e-mails to: jboss-aop-builds(a)lists.jboss.org builds(a)lists.jboss.org | finished: FAILURE | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175338#4175338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175338

17 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Updating versions in AOP build

by pgier

The pom in the thirdparty directory was pointing to the 2.0.0.CR16 version of the aop parent pom in the root directory. So it was still inheriting the old dependency versions. I changed it to point to the 2.0.0-SNAPSHOT version of the aop parent (the version currently in the project root directory) and then the thirdparty build works fine. Whenever we do a release we have to remember to update the versions in all the poms. Eventually I will automate this, but right now it is manual. If you want, you can change all the poms to the next release version so you don't have to remember to do this during the release process. You just won't be able to deploy a snapshot version if the version in the poms is not snapshot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175319#4175319 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175319

17 years, 7 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Handling soft versus hard pooledInvoker exceptions in JR

by galder.zamarreno＠jboss.com

https://jira.jboss.org/jira/browse/JBAS-4963 I created this JIRA a while back to look into the differences between JRMP and Unified invoker proxies in terms of whether failover would be allowed. You could probably add your stuff in there? Feel free to assign it to yourself :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175314#4175314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175314

17 years, 7 months

1
0
0 / 0

[Design of Clustering on JBoss] - Handling soft versus hard pooledInvoker exceptions in JRMPIn

by ScottMarlowNovell

Before I create a jira for this issue, I wanted to gather some feedback. Let me know if I didn't explain this clearly enough. :-) I noticed that the PooledInvokerProxy.invoke() handles java.io.EOFException by throwing a java.rmi.ConnectException (this is in a general catch all Exception). I happened to hit this case and found that the call target (cluster member) is removed as a dead member (in JRMPInvokerProxyHA.invoke). This is not the right thing to do for java.io.EOFException which only means that the pooled connection went bad but the cluster member is still alive (in my case the cluster member was still fine.) As a quick hack, I'm going to try changing the JRMPInvokerProxyHA.invoke from the following: | catch (java.rmi.ConnectException e) | { | lastException = e; | } | To: | catch (java.rmi.ConnectException e) | { | lastException = e; | if(e.getCause() != null && e.getCause() instanceof java.io.EOFException) | { | // don't failover as we may of reached the target | invocationHasReachedAServer (invocation); | throw e; | } | } | I need to do more testing to see if this is the right approach (need to ensure that the real fail-over case still works). Perhaps there are other exceptions that should also be treated differently. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175307#4175307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175307

17 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: bundling JTS into AS 5.0

by jhalliday

ok, so I create a subdirectory under trunk/jbossas and put my jts related files in it. Now what? Hacking build/build-distr.xml to copy them into docs/examples/jts would take 30 seconds but is presumably frowned upon as further contributing to the ball of mud? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175295#4175295 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175295

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: sar vs ear packaging

by thomas.diesler＠jboss.com

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

17 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - jBPM Integration, EsbActionHandler and payload location

by p.mischke

In the last few weeks I've tried some of the jBPM-ESB integration features. Now and then I run into trouble with the payload location. I would like to discuss the problems with you. The EsbActionHandler (and EsbNotifier too) is able to map jBPM context variables to the ESB message. See samples and docs for the element. Sometimes (maybe most of time) you map more than one variable. Each mapping is given a name by the "esb" attribute. Inspecting the resulting ESB message you will see that the body of the message contains one object for each variable. They all can be retrieved inside the actions by calling message.getBody().get("myVariableName") This approach works fine when developing custom actions. But is does not work with all these useful ESB actions supplied out-of-the-box. For example the org.jboss.soa.esb.actions.soap.SOAPClient or org.jboss.soa.esb.actions.Notifier. As described in the Programmers Guide in section "Getting and Setting Data on the Message Body" all standard ESB actions expect the payload as a single object located at the default payload location. This object can be a String, a byte-array, a Map containing several more Java objects, or anything else. Nevertheless they all expect a single object. This message format is not compatible with ESB messages created by the EsbActionHandler. After discovering this contradiction I thought about using the SmooksAction to transform the message format. Unfortunately the SmooksAction expects a single object at the default payload location too :-( Another work-around is to configure a different default payload location. But this work-around only helps with a single variable. Now I am thinking about patching the EsbActionHandler to store all mapped variables inside a Map at the default payload location. I would be grateful for any ideas on this topic. Thanks in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175277#4175277 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175277

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: QueueImpl::deliverAsync

by timfox

If you set the flag to false after calling deliver, then there's a possibility deliver will never get called, and messages not delivered. Thread 1 calls deliverasync Delivery thread delivers message Thread 2 adds message to queue Thread2 calls deliverasync Already delivering so thread 2 call to deliver is ignored Delivery thread sets flag to false ==> Message gets "stuck" in queue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175276#4175276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175276

17 years, 7 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: reflect and mdr CR releases

by kabir.khan＠jboss.com

I've run into some problems http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175273#4175273 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175274#4175274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175274

17 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Updating versions in AOP build

by kabir.khan＠jboss.com

Paul, I've updated https://svn.jboss.org/repos/jbossas/projects/aop/trunk/pom.xml[/url] to point to the up to date versions of jboss-managed, jboss-reflect and jboss-mdr as requested by Adrian [url]http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142008. I then clean the aop thirdparty folder, and run the aop build. When looking at the component-info.xml's for these projects they contain the old versions. For example I have 2.0.0.CR1 for all the projects mentioned above, but their corresponding component-info.xmls show them to be | <component id="jboss/jboss-managed" | licenseType="" | version="2.0.0.Beta16" | description="" | | > | ... | <component id="jboss/jboss-mdr" | licenseType="" | version="2.0.0.Beta17" | description="" | | > | ... | <component id="jboss/jboss-reflect" | licenseType="" | version="2.0.0.Beta13" | description="" | | > | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175273#4175273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175273

17 years, 7 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 2008