Please follow standard maven directory structure to add tests, you can use
src/test/ directory.
Better to generate jar file at run time using maven and get it copied to
src/test/resources directory.
Thanks,
Krishantha.
On Tue, Jan 13, 2015 at 9:12 AM, Buddhi Senarathna budd...@wso2.com wrote:
Hi krishantha.
noted and thanks.
On Tue, Jan 13, 2015 at 2:41 PM, Krishantha Samaraweera krishan...@wso2.com
wrote:
Please follow standard maven directory structure to add tests, you can use
src/test/ directory.
Better to generate jar file at run time using maven and get it copied to
Hi Buddhi,
Please add deadlock sample as a test case for your work.
+1 for using Runtime.exec to trigger the class.
Thanks,
Krishantha.
On Tue, Jan 13, 2015 at 7:51 AM, Buddhi Senarathna budd...@wso2.com wrote:
Hi krishantha,
as you guided, i had started to create the thread analyses
Hi krishantha,
as you guided, i had started to create the thread analyses sample. creating
deadlock part is already done.
1. what else should i have to do?
2. I'm thinking of bundle this class as a jar file and use java
Processbuilder class or Runtime.exec methods to execute it as a new
process.
Hi krishantha.
Where should i have to add this test case and where should i have to place
this deadlock.jar file.
please give me an advise.
thanks.
On Tue, Jan 13, 2015 at 8:18 AM, Buddhi Senarathna budd...@wso2.com wrote:
Hi krishantha,
sure thing. i'll do that.
thanks
On Tue, Jan 13,
Hi krishantha,
sure thing. i'll do that.
thanks
On Tue, Jan 13, 2015 at 8:15 AM, Krishantha Samaraweera krishan...@wso2.com
wrote:
Hi Buddhi,
Please add deadlock sample as a test case for your work.
+1 for using Runtime.exec to trigger the class.
Thanks,
Krishantha.
On Tue, Jan 13,
Hi all,
after having a first code review, it has been suggested to do following
changes.
1. rename the class name according to the purpose
2. change pid to integer type variable
3. use enum values provided by the API where its possible
4. mbeanobject return set, but returns only one
hi all,
My task of creating a tool to take thread dumps and analyze thread info as test
framework utility is almost finished.
to had cover these task.
1. access to a process remotely using process id.
2. get thread dump of that remote process .
3. expose necessary informations of
hi all,
I'm working on creating a tool to take thread dumps and analyze thread info
as carbon test utility.
to do that i have to cover these task.
1. access to a process remotely using process id.
2. get thread dump of that remote process .
3. expose necessary informations of thread
Hi Buddi,
Are you using JStack ? By default, java thread dump does not record lock owners
for locks. If you use jstack, use -l parameter as well [1]. (eg: jstack
-l pid ). This params records lock owner information only for
synchronized blocks. Which is usefull to detect possible deadlocks.
[1]
Hi Buddhi,
On Tue, Dec 23, 2014 at 6:02 PM, Buddhi Senarathna budd...@wso2.com wrote:
hi all,
I'm working on creating a tool to take thread dumps and analyze thread
info as carbon test utility.
This should be corrected as test framework utility.
to do that i have to cover these task.
Hi hasitha,
thanks a lot, but i'm using JMX api for this. j
On Tue, Dec 23, 2014 at 6:27 PM, Hasitha Aravinda hasi...@wso2.com wrote:
Hi Buddi,
Are you using JStack ? By default, java thread dump does not record lock
owners
for locks. If you use jstack, use -l parameter as well [1]. (eg:
Hi krishantha,
noted and will change it in next update.
thanks
On Wed, Dec 24, 2014 at 11:21 AM, Buddhi Senarathna budd...@wso2.com
wrote:
Hi hasitha,
thanks a lot, but i'm using JMX api for this. j
On Tue, Dec 23, 2014 at 6:27 PM, Hasitha Aravinda hasi...@wso2.com
wrote:
Hi Buddi,
Are
13 matches
Mail list logo
