GlassFish 2.1

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X OpenSource RSS GlassFish 2.1
# 1  
Old 04-04-2009
CPU & Memory GlassFish 2.1

ImageAbout GlassFish
A production-ready, Java EE 5, open source application server. GlassFish V2 includes support for Enterprise JavaBeans (EJB) 3.0, JavaServer Faces (JSF) 1.2, JavaServer Pages (JSP) 2.1, Java Servlet 2.5, Java API for XML Web Services (JAX-WS) 2.1, Java Architecture for XML Binding (JAXB) 2.1 technologies, etc.

More from Apple...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

difference between oracle glassfish and glassfish opensource

questions. What's basically the difference between if I use the opensource and oracle glassfish (the one that requires license for production use)? Is there an evaluation period for the latter? Pls advise (0 Replies)
Discussion started by: lhareigh890
0 Replies

2. Solaris

Invalid Argument and glassfish

I tried to install glassfish on Solaris 10 and it worked fine on other instances. I got the below message bash-3.00# ./sjsas-9_1_01-solaris-sparc.bin -console bash: ./sjsas-9_1_01-solaris-sparc.bin: Invalid argument I logged on as root and the file has execute permission. So strange. Do... (1 Reply)
Discussion started by: Andrew2008
1 Replies
Login or Register to Ask a Question
jsadebugd(1)						      General Commands Manual						      jsadebugd(1)

NAME
jsadebugd - serviceability agent debug daemon SYNOPSIS
jsadebugd [pid] [server-id] jsadebugd executable core [server-id] DESCRIPTION
jsadebugd attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to the server using Java Remote Method Invocation (RMI). Before starting jsadebugd, rmiregistry must be started with: rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar where $JAVA_HOME is the J2SE SDK installation directory. If rmiregistry was not started, jsadebugd will start an rmiregistry in a standard (1099) port internally. Debug server may be stopped by sending SIGINT (pressing Ctrl-C) to it. NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK. jinfo is not currently available on Windows platforms or on the Linux Itanium platform. PARAMETERS
pid process id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java processes running on a machine, jps may be used. At most one instance of the debug server may be attached to a single process. executable Java executable from which the core dump was produced. core core file to which the debug server should attach. server-id optional unique id, needed if multiple debug servers are started on the same machine. This ID must be used by remote clients to identify the particular debug server to attach. Within a single machine, this ID must be unique. SEE ALSO
jinfo(1) jmap(1) jps(1) jstack(1) rmiregistry(1) 13 June 2004 jsadebugd(1)