learn unix and linux commands

Article: Looking Ahead to Java SE 7 and 8: A Discussion with Oracle’s Java Language Architect, Brian

 
Thread Tools Search this Thread
# 1  
Old 01-27-2011
Article: Looking Ahead to Java SE 7 and 8: A Discussion with Oracle’s Java Language Architect, Brian

We caught up with Oracle's Java Language Architect, Brian Goetz, to get his thoughts on concurrency, Java SE 7 and 8, developments in the Java Virtual Machine (JVM), and more.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Fedora

Fedora: Uninstall Java JDK 1.8 and install Oracle Java 1.7.15

Hi All, I have just downloaded fedora 27 iso and set it up in virtual box. I want to learn Hadoop so trying to install Apache hadoop. Before all those I have to install Oracle Java 1.7.15 (as mentioned in the Apache hadoop page). Can you please help me how to Uninstall currently installed... (6 Replies)
Discussion started by: TechGyaann
6 Replies
Login or Register to Ask a Question
jstack(1)						      General Commands Manual							 jstack(1)

NAME
jstack - stack trace SYNOPSIS
jstack [ option ] pid jstack [ option ] executable core jstack [ option ] [server-id@]remote-hostname-or-IP DESCRIPTION
jstack prints Java stack traces of Java threads for a given Java process or core file or a remote debug server. For each Java frame, the full class name, method name, 'bci' (byte code index) and line number, if available, are printed. With the -m option, jstack prints both Java and native frames of all threads along with the 'pc' (program counter). For each native frame, the closest native symbol to 'pc', if available, is printed. C++ mangled names are not demangled. To demangle C++ names, the output of this command may be piped to c++filt. NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK. jstack is not currently available on Windows platforms or on the Linux Itanium platform. PARAMETERS
Options are mutually exclusive. Option, if used, should follow immediately after the command name. pid process id for which the stacktrace is to be printed. The process must be a Java process. To get a list of Java processes running on a machine, jps may be used. executable Java executable from which the core dump was produced. core core file for which the stack trace is to be printed. remote-hostname-or-IP remote debug server's (see jsadebugd) hostname or IP address. server-id optional unique id, if multiple debug servers are running on the same remote host. OPTIONS
-m prints mixed mode (both Java and native C/C++ frames) stack trace. -h Prints a help message. -help Prints a help message. SEE ALSO
pstack(1) c++filt(1) jps(1) jsadebugd(1) KNOWN BUGS
Mixed mode stack trace, the -m option, does not work with the remote debug server. 13 June 2004 jstack(1)