I debugged a bit and got to the point where it was hanging in
the java.io.FileInputStream. I think it's going into native
code there because I can't step in and the state in the
jstacktrace was IN_NATIVE.
Here is line 219-221 of java.io.FileInputStream:
public int read(byte b[], int off, int len) throws
IOException {
return readBytes(b, off, len);
}
It could just be at the OS level. The JBoss Modules reaper
thread seems to be blocking too. It could be because of the
org.jboss.forge.shell.buffers.ConsoleInputSession readerThread
is hung though.
On 11/30/2012 05:43 PM, George
Gastaldi wrote:
Great ! Btw if you find any offending piece of code,
let us know ! Thanks for the feedback !
Em 30/11/2012, às 23:35, James Perkins <
jperkins@redhat.com>
escreveu:
It does seem to be reproducible. I've created the JIRA
here
https://issues.jboss.org/browse/FORGE-710.
If you need anything else just let me know. If you can't
reproduce it I can do whatever you need locally too.
On 11/30/2012 03:39 PM,
George Gastaldi wrote:
James,
Is it always reproductible ? What is the OS
you're using ? Can you please file a JIRA with this
data ? I'll have a look at it next week.
Thanks !
George Gastaldi
I'm seeing a hang on exit. I did a stack trace and
a kill -3 on it,
https://gist.github.com/4179325.
It looks like the console input thread is hanging
for some reason. Note this only happens when I
type exit and enter. Using CTRL+D works, but
CTRL+C does not either. It doesn't hang, but it
doesn't exit with CTRL+C.
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
James R. Perkins
JBoss by Red Hat