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

[Design of POJO Server] - Re: trunk testsuite status

by anil.saldhana＠jboss.com

This is after I checked out the workspace and did a clean build(nuked third party etc). | 2007-03-24 00:22:45,046 DEBUG [org.jboss.system.server.profileservice.ServerImpl] Failed to start | java.lang.OutOfMemoryError: Java heap space | 2007-03-24 00:22:45,046 ERROR [STDERR] Exception in thread "main" | 2007-03-24 00:22:45,046 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space | Maybe you are trying with different thirdparty libraries for aop/remoting that are different from what are in build-thirdparty.xml | asaldhana~/JB5/trunk/testsuite>ant tests-jacc-security | Buildfile: build.xml | Overriding previous definition of reference to jboss.test.classpath | | tests-jacc-security: | [echo] creating jacc config | [copy] Copying 187 files to C:\cygwin\home\asaldhana\JB5\trunk\build\output | \jboss-5.0.0.Beta2\server\jacc | [echo] Overwriting config descriptors | [copy] Copying 6 files to C:\cygwin\home\asaldhana\JB5\trunk\build\output\j | boss-5.0.0.Beta2\server\jacc | [server:start] Starting server "jacc" with command: | [server:start] C:\Java\jdk1.5.0_10\bin\java -cp C:\cygwin\home\asaldhana\JB5\tru | nk\build\output\jboss-5.0.0.Beta2\bin\run.jar;c:\java\jdk1.5.0_10\lib\tools.jar | org.jboss.Main -c jacc -b localhost | | BUILD FAILED | C:\cygwin\home\asaldhana\JB5\trunk\testsuite\build.xml:2341: Error starting serv | er "jacc": Server failed to start; see logs. exit code: 0 | | Total time: 2 minutes 42 seconds | asaldhana~/JB5/trunk/testsuite> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031261#4031261 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031261

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: trunk testsuite status

by scott.stark＠jboss.org

That test runs to completion for me, but has many errors. Its not affected by the memory leak issue. | [starksm@succubus testsuite]$ ant tests-jacc-security | Buildfile: build.xml | Overriding previous definition of reference to jboss.test.classpath | | tests-jacc-security: | [echo] creating jacc config | [copy] Copying 187 files to /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/jacc | [echo] Overwriting config descriptors | [copy] Copying 7 files to /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/jacc | [server:start] Starting server "jacc" with command: | [server:start] /usr/java/jdk1.5.0_09/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/bin/run.jar:/usr/java/jdk1.5.0_09/lib/tools.jar org.jboss.Main -c jacc -b localhost | [echo] Starting patternset=jacc.includes config=JACC | [junit] Running org.jboss.test.cmp2.audit.test.AuditUnitTestCase | [junit] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 3.659 sec | [junit] Test org.jboss.test.cmp2.audit.test.AuditUnitTestCase FAILED | [junit] Running org.jboss.test.cmp2.cmrstress.CMRStressTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.319 sec | [junit] Test org.jboss.test.cmp2.cmrstress.CMRStressTestCase FAILED | [junit] Running org.jboss.test.cmp2.cmrtransaction.test.CMRTransactionUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.288 sec | [junit] Test org.jboss.test.cmp2.cmrtransaction.test.CMRTransactionUnitTestCase FAILED | [junit] Running org.jboss.test.cmp2.commerce.CompleteUnitTestCase | [junit] Tests run: 32, Failures: 0, Errors: 31, Time elapsed: 2.404 sec | [junit] Test org.jboss.test.cmp2.commerce.CompleteUnitTestCase FAILED | [junit] Running org.jboss.test.cmp2.perf.test.PerfUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.325 sec | [junit] Test org.jboss.test.cmp2.perf.test.PerfUnitTestCase FAILED | [junit] Running org.jboss.test.cmp2.relationship.RelationshipUnitTestCase | [junit] Tests run: 21, Failures: 0, Errors: 21, Time elapsed: 2.141 sec | [junit] Test org.jboss.test.cmp2.relationship.RelationshipUnitTestCase FAILED | [junit] Running org.jboss.test.cmp2.simple.SimpleUnitTestCase | [junit] Tests run: 44, Failures: 0, Errors: 44, Time elapsed: 1.214 sec | [junit] Test org.jboss.test.cmp2.simple.SimpleUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.CallerInRoleUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.152 sec | [junit] Test org.jboss.test.jacc.test.CallerInRoleUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.EJBSpecUnitTestCase | [junit] Tests run: 23, Failures: 2, Errors: 20, Time elapsed: 4.275 sec | [junit] Test org.jboss.test.jacc.test.EJBSpecUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.FormAuthUnitTestCase | [junit] Tests run: 5, Failures: 4, Errors: 0, Time elapsed: 3.477 sec | [junit] Test org.jboss.test.jacc.test.FormAuthUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.JMXConsoleUnitTestCase | [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.171 sec | [junit] Running org.jboss.test.jacc.test.MissingMethodUnitTestCase | [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 1.359 sec | [junit] Test org.jboss.test.jacc.test.MissingMethodUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.WebConstraintsUnitTestCase | [junit] Tests run: 4, Failures: 0, Errors: 3, Time elapsed: 0.768 sec | [junit] Test org.jboss.test.jacc.test.WebConstraintsUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.WebIntegrationUnitTestCase | [junit] Tests run: 37, Failures: 2, Errors: 22, Time elapsed: 4.829 sec | [junit] Test org.jboss.test.jacc.test.WebIntegrationUnitTestCase FAILED | [junit] Running org.jboss.test.jacc.test.WebPermissionsValidationTestCase | [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.579 sec | [junit] Test org.jboss.test.jacc.test.WebPermissionsValidationTestCase FAILED | [junit] Running org.jboss.test.web.test.UserInRoleUnitTestCase | [junit] Tests run: 4, Failures: 0, Errors: 3, Time elapsed: 0.973 sec | [junit] Test org.jboss.test.web.test.UserInRoleUnitTestCase FAILED | [junit] Running org.jboss.test.webservice.jbws309.JBWS309TestCase | [junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 4.478 sec | [junit] Test org.jboss.test.webservice.jbws309.JBWS309TestCase FAILED | [server:stop] Shutting down server: jacc | [server:stop] Shutting down server: /usr/java/jdk1.5.0_09/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/bin/shutdown.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jbossall-client.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jboss-common.jar org.jboss.Shutdown --server jnp://localhost:1099 --shutdown | [server:stop] shutdownTimeout will be=45 | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031259#4031259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031259

17 years, 3 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SecurityContext

by anil.saldhana＠jboss.com

Moving on to the concept of JBossSubject an end result of authentication, we have many variations of Subjects to consider: a) JAAS Subject. b) SAML Subject c) WS-Trust Security Token (that contains claims about a trusted identity like name etc). d) XACML Subject e) Custom subject. Of these the structure of JAAS, SAML and XACML are well defined. WS-T security token is open-ended with scope for custom tokens. I am thinking that JBossSubject should be a composition of these subjects , rather than an union of constituents of these individual subjects. My Choice: | public class JBossSubject | { | List<Object> theSubjects; | | public <T> void addSubject(T subject); | } | A particular case I have in mind is when an authenticated subject has multiple identities (a jaas subject, saml subject, a security token etc) and the authorization layer can make a decision based on some configuration, in the presence of multiple subject types for a particular identity. For the record, a ws-trust security token can be saml, x509, username/pwd or custom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031257#4031257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031257

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by flavia.rainone＠jboss.com

Hi! I changed that in version 2.0, and I added a javadoc documenting the rules related to getArguments(): | /** | * Returns a non-null array containing all method arguments. | * <p> | * The returned array can be changed by the advice or interceptor accordingly. All | * changes are reflected on joinpoint execution, and are noticed as well by | * other advices and interceptors that are executed after the current one. | * <br> | * However, changes to this array are limited to the scope of current advice | * execution, and must be performed before execution of {@link #invokeNext()}, | * {@link #invokeNext(Interceptor[])}, or {@link #invokeTarget()} method. | * Otherwise, inconsistency on joinpoint argument values may be noticed. | * | * @return the method arguments | */ | public Object[] getArguments() | The main cause of this was the use of annotated arguments on before/after advices (new feature of JBoss AOP 2.0). A before/after advice can receive the arguments array as a parameter: | public void beforeAdvice(@Args Object[] arguments) | { | // do something before joinpoint execution | } | Kabir and I decided that an advice that receives arguments would be called to intercept all types of joinpoint, even though arguments array would be null during a field read joinpoint. Given that, and considering I couldn't find a documentation on getArguments method returning a null value (please, Kabir, let me know if there is one), I thought that the arguments array should be a non-null value during the interception of other joinpoint types (hence, for methods with no arguments, the arguments array should be an empty array). Since the intention is to make @Args annotated parameters consistent with [InvocationType].getArguments() and [InvocationType].setArguments() methods, I changed getArguments method to return always a non-null value, as you can see on the javadoc comments (notice that these methods are available only on Invocation classes that are equivalent to joinpoints with a valid arguments list, which excludes the FieldReadInvocation class). So, this is the reason for which I changed that. I apologize for causing any trouble. Now, I think we need to decide whether we keep things this way, or we make arguments array null on methods and constructors with an empty argument list. Any thoughts? Kabir? Clebert? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031255#4031255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031255

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: trunk testsuite status

by anil.saldhana＠jboss.com

Is the test suite totally unusable now? In the afternoon, I tried running the target "tests-jacc-security". Had OOME. Jacc server config did not start. Scott, should we wait till the leaks are fixed with Kabir's proposed new 2.0.0.alpha5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031252#4031252 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031252

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: trunk testsuite status

by scott.stark＠jboss.org

I tried running with: aop: 2.0.0.alpha4 jbm: 1.2.0.SP.snapshot.aop2beta remoting: 2.2.0.GA and the run did complete although there still were OMEs. Apparently it got further along and limped to completion. I then ran with: aop: snapshot jbm: 1.2.0.SP.snapshot.aop2beta remoting: 2.2.0.GA and the run completed without OMEs. So there are both aop and remoting leaks that are fixed in these latter versions. Can you create an 2.0.0.alpha5 release of aop Kabir. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031248#4031248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031248

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by scott.stark＠jboss.org

I would just make the check more robust: | if (mi.getArguments() != null && mi.getArguments().length() == 1) | { | jbm.setText(mi.getArguments()[0].toString()); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031244#4031244 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031244

17 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossDDObjectFactory use of SystemPropertiesService

by wolfc

The backport to jbossxb (now 1.0.0-CR9-brew) is needed for EJB3 plugin (/ AS 4.2). I've got a module jboss-metamodel-dd in ejb3 which currently is the mavenized version. It still needs a proper place and proper dependencies. Note that JBossWS stuff is not working there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031211#4031211 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031211

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Depends on microcontainer bean in -service.xml

by bstansberry＠jboss.com

To atone, I've put up a couple more entries in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainerFAQ. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031183#4031183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031183

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by clebert.suconic＠jboss.com

this returns null or aop1.x if I call someMethod(); if (mi.getArguments() != null) | { | jbm.setText((String)mi.getArguments()[0]); | } | While it returns something different with aop 2.0 Notice that I have an overloaded method.. where I can do either someMethod() or someMethod(String). Our aop binding is set on: <bind pointcut="execution(* org.jboss.jms.client.delegate.ClientSessionDelegate->createTextMessage(..))"> | <advice name="handleCreateTextMessage" aspect="org.jboss.jms.client.container.SessionAspect"/> | </bind> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031176#4031176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031176

17 years, 3 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 March 2007