Glassfish server open source edition

Replaced by an operand in the list-custom-resources subcommand and the list-jndi-entries subcommand:. Suppose that you have deployed applications that use Java DB databases in your previous server installation, and you upgrade your existing installation to GlassFish Server 4.

If you run the asadmin start-database command and successfully start Java DB, you could run into problems while trying to run applications that were deployed on your previous server installation. Make sure the database is not running when you do this. Use the asadmin start-database command with the --dbhome option pointing to the databases directory in the older version of Java DB.

For example:. The container creates an EntityManager if the application uses the PersistenceContext annotation to inject an EntityManager , as in the following example:. The container creates an EntityManagerFactory if the application uses the PersistenceUnit annotation to inject an EntityManagerFactory , as in the following example:.

When the application is loaded, GlassFish Server 4. The actual persistence. Under certain circumstances, however, you may have to modify the persistence. An application uses Java SE code if it uses the javax.

Persistence class to create the EntityManagerFactory , as in the following example:. If the application itself contains any TopLink Essentials-specific code and therefore contains casts to oracle. This tool is not provided with GlassFish Server 4.

Elements that are no longer supported are request-processing , keep-alive , connection-pool , http-protocol , http-file-cache , and http-listener. During the upgrade process, these discontinued elements are remapped to the new configuration automatically and then deleted. The dotted name hierarchy for the GlassFish Server 4. The network-config element and all its children are new except for ssl. Note that the configuration for Enterprise Server v3 also applies to all earlier Enterprise Server 2.

The create-ssl subcommand has a new --type parameter value, network-listener. The create-virtual-server SUBcommand has a new parameter, --networklisteners. The create-http-listener subcommand adds a network-listener element to the domain configuration. The syntax and options of this commands are unchanged.

If you use a configuration from a Sun GlassFish Enterprise Server v2 or v3 release, this remapping happens automatically and then discontinued elements are deleted. The new file-cache element has no new attributes. All of its attributes are remapped from the http-file-cache element. For details, see Table Specifies the name of the protocol associated with this network-listener. Although this attribute is required, a protocol is automatically created with the same name as the network-listener when you use asadmin create-http-listener to create a network-listener.

Optional Specifies the name of the thread-pool associated with this network-listener. Specifies the name of the transport associated with this network-listener. Although this attribute is required, the default transport is used when you use asadmin create-http-listener to create a network-listener. Specifies the class name of the protocol-chain-instance-handler implementation. Specifies the name of the protocol associated with this protocol-finder.

Specifies the class name of the selection-key-handler implementation. Optional Specifies the class name of the thread-pool implementation. Optional Specifies the maximum number of messages that can be queued until threads are available to process them. A value of -1 specifies no limit. For remapped thread-pool attributes, see Table , Table , and Table Optional Specifies the class name of the transport implementation. For example: glassfish.

Log Level represents the log level. The default is INFO. Message ID consists of a module code that indicates the origin of the message and the message number.

LoggerName represents a hierarchical logger namespace that identifies the source of the log module. For example: javax. Key Value Pairs represents pairs of key names and values. For example: timeMillis: Message represents the text of the log message.

For multiline messages, [[ marks the end of the first line, and ]] marks the end of the message. Multiline messages start on a new line after the message header and are indented. Key Value Pairs represents pairs of key names and values and can include a message ID. The Administration Console presents log records in a more readable display.

By default, when a log file grows to 2 MB, GlassFish Server Open Source Edition renames rotates the file to incorporate a timestamp and creates a new log file. You can configure the logging service to change the default settings for log file rotation, as explained in Setting Log File Rotation. The following list is an example of the logger namespaces in a server instance as they appear when using the list-log-levels subcommand.

For information about how to display logger namespaces and log levels, see To List Log Levels. For information about how to display a list of loggers and logger details, see To List Loggers. Each instance in an GlassFish Server Open Source Edition domain has a dedicated log file, and each instance and cluster has its own logging properties file. To configure logging for an instance or a cluster, GlassFish Server Open Source Edition allows you target specific log files or logging properties files when you do the following:.

The following subcommands optionally accept a target specification. A target can be a configuration name, server name, cluster name, or instance name, and is specified as either an operand or as a value passed using the --target option. If no target is specified when using any of these subcommands, the default target is the DAS.

Rotates the log file by renaming it and creating a new log file to store new messages. Sets the log level for one or more loggers listed in the logging properties file.

The DAS as well as each configuration, instance, and cluster has its own set of logging properties that are maintained in individual configuration files. A logging properties file is named logging. By default in an GlassFish Server Open Source Edition domain, logging properties files are created in the following locations:. For information about configuring logging properties, see Configuring the Logging Service.

This section explains how to change the name and location of the following logging service files:. To change the name and location of the log file, first use the list-log-attributes subcommand to obtain the current log attribute setting for the log file name and location.

Then use the set-log-attributes subcommand to specify the new name or location. The default target for these two subcommands is the DAS. However, you can optionally specify one of the following targets:.

Configuration name — to target all instances or clusters that share a specific configuration name. Ensure that the target server or cluster is running. Remote subcommands require a running server. Use the list-log-attributes subcommand in remote mode to obtain the current log attribute settings. The name and location of the log file is set with the com. Optionally you can target a configuration, server, instance, or cluster.

If you do not specify a target, the log attribute settings for the DAS are displayed. Use the set-log-attributes subcommand in remote mode to define a custom name or location of the log file.

If you do not specify a target, the log file for the DAS is targeted by default. If you target a cluster, the name of the cluster log file for each member instance can be changed the server log file name cannot. This example changes the name of the cluster log file for Cluster1 to cluster1. Cluster1 has two server instances: ClusterServer1 and ClusterServer2. You can view the full syntax and options of these subcommands by typing asadmin help list-log-levels and asadmin help set-log-attributes at the command line.

You can set the name and location of the logging properties file by setting the java. By setting this system property, you can have a single logging properties file that is used by all instances running on the same host.

Setting the java. Set the java. For example, you can use the following java command:. Alternatively, you can use the Administration Console to set this system property. The default setting is INFO. You can list current log levels of all loggers specified in the logging properties file. In some cases, loggers that have not been created by the respective containers will also appear in the list. You can set log levels that are global or logger-specific. When you set a global log level, the log level goes into effect for all loggers.

If you set the log level for a specific logger that is different from the global log level, the logger-specific setting takes precedence. In addition, when setting log levels, you can target a configuration, server, instance, or cluster. Because setting log levels is a dynamic operation, you do not need to restart GlassFish Server Open Source Edition for changes to take effect.

Setting either global or logger-specific log levels is done by using the set-log-levels subcommand. Listing log levels is done by using the list-log-levels subcommand. Listing the loggers provides a convenient means to view current loggers and log levels either prior to or after making log level changes.

Use the list-log-levels subcommand in remote mode to list the modules and their current log levels. The default target for this subcommand is the DAS.

List the existing module loggers and log levels by using the list-log-levels subcommand. This example shows a partial list of the loggers and log levels for the instance MyServer2.

You can view the full syntax and options of the subcommand by typing asadmin help list-log-levels at the command line. The global log level specifies the events that are logged across all loggers. Use the set-log-levels subcommand in remote mode to set the global log level. However, you can optionally specify one of the following targets using the --target option:. Set the global log level by using the set-log-levels subcommand, specifying the log level of the java.

ConsoleHandler logger. The ConsoleHandler has a separate log level setting that limits the messages that are displayed. For example:. By setting the log level of the ConsoleHandler , you set the global log level for all loggers. You can view the full syntax and options of the subcommand by typing asadmin help set-log-levels at the command line. A module log level specifies the events that are logged for a particular logger.

The global log level is overridden by a module-specific log level. By default, the module log level is set to FINE. Action: Take appropriate action based on the exception message. Cause: The service that implements the command could not be loaded. Cause: An unexpected exception occurred while running a command. Cause: A request for a lock timed out while processing an admin console request.

Cause: InterruptedException occurred while the service thread is running. Cause: An unexpected exception occurred while changing run levels. A shutdown is required. Cause: An unexpected exception occurred while starting the startup service. Cause: An unexpected exception occurred while starting the server. Cause: An unexpected exception occurred while enabling an application.

Cause: An unexpected exception occurred while disabling an application. Cause: An unexpected exception occurred during lifecycle processing. Cause: An unexpected condition during lifecycle processing. Cause: An unexpected condition occurred during lifecycle processing. Cause: An unexpected condition occurred while loading an application.

Cause: An unexpected exception occurred while deploying an application. Cause: The deployment command for an application failed as indicated in the message. Action: Check the application and redeploy. Cause: An unexpected exception occurred while loading an application. Cause: Unable to retrieve an entry from the archive. Cause: An unexpected exception occurred while processing an archive.

Cause: An unexpected exception occurred while closing an archive. Cause: An unexpected exception occurred while loading a lifecycle module. Cause: An unexpected exception occurred while starting the grizzly service.

Cause: An unexpected exception occurred while closing a port. Cause: The container could not be started. Action: Ensure the libraries for the container are available. Cause: An exception occurred while attempting to start the container. Cause: An exception occurred while mapping a request to the container. Cause: An exception occurred while adding the container configuration to the domain.

Cause: An exception occurred while enabling or disabling the autodeployment of applications. Cause: An exception occurred while sending an event. Cause: An exception occurred while stopping the server. Cause: An exception occured when cleaning the managed jobs Action: Check the system logs and contact Oracle support. Cause: A software error is causing an incorrect argument sequence.

Action: No action necessary. Cause: While running the configure-managed-jobs command, a write transaction to the ManagedJobConfig bean failed. Cause: While running the configure-managed-jobs command, access to the ManagedJobConfig bean failed. Cause: An exception occured when shutting down the server after an upgrade. Cause: No port value is available in the NetworkListener config bean Action: Check the system logs and contact Oracle support.

Cause: There is an invalid port value in the domain. Cause: There is an invalid address value in the domain. Cause: An unexpected exception occured. Cause: An exception has occurred while reading the logging configuration file. Cause: There was an exception thrown while applying the logging configuration changes.

Cause: There was an exception thrown while executing log query. Cause: There was an exception thrown while initializing the syslog handler. Cause: There was an exception thrown while sending a log message to the syslog. Cause: An exception was caught when the operation was attempted Action: See the exception to determine how to fix the error. Cause: An exception was caught when the application was autodeployed. Action: See the exception to determine how to fix the error. Cause: An exception was caught when the entry was expanded Action: See the exception to determine how to fix the error.

Please provide a valid specification version for this optional package :: Cause: As described in the message. Cause: The type of archive being created is not supported. Action: Determine the type of archive requested to see whether another type can be used. Cause: The application might specify that modules are to be processed in the order they appear in the application and an app client module appears before a module that creates an artifact to be included in app clients.

Action: Make sure, if the application specifies initialize-in-order as true, that the app clients appear after other modules which generated artifacts that should be accessible to app clients. Cause: The server is attempting to register an artifact to be included in the generated client JAR but the artifact does not exist or cannot be read Action: This is an internal server error. Please file a bug report.

Cause: The server has created more than one artifact with the same relative path to be included in the generated client JAR file Action: This is an internal server error. Cause: Unknown Java type for the param Action: Try giving a fully qualified name for the type. Operating System does not support DTrace. Currently you must have Solaris 10 or higher for DTrace support. Action: Run with Solaris 10 or higher. Cause: Classpath is not properly set in the domain.

Cause: Please check the exception to get more details. Action: Please check the exception to resolve the same. Cause: Copying server config files. Cause: The XML file s may not be well formed. Action: Make sure the XML file s are well formed. Action: Check if the user. Cause: Upgrade security config files from a previous version. Action: Please refer to the v3. Cause: Private Credentials of Subject not available. Action: Please check if the private credentials are available. Cause: PasswordCredential was required, but not supplied.

Action: Please check if the password is provided. Cause: Setting the system wide policy. Cause: There was an exception obtaining the default security context. Cause: There was an exception while authenticating the default caller principal. Cause: An exception occurred while processing username and password for security. Action: An exception occurred while processing username and password for security.

Cause: There was an unexpected exception while setting the security context. Cause: Changing the current SecurityContext. Cause: null Subject used in SecurityContext construction. Action: Make sure the Subject is not null. RemoteException Action: Check server. Cause: An invalid context handle is being passed.

Cause: Can not initiate the Work Manager class. Action: Check the Work Manager class type. Only one can be specified. Cause: Unable to set Security Context. Action: Check the server. Cause: The annotation is incorrect. AS-EJB sfsb checkpoint error. AS-EJB 1. AS-EJB sfsb passivation error. Override will be ignored. AS-EJB keepstate is true and will not create new auto timers during deployment. Please use --default-virtual-server to specify this value. Please use only --default-virtual-server to specify this value.

Cannot add duplicate http. Cannot add duplicate http-redirect. Cannot add duplicate protocol. Cannot add duplicate transport. Possible causes are 1 Monitoring is not turned on or at a lower level 2 The corresponding container web, ejb, etc.

The ThreadLocal has been correctly set to null and the key will be removed by GC. This is expected on non-Sun JVMs. Expected: java. Either add a MultipartConfig to the servlet, or a multipart-config element to web. ObjectName for Logger Cause: As described in the message. Trying to re-open it. The database could be down.

The archive will be ignored. No closing! ProxyHandler Cause: Invalid proxy handler Action: Check to see if the proxy handler is an instance of com. Run updatecenter client located in bin folder to install Metro Cause: As described in the message.

Creating or using the named protocol element instead. Creating a new BDA. AS-CDI javax. Restriction on use of UserTransaction will not be enforced. Is port-component-name in webservices. Potential cause may be webservice endpoints not supported in embedded ejb case. Please wait. Register adapter. Remove instances before removing node.

You may specify the name of an existing config element next time. No need to create default-config. We could be running in unit tests. Running DefaultConfigUpgrade to create default-config. They were stripped out for you. Action: Find the agent file. Enabling all the MBeans Cause: As described in the message.