September 2008 - jboss-dev-forums

[Design of JBoss Profiler] - JBoss Profiler 2 memory analysis

by angusm

In the jboss-profiler.properties there is a memory option; but I can not see any reference to memory in the generated snapshot files (overview.txt etc). In an extremely rapid perusal of the source I can not see much reference to memory either. Have I missed something, or is this something to come? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178920#4178920 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178920

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by mimra

Yes that sounds great. I'll create a JIRA and post a patch. Let's just agree on "copyParentKey" for attribute name. Hmm - one more thing though; I've made the change to the 3.2.2 code because I use this in the JBoss ESB 4.4.GA which comes with jBPM 3.2.2. If I make this change to jBPM 3.2.3 it won't be of much help if the ESB guys don't upgrade to 3.2.3 with the next ESB release... I'll have a look at the 3.2.3 - if the class in question hasn't changed in 3.2.3 we can make the patch in both 3.2.2 and 3.2.3... /Michael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178917#4178917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178917

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by camunda

Agreed. Maybe we can agree, that inherit the parent key is easy to solve, a valuable use case and we have a volunteer :-) So I would propse: Go ahead! If you don't have committer access post the code here and I can commit it. One remaining problem is, that the XSD can not be changed in minor versions (or is that allowed? Koen? Is it possible in major versions?), so that XSD and designer support will still lack, but the implementation can be already done I think. The only important choice is how the attribute is named, I would suggest "copyParentKey" (because it is in the SuperProcess, "inherit" is from the perspective of the SubProcess). But please open a jira issue for it... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178913#4178913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178913

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Also, it seems that doing a mvn clean gets rid of ouput/eclipse-classes, so I need to do a full rebuild in Eclipse after that View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178908#4178908 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178908

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Hi Paul, As discussed earlier, I am splitting asintegration into some new modules. While updating the release script I noticed that there is no javadoc being generated in the mavenized build. The release build expects to find these under aop/output/api aspects/output/api etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178907#4178907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178907

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Deploying web services in service archive

by alessio.soldano＠jboss.com

I've been looking at https://jira.jboss.org/jira/browse/JBWS-2246. As Adrew correctly pointed out, the problem here is that the jbossws deployer relies upon injection into beans declared in server//deploy/jbossws.sar/META-INF/jboss-beans.xml which of course are not available at startup till jbossws.sar itself is deployed. I'd say everything required for the deployment should go to server//deployers to solve this. But I'm wondering if leaving part of the beans involved in the deployment (mainly the stack specific ones) in the jbossws.sar was done on purpose for a reason I'm missing. Perhaps Thomas or Heiko can suggest here. I've done some tests, anyway, manually moving all the deploy stuff to server//deployers. The problem I see now with JSE endpoints in sar archives is that jbossws needs the classloader to instanciate classes that live in the generated webapp. To achieve this during the deployment the UnifiedMetaDataDeploymentAspect reads the the context classloader from the JBossWebMetaData. That classloader is previously set in the JBossWebMetaData by the TomcatDeployment, but of course that only happens after the jboss.web:service=WebServer is started (and that lives in server//deploy). So the problem in JBWS-2246 would stay, unless we find another solution for this too. Any suggestion? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178893#4178893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178893

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by clebert.suconic＠jboss.com

As soon as you're done with your changes I will simplify it (if you haven't done so already). As we were talking on IRC, we could just set counter as (System.currentTimeMillis() & MASK_TIME) << 32), and aways get IDs from there with a simple counter.incrementAndGet(). That would be enough to guarantee uniqueIDs on the Node after a restart. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178891#4178891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178891

17 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal clustering problem, a JBoss cache issue??

by michaelchan

Portal: 2.6.3, AS: 4.2.2 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178868#4178868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178868

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Testing Bootstrap Dependencies

by istudens＠redhat.com

There is a short look at my current implementation. I have not followed Adrian's advice yet, because I don't know how to implement his idea. I can't even start JBoss server with empty deploy/ directory. Therefore I don't have any clue, how to at first start the AS with empty deploy directory and then deploy an ear and after that all services from all/deploy. I have not even followed Brian's advice, because after trying methods from org.jboss.test.deployers.AbstractDeploymentTest I have found out that they test a structure of deployment only and hence they pass even if the deployment of the tested SAR fails. Now my test creates a different profile for each tested module. The snippet of build.xml:  | <target name="bootstrap-dependency-tests" description="Tests bootstrap deployment dependency in new JBossMC."> |  | <create-bootstrapdependency-config baseconf="all" conf="bootstrapdependencyJBAS5349-EJB3Session"> | <module-patternset> | <include name="bootstrapdependency-ejb3-sessionbean.jar"/> | </module-patternset> | </create-bootstrapdependency-config> | <server:start name="bootstrapdependencyJBAS5349-EJB3Session"/> | <run-junit junit.patternset="bootstrap-dependency.includes" | junit.configuration="EJB3Session" /> | <server:stop name="bootstrapdependencyJBAS5349-EJB3Session"/> |  | <create-bootstrapdependency-config baseconf="all" conf="bootstrapdependencyJBAS5349-EJB3Entity"> | <module-patternset> | <include name="bootstrapdependency-ejb3-entitybean.jar"/> | </module-patternset> | </create-bootstrapdependency-config> | <server:start name="bootstrapdependencyJBAS5349-EJB3Entity"/> | <run-junit junit.patternset="bootstrap-dependency.includes" | junit.configuration="EJB3Entity" /> | <server:stop name="bootstrapdependencyJBAS5349-EJB3Entity"/> | ... The macro 'create-bootstrapdependency-config' is defined in the imports/server-config.xml: <macrodef name="create-bootstrapdependency-config" | description="Create a configuration based on 'all' profile"> | <attribute name="conf" /> | <attribute name="baseconf" /> | <element name="module-patternset" /> | <sequential> | <server:config> | <server name="@{conf}" host="${node0}"> | <jvmarg value="-Xms128m" /> | <jvmarg value="-Xmx512m" /> | <jvmarg value="-XX:MaxPermSize=512m" /> | <jvmarg value="-XX:+HeapDumpOnOutOfMemoryError" /> | <sysproperty key="java.net.preferIPv4Stack" value="true" /> | <sysproperty key="java.endorsed.dirs" value="${jboss.dist}/lib/endorsed" /> | <sysproperty key="jgroups.udp.ip_ttl" value="${jbosstest.udp.ip_ttl}" /> | </server> | </server:config> | <delete dir="${jboss.dist}/server/@{conf}" /> | <create-config baseconf="@{baseconf}" newconf="@{conf}" newconf-src="bootstrap-dependency"> | <patternset> | <include name="conf/**" /> | <include name="deployers/**" /> | <include name="deploy/**" /> | <include name="lib/**" /> | </patternset> | </create-config> | <copy todir="${jboss.dist}/server/(a){conf}/deploy/Aaabootstrapdependency-jbas5349.sar" | filtering="false"> | <fileset dir="${build.lib}"> | <patternset> | <module-patternset /> | </patternset> | </fileset> | </copy> | </sequential> | </macrodef> I have probably discovered a bug in the 'run-junit' macro in the file import/server-config.xml. There is an argument 'junit.configuration' which sets a 'report.ext' property. This argument should differentiate the outputs of repeatedly runing test. I am not sure if anyone has ever used this, because it does not work. The 'run-junit' macro uses the 'report.ext' property to remember an extension of test name, but in ant any property cannot be changed after it was once set. It means that if you run this macro twice with different junit.configuration arguments, you will get the same report.ext property value and it will be the value of the first one. So I have rewritten this macro to use a property ${report.ext.(a){junit.configuration}} instead of ${report.ext} and simplified the syntax of condition to:  | <condition property="report.ext.(a){junit.configuration}" value=".xml" else="-(a){junit.configuration}.xml"> | <equals arg1="" arg2="@{junit.configuration}" /> | </condition> I hope that checking of a status of the SAR's MBean is reliable manner method how to test the result of deployment. I consider it to be the best way how to do it.. the best one I know :) Should I commit the new test to the https://svn.jboss.org/repos/jbossas/trunk/testsuite/? Should I report the issue of run-junit's bug? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178855#4178855 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178855

17 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portal clustering problem, a JBoss cache issue??

by prabhat.jha＠jboss.com

Which portal and JBoss AS version? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178850#4178850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178850

17 years, 3 months

1
0
0 / 0

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