You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by "Matheus Piai Bianconi (JIRA)" <ca...@jakarta.apache.org> on 2004/12/06 13:51:20 UTC
[jira] Created: (CACTUS-158) OutOfMemory in application server
OutOfMemory in application server
---------------------------------
Key: CACTUS-158
URL: http://nagoya.apache.org/jira/browse/CACTUS-158
Project: Cactus
Type: Bug
Components: Ant Integration
Reporter: Matheus Piai Bianconi
Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: cactus:compile doesn't work ?
Posted by Nicolas Chalumeau <ni...@gmail.com>.
Ok for this.
I just want to know how execute this integration first. I try to
integrate it in maven but whith your comment I realize that the ant
integration should be done before...
Nicolas,
On Sun, 12 Dec 2004 20:14:25 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> Hi Nicolas,
>
> > -----Original Message-----
> > From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> > Sent: dimanche 12 décembre 2004 19:41
> > To: Cactus Developers List
> > Subject: Re: cactus:compile doesn't work ?
> >
> > Ok so will use the cvs head instead
>
> The Cargo branch is for migrating the Ant integration to using Cargo. It's
> in a branch because it's a pretty big refactoring and I wanted to share my
> work with you all before it was finished so that others could possibly help
> too (or at least see where it is going).
>
> So either you're working on the cargo refactoring (which I thought you were
> from the email you sent me) or you're not (in which case you should
> definitely not use this branch).
>
> Thanks
> -Vincent
>
> >
> >
> > On Sun, 12 Dec 2004 19:34:39 +0100, Vincent Massol <vm...@pivolis.com>
> > wrote:
> > > Hi Nicolas,
> > >
> > > I have no idea but remember that this branch is definitely not working
> > as
> > > what I had committed in the Ant integration module was not working yet.
> > >
> > > Thanks
> > > -Vincent
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> > > > Sent: dimanche 12 décembre 2004 19:13
> > > > To: Cactus Developers List
> > > > Subject: cactus:compile doesn't work ?
> > > >
> > > > I was using the cvs cargo integration branch to help with a patch. It
> > > > seems to be some jdk version problem (I have a 1.4 version of the
> > > > jdk). Is this branch work for you ?
> > > >
> > > > I have the following error :
> > > >
> > > > java:compile:
> > > > [echo] Compiling to
> > > > d:\java\myProjects\jakarta-
> > > > cactus\integration\maven\samples\servlet/target/classes
> > > >
> > > > cactus:compile:
> > > > [javac] Compiling 4 source files to
> > > > D:\java\myProjects\jakarta-
> > > > cactus\integration\maven\samples\servlet\target\test-cactu
> > > > s-classes
> > > > javac: invalid source release:
> > > > Usage: javac <options> <source files>
> > > > where possible options include:
> > > > -g Generate all debugging info
> > > > -g:none Generate no debugging info
> > > > -g:{lines,vars,source} Generate only some debugging info
> > > > -nowarn Generate no warnings
> > > > -verbose Output messages about what the compiler is
> > > > doing
> > > > -deprecation Output source locations where deprecated
> > > > APIs are used
> > > > -classpath <path> Specify where to find user class files
> > > > -sourcepath <path> Specify where to find input source files
> > > > -bootclasspath <path> Override location of bootstrap class files
> > > > -extdirs <dirs> Override location of installed extensions
> > > > -d <directory> Specify where to place generated class
> > files
> > > > -encoding <encoding> Specify character encoding used by source
> > > > files
> > > > -source <release> Provide source compatibility with
> > specified
> > > > release
> > > > -target <release> Generate class files for specific VM
> > version
> > > > -help Print a synopsis of standard options
> > > >
> > > >
> > > > BUILD FAILED
> > > > File...... C:\Documents and
> > > > Settings\PropriÚtaire\.maven\cache\cactus-maven-1.7dev\plugin.jelly
> > > > Element... ant:javac
> > > > Line...... 193
> > > > Column.... 107
> > > > Compile failed; see the compiler error output for details.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: cactus:compile doesn't work ?
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Nicolas,
> -----Original Message-----
> From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> Sent: dimanche 12 décembre 2004 19:41
> To: Cactus Developers List
> Subject: Re: cactus:compile doesn't work ?
>
> Ok so will use the cvs head instead
The Cargo branch is for migrating the Ant integration to using Cargo. It's
in a branch because it's a pretty big refactoring and I wanted to share my
work with you all before it was finished so that others could possibly help
too (or at least see where it is going).
So either you're working on the cargo refactoring (which I thought you were
from the email you sent me) or you're not (in which case you should
definitely not use this branch).
Thanks
-Vincent
>
>
> On Sun, 12 Dec 2004 19:34:39 +0100, Vincent Massol <vm...@pivolis.com>
> wrote:
> > Hi Nicolas,
> >
> > I have no idea but remember that this branch is definitely not working
> as
> > what I had committed in the Ant integration module was not working yet.
> >
> > Thanks
> > -Vincent
> >
> >
> >
> > > -----Original Message-----
> > > From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> > > Sent: dimanche 12 décembre 2004 19:13
> > > To: Cactus Developers List
> > > Subject: cactus:compile doesn't work ?
> > >
> > > I was using the cvs cargo integration branch to help with a patch. It
> > > seems to be some jdk version problem (I have a 1.4 version of the
> > > jdk). Is this branch work for you ?
> > >
> > > I have the following error :
> > >
> > > java:compile:
> > > [echo] Compiling to
> > > d:\java\myProjects\jakarta-
> > > cactus\integration\maven\samples\servlet/target/classes
> > >
> > > cactus:compile:
> > > [javac] Compiling 4 source files to
> > > D:\java\myProjects\jakarta-
> > > cactus\integration\maven\samples\servlet\target\test-cactu
> > > s-classes
> > > javac: invalid source release:
> > > Usage: javac <options> <source files>
> > > where possible options include:
> > > -g Generate all debugging info
> > > -g:none Generate no debugging info
> > > -g:{lines,vars,source} Generate only some debugging info
> > > -nowarn Generate no warnings
> > > -verbose Output messages about what the compiler is
> > > doing
> > > -deprecation Output source locations where deprecated
> > > APIs are used
> > > -classpath <path> Specify where to find user class files
> > > -sourcepath <path> Specify where to find input source files
> > > -bootclasspath <path> Override location of bootstrap class files
> > > -extdirs <dirs> Override location of installed extensions
> > > -d <directory> Specify where to place generated class
> files
> > > -encoding <encoding> Specify character encoding used by source
> > > files
> > > -source <release> Provide source compatibility with
> specified
> > > release
> > > -target <release> Generate class files for specific VM
> version
> > > -help Print a synopsis of standard options
> > >
> > >
> > > BUILD FAILED
> > > File...... C:\Documents and
> > > Settings\PropriÚtaire\.maven\cache\cactus-maven-1.7dev\plugin.jelly
> > > Element... ant:javac
> > > Line...... 193
> > > Column.... 107
> > > Compile failed; see the compiler error output for details.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: cactus:compile doesn't work ?
Posted by Nicolas Chalumeau <ni...@gmail.com>.
Ok so will use the cvs head instead
On Sun, 12 Dec 2004 19:34:39 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> Hi Nicolas,
>
> I have no idea but remember that this branch is definitely not working as
> what I had committed in the Ant integration module was not working yet.
>
> Thanks
> -Vincent
>
>
>
> > -----Original Message-----
> > From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> > Sent: dimanche 12 décembre 2004 19:13
> > To: Cactus Developers List
> > Subject: cactus:compile doesn't work ?
> >
> > I was using the cvs cargo integration branch to help with a patch. It
> > seems to be some jdk version problem (I have a 1.4 version of the
> > jdk). Is this branch work for you ?
> >
> > I have the following error :
> >
> > java:compile:
> > [echo] Compiling to
> > d:\java\myProjects\jakarta-
> > cactus\integration\maven\samples\servlet/target/classes
> >
> > cactus:compile:
> > [javac] Compiling 4 source files to
> > D:\java\myProjects\jakarta-
> > cactus\integration\maven\samples\servlet\target\test-cactu
> > s-classes
> > javac: invalid source release:
> > Usage: javac <options> <source files>
> > where possible options include:
> > -g Generate all debugging info
> > -g:none Generate no debugging info
> > -g:{lines,vars,source} Generate only some debugging info
> > -nowarn Generate no warnings
> > -verbose Output messages about what the compiler is
> > doing
> > -deprecation Output source locations where deprecated
> > APIs are used
> > -classpath <path> Specify where to find user class files
> > -sourcepath <path> Specify where to find input source files
> > -bootclasspath <path> Override location of bootstrap class files
> > -extdirs <dirs> Override location of installed extensions
> > -d <directory> Specify where to place generated class files
> > -encoding <encoding> Specify character encoding used by source
> > files
> > -source <release> Provide source compatibility with specified
> > release
> > -target <release> Generate class files for specific VM version
> > -help Print a synopsis of standard options
> >
> >
> > BUILD FAILED
> > File...... C:\Documents and
> > Settings\PropriÚtaire\.maven\cache\cactus-maven-1.7dev\plugin.jelly
> > Element... ant:javac
> > Line...... 193
> > Column.... 107
> > Compile failed; see the compiler error output for details.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: cactus:compile doesn't work ?
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Nicolas,
I have no idea but remember that this branch is definitely not working as
what I had committed in the Ant integration module was not working yet.
Thanks
-Vincent
> -----Original Message-----
> From: Nicolas Chalumeau [mailto:nicolas.chalumeau@gmail.com]
> Sent: dimanche 12 décembre 2004 19:13
> To: Cactus Developers List
> Subject: cactus:compile doesn't work ?
>
> I was using the cvs cargo integration branch to help with a patch. It
> seems to be some jdk version problem (I have a 1.4 version of the
> jdk). Is this branch work for you ?
>
> I have the following error :
>
> java:compile:
> [echo] Compiling to
> d:\java\myProjects\jakarta-
> cactus\integration\maven\samples\servlet/target/classes
>
> cactus:compile:
> [javac] Compiling 4 source files to
> D:\java\myProjects\jakarta-
> cactus\integration\maven\samples\servlet\target\test-cactu
> s-classes
> javac: invalid source release:
> Usage: javac <options> <source files>
> where possible options include:
> -g Generate all debugging info
> -g:none Generate no debugging info
> -g:{lines,vars,source} Generate only some debugging info
> -nowarn Generate no warnings
> -verbose Output messages about what the compiler is
> doing
> -deprecation Output source locations where deprecated
> APIs are used
> -classpath <path> Specify where to find user class files
> -sourcepath <path> Specify where to find input source files
> -bootclasspath <path> Override location of bootstrap class files
> -extdirs <dirs> Override location of installed extensions
> -d <directory> Specify where to place generated class files
> -encoding <encoding> Specify character encoding used by source
> files
> -source <release> Provide source compatibility with specified
> release
> -target <release> Generate class files for specific VM version
> -help Print a synopsis of standard options
>
>
> BUILD FAILED
> File...... C:\Documents and
> Settings\PropriÚtaire\.maven\cache\cactus-maven-1.7dev\plugin.jelly
> Element... ant:javac
> Line...... 193
> Column.... 107
> Compile failed; see the compiler error output for details.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
cactus:compile doesn't work ?
Posted by Nicolas Chalumeau <ni...@gmail.com>.
I was using the cvs cargo integration branch to help with a patch. It
seems to be some jdk version problem (I have a 1.4 version of the
jdk). Is this branch work for you ?
I have the following error :
java:compile:
[echo] Compiling to
d:\java\myProjects\jakarta-cactus\integration\maven\samples\servlet/target/classes
cactus:compile:
[javac] Compiling 4 source files to
D:\java\myProjects\jakarta-cactus\integration\maven\samples\servlet\target\test-cactu
s-classes
javac: invalid source release:
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated
APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-help Print a synopsis of standard options
BUILD FAILED
File...... C:\Documents and
Settings\PropriÚtaire\.maven\cache\cactus-maven-1.7dev\plugin.jelly
Element... ant:javac
Line...... 193
Column.... 107
Compile failed; see the compiler error output for details.
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Updated: (CACTUS-158) OutOfMemory in application server
Posted by "Matheus Piai Bianconi (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=history ]
Matheus Piai Bianconi updated CACTUS-158:
-----------------------------------------
Attachment: CACTUS_158.patch
This is the patch - it hasn't been fully tested yet, but it should work.
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Updated: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=history ]
Felipe Leme updated CACTUS-158:
-------------------------------
type: Improvement (was: Bug)
Version: 1.6.1
Fix Version: 1.7
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Improvement
> Components: Ant Integration
> Versions: 1.6.1
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Fix For: 1.7
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Vincent Massol (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56513 ]
Vincent Massol commented on CACTUS-158:
---------------------------------------
I haven't tried them but sounds good to me!
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Improvement
> Components: Ant Integration
> Versions: 1.6.1
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Fix For: 1.7
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Matheus Piai Bianconi (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56274 ]
Matheus Piai Bianconi commented on CACTUS-158:
----------------------------------------------
PS: We are working on a solution and will send a patch later (even though this solution may not be generic).
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56508 ]
Felipe Leme commented on CACTUS-158:
------------------------------------
Nevermind, I figured out the solution: calling createJvmarg().setLines() instead of createJvmarg().setValue().
In fact, that's exactly what the setJvmargs method does:
public void setJvmargs(String s) {
log("The jvmargs attribute is deprecated. "
+ "Please use nested jvmarg elements.", Project.MSG_WARN);
cmdl.createVmArgument().setLine(s);
}
public Commandline.Argument createJvmarg() {
return cmdl.createVmArgument();
}
So, I fixed that - the only pending issue now is which properties to use on the maven plugin.
-- Felipe
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Versions: 1.6.1
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Fix For: 1.7
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Closed: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=history ]
Felipe Leme closed CACTUS-158:
------------------------------
Resolution: Fixed
I also applied the changes to the maven plugin - please let me know if they're fine...
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Improvement
> Components: Ant Integration
> Versions: 1.6.1
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Fix For: 1.7
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Vincent Massol (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56504 ]
Vincent Massol commented on CACTUS-158:
---------------------------------------
Hi Matheus,
Just a quick question: why don't you call java.setJvmargs() instead of calling java.createJvmarg().setValue(...)? Does your solution work when you have to pass several JVM arguments?
I'm curious because I've used setJvmargs() for Cargo and it is working fine.
Thanks
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Vincent Massol (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56509 ]
Vincent Massol commented on CACTUS-158:
---------------------------------------
ok, I get it. I've fixed Cargo accordingly. Thanks.
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Improvement
> Components: Ant Integration
> Versions: 1.6.1
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Fix For: 1.7
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Vincent Massol (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56421 ]
Vincent Massol commented on CACTUS-158:
---------------------------------------
Fyi, just done that for Cargo. See http://jira.codehaus.org/browse/CARGO-89
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Vincent Massol (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56507 ]
Vincent Massol commented on CACTUS-158:
---------------------------------------
Felipe,
1/ About the deprecation. This should only happen if you use <java jvmarsg="...">. You shouldn't get it at the Java API level (at least I did not notice it when I've done the change on Cargo - Maybe I've just missed it).
2/ About the maven plugin. I think having one per container is the most flexible and would be useful to run cactus tests on several containers at once. You could always have a generic one and then have each container-specific one default to the generic one.
thanks
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Assigned: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=history ]
Felipe Leme reassigned CACTUS-158:
----------------------------------
Assign To: Felipe Leme
Vincent,
What about the maven plugin? Should we create a generic property for all containers (like cactus.containers.jvmArgs) or one per container (cactus.jboss3x.jvmArgs, cactus.tomcat5.jvmArgs, etc...)?
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: [jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Felipe,
Sounds very good. Feel free to fix it in Cactus. We'll also need to do the
same fix in Cargo.
Personally I'd love Cactus to move as quickly as possible on cargo:
1/ because that will fix a bunch of existing issues
2/ because I'm working actively on Cargo and I can also participate much
more there
Let me know if you're interested to help in moving Cactus to Cargo. If so,
we can have a chat, say this Thursday or Friday, so that I can introduce you
to Cargo.
Let me know what you think
Thanks a lot
-Vincent
> -----Original Message-----
> From: Felipe Leme (JIRA) [mailto:cactus-dev@jakarta.apache.org]
> Sent: mercredi 8 décembre 2004 12:08
> To: cactus-dev@jakarta.apache.org
> Subject: [jira] Commented: (CACTUS-158) OutOfMemory in application server
>
> [ http://nagoya.apache.org/jira/browse/CACTUS-
> 158?page=comments#action_56376 ]
>
> Felipe Leme commented on CACTUS-158:
> ------------------------------------
>
> Vincent,
>
> I haven't seen the patch yet, but I have the feeling there are 2 places
> where we should consider a generic approach:
>
> 1.This issue might happens in any container, not only JBoss, so the fix
> should go into the super-class of all container tasks (I think it should
> be defined on AbstractContainerJava or somthing like that). Note also that
> this issue might be appliable to Cargo as well.
>
> 2.The Java Ant tasks has a method to set the max memory; using that method
> should fix that specific problem, but we could be generic here too,
> allowing arbitrary JVM args to be passed to the container.
>
> Once we define a way to fix it, I could implement the changes. So, any
> thoughts?
>
> -- Felipe
>
>
> > OutOfMemory in application server
> > ---------------------------------
> >
> > Key: CACTUS-158
> > URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> > Project: Cactus
> > Type: Bug
> > Components: Ant Integration
> > Reporter: Matheus Piai Bianconi
>
> >
> > Cactus does not allow to define memory used by application server, then
> some tests fail and error "OutOfMemoryError" occur.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://nagoya.apache.org/jira/secure/Administrators.jspa
> -
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56376 ]
Felipe Leme commented on CACTUS-158:
------------------------------------
Vincent,
I haven't seen the patch yet, but I have the feeling there are 2 places where we should consider a generic approach:
1.This issue might happens in any container, not only JBoss, so the fix should go into the super-class of all container tasks (I think it should be defined on AbstractContainerJava or somthing like that). Note also that this issue might be appliable to Cargo as well.
2.The Java Ant tasks has a method to set the max memory; using that method should fix that specific problem, but we could be generic here too, allowing arbitrary JVM args to be passed to the container.
Once we define a way to fix it, I could implement the changes. So, any thoughts?
-- Felipe
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
[jira] Commented: (CACTUS-158) OutOfMemory in application server
Posted by "Felipe Leme (JIRA)" <ca...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/CACTUS-158?page=comments#action_56506 ]
Felipe Leme commented on CACTUS-158:
------------------------------------
Vincent,
I tried the setJvmArgs, but got the following message:
[cactus] The jvmargs attribute is deprecated. Please use nested jvmarg elemets.
Did you get that with Cargo too?
I haven't found a @deprecated in the Ant's API, so I think this message is a bug - I think it was meant only to the Ant task, not the java call (i.e., it should be displayed only when jvmargs is passed as an attribute to the java task).
-- Felipe
> OutOfMemory in application server
> ---------------------------------
>
> Key: CACTUS-158
> URL: http://nagoya.apache.org/jira/browse/CACTUS-158
> Project: Cactus
> Type: Bug
> Components: Ant Integration
> Reporter: Matheus Piai Bianconi
> Assignee: Felipe Leme
> Attachments: CACTUS_158.patch
>
> Cactus does not allow to define memory used by application server, then some tests fail and error "OutOfMemoryError" occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org