|
Glassfish example source code file (LogStrings.properties)
The Glassfish LogStrings.properties source code# # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. # # Copyright (c) 2010 Oracle and/or its affiliates. All rights reserved. # # The contents of this file are subject to the terms of either the GNU # General Public License Version 2 only ("GPL") or the Common Development # and Distribution License("CDDL") (collectively, the "License"). You # may not use this file except in compliance with the License. You can # obtain a copy of the License at # https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html # or packager/legal/LICENSE.txt. See the License for the specific # language governing permissions and limitations under the License. # # When distributing the software, include this License Header Notice in each # file and include the License file at packager/legal/LICENSE.txt. # # GPL Classpath Exception: # Oracle designates this particular file as subject to the "Classpath" # exception as provided by Oracle in the GPL Version 2 section of the License # file that accompanied this code. # # Modifications: # If applicable, add the following below the License Header, with the fields # enclosed by brackets [] replaced by your own identifying information: # "Portions Copyright [year] [name of copyright owner]" # # Contributor(s): # If you wish your version of this file to be governed by only the CDDL or # only the GPL Version 2, indicate your decision by adding "[Contributor] # elects to include this software in this distribution under the [CDDL or GPL # Version 2] license." If you don't indicate a single choice of license, a # recipient has the option to distribute your version of this file under # either the CDDL, the GPL Version 2 or to extend the choice of license to # its licensees as provided above. However, if you add GPL Version 2 code # and therefore, elected the GPL Version 2 license, then the option applies # only if the new code is made subject to such option by the copyright # holder. # jdbc.exc_jb_val=RAR5103 : Error setting java bean value : {0} RAR5103.diag.cause.1=The pool parameters in the domain.xml are improper. RAR5103.diag.cause.2=The application server process does not have enough permissions to access the DataSource class RAR5103.diag.check.1=Check that the pool parameters specified in the domain.xml are correct. For example check that parameters that expect numeric values are numerals RAR5103.diag.check.2=Check that the application server process has permissions to read the directory where the class resides jdbc.exc_nfe=RAR5104 : Not a valid type for this method : {0} RAR5104.diag.cause.1=The pool parameters in the domain.xml are improper. RAR5104.diag.check.1=Check that the pool parameters specified in the domain.xml are correct. For example check that parameters that expect numeric values are numerals jdbc.exc_cnfe_ds=RAR5099 : Wrong class name or classpath for Datasource Object RAR5099.diag.cause.1=Classpath is not properly set in the domain.xml RAR5099.diag.cause.2=The application server process does not have read permissions on the directory that holds the classes/jar RAR5099.diag.check.1=Check if the server classpath specified in the java-config element in the domain.xml has an entry for the jar containing this class RAR5099.diag.check.2=Check that the directory where the classes/jars reside have read permission for the application server process jdbc.exc_inst=RAR5101 : Exception while instantiating {0} RAR5101.diag.cause.1=The appserver process does not have read access to the directory where this class resides RAR5101.diag.cause.2=The application server process does not have security permissions to access this code RAR5101.diag.check.1=Check if the application server has read permissions on the directory where this class/jar containing this class resides RAR5101.diag.check.2=Check if your security manager policy is configured properly jdbc.exc_acc_inst=RAR5102 : Access error while instantiating {0} RAR5102.diag.cause.1=The application server process do not have permission to access the code base where the class resides RAR5102.diag.cause.2=This is an internal server/JVM error. Please contact Sun Microsystems with the complete error log RAR5102.diag.check.1=See if the application server process has permission to read the directory where the class/jar resides RAR5102.diag.check.2=Check if all relevant JVM patches are installed on your machine. Please contact Sun Microsystems with the complete error log statement.leak.detector_reclaim_statement_failure=RAR9000 : Failure while reclaiming statement for pool : {0}. Exception : {1} RAR9000.diag.cause.1=Database could be inaccessible. RAR9000.diag.check.1=Check if the database is accessible. #------------------------------------------------------------------------------------------------------ #RAR9000 till RAR9500 reserved for jdbc-ra LogStrings. #Please increment RAR IDs by one for any new additional messages added here. #Add any new properties above these comments. #------------------------------------------------------------------------------------------------------ #------------------------------------------------------------------------------------------------------ #RAR8010 till RAR8500 reserved for connectors-runtime LogStrings. #RAR8501 till RAR8700 reserved for connectors-inbound-runtime LogStrings. #RAR8701 till RAR8850 reserved for connectors-internal-api LogStrings. #RAR8850 till RAR8999 reserved for work-management LogStrings. #RAR9000 till RAR9500 reserved for jdbc-ra LogStrings. #------------------------------------------------------------------------------------------------------ Other Glassfish examples (source code examples)Here is a short list of links related to this Glassfish LogStrings.properties source code file: |
... this post is sponsored by my books ... | |
#1 New Release! |
FP Best Seller |
Copyright 1998-2021 Alvin Alexander, alvinalexander.com
All Rights Reserved.
A percentage of advertising revenue from
pages under the /java/jwarehouse
URI on this website is
paid back to open source projects.