Good Afternoon Intelligent Administrators/Debuggers!
I am installing JAMES on an internal server (192.168.2.33)
Specs of xxx.xxx.xxx.33 = SunOS v210b 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V210
After placing and "gunziping" the respective file, I am trying to run it by:
... (1 Reply)
Hi, I have the following situation and proposed solution:
SITUATION
I have a notebook computer. The manufacturer ships the hardware with a Windows OS (either XP Pro, Vista or Windows 7). They provide support only for a Windows OS.
Also, I am not sure how fuss-free it is to use any Linux... (0 Replies)
Good day!
Im interested with unix application, however i don't have any idea on how to configure network on unix applicaton(server) to have a connection with windows operating system (worksatation).
Please give me some facts how network works between unix and windows. (4 Replies)
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)
