Mohammad Nour El-Din kirjoitti:
Hi Alex...
This is actually the problem. The build does not hang, the mentioned
test case fails and the whole build process fails and exit execution,
this is why I don't know how to use that tool in such situation, I
didn't ask about process IDs, which I know about BTW.
You started the topic saying that the build hangs, not that it fails.
For me, it just hangs randomly, which is why Dain suggested the use of
jstack. I'm fairly new to Maven so I don't know how to get more verbose
output from the unit tests, but a failing test case should be easier to
figure out than one that just hangs. See if you can run the that
specific test case directly from your IDE. It should make it easier to
find out what's wrong.
On Fri, Nov 28, 2008 at 12:50 AM, Alex Grönholm
<[EMAIL PROTECTED]> wrote:
Mohammad Nour El-Din kirjoitti:
Dain...
I am still not able to use the tools cause the output of the build
is running over the console and I don't know when I should issue the
signal to print the thread dump. Please help.
Run the stack trace when the build process hangs in the test you told us
about.
The purpose of the stack trace is to give us an idea what's happening inside
the JVM when the test appears stuck.
On Fri, Nov 28, 2008 at 12:29 AM, Alex Grönholm
<[EMAIL PROTECTED]> wrote:
Jacek Laskowski kirjoitti:
On Thu, Nov 27, 2008 at 9:48 PM, Alex Grönholm
<[EMAIL PROTECTED]> wrote:
No, that's why you have to explicitly give the process ID of the
running
test as a parameter to jstack.
But this is not the right place to ask generic questions about how to
use
the command line and how operating systems generally work. You have to
learn
that elsewhere.
Hi Alex,
I value your patience responding to Mohammed's questions, but was
worried with your last answer, esp. "You have to learn that
elsewhere." Why do you think openejb mailing list is less appropriate
for such questions than other places? I think it's as good as
"elsewhere" (or better as chances are nobody knows where "elsewhere"
is).
Jacek
Because the topics in question are, IMHO, too broad to be properly
addressed
here. This mailing list is for discussing OpenEJB development, and I for
one
don't want to pollute it with off topic chatter that is of little to no
value to anyone outside the parties involved.
Also, to be able to contribute code to a complex project such as this,
certain basic knowledge about computers and operating systems (such as
processes and threads) is required. While I'm not judging anyone for lack
thereof, I simply feel that educating people about these matters is
beyond
the scope of this specific mailing list. At the very least, these
questions
should be asked on the users' list and not here.
