• Home
• org.graalvm.visualvm.modules
• org-graalvm-visualvm-lib-jfluid
• 2.1.1
• source code
• Bundle.properties

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

org.graalvm.visualvm.lib.jfluid.Bundle.properties Maven / Gradle / Ivy

# Copyright (c) 1997, 2020, Oracle and/or its affiliates. All rights reserved.
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
#
# This code is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License version 2 only, as
# published by the Free Software Foundation.  Oracle designates this
# particular file as subject to the "Classpath" exception as provided
# by Oracle in the LICENSE file that accompanied this code.
#
# This code is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
# version 2 for more details (a copy is included in the LICENSE file that
# accompanied this code).
#
# You should have received a copy of the GNU General Public License version
# 2 along with this work; if not, write to the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
#
# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
# or visit www.oracle.com if you need additional information or have any
# questions.

OpenIDE-Module-Display-Category=Profiling
OpenIDE-Module-Name=Java Profiler (JFluid)
ProfilerClient_CannotOpenServerTempFileMsg=Cannot open temporary communication file created at the server side.\nName\: {0}
ProfilerClient_PerformingInstrumentationString=Performing instrumentation, please wait...
ProfilerClient_InvalidCodeRegionMsg=Invalid location was specified for code region instrumentation.\nInstrumentation cannot be performed.
ProfilerClient_ClassNotFoundMsg=Could not find class {0} on the class path.\nInstrumentation cannot be performed.
ProfilerClient_OutOfMemoryMsg=Too much data collected - the profiler ran out of memory.\nCollected profiling data has been deleted and profiling resumed.\nTo avoid this error please increase the -Xmx value\nin the etc/visualvm.conf file in VisualVM directory\nor lower the amount of details in profiling settings.
ProfilerClient_IncorrectAgentVersionMsg=Warning\: The profiler agent you are connecting to is a different version than this profiler.\nYou may encounter errors and unexpected behavior.
ProfilerClient_ErrorGettingCalibrationDataMsg=Error when retrieving saved calibration data for target JVM\:\n{0}
ProfilerClient_MustCalibrateFirstMsg=Since you did not run the Profiler on this machine or target JVM before,\ndeleted the saved calibration data, or this data is corrupt, profiling will STOP now.\n\nYou have to run the calibration command for your target JVM\nbefore running the Profiler with it again.\nThe obtained calibration data will be saved and re-used\non subsequent runs, so you will not see this message anymore.\n\nTo perform the calibration, use\n\"Tools | Options | Profiling | Manage calibration data\".\n\n
# HTML-formatted
ProfilerClient_MustCalibrateFirstShortMsg=Calibration data missing.

Profiling cannot be started on this JDK. Please perform
profiler calibration first and start profiling again.
# HTML-formatted
ProfilerClient_InstrumentationLimitReachedMsg=The limit of 64K instrumented methods has been reached.

The profiler cannot instrument more methods, some of your code
will not be profiled.

To avoid this problem, limit the number of profiled classes by
changing the profiling roots and/or instrumentation filter.
ProfilerClient_CorruptedTargetCalibrationDataMsg=Problem with saved calibration data on target machine\:\n{0}
ProfilerClient_ConnectVmMsg=Connecting to the target VM...
ProfilerClient_TargetJvmErrorMsg=Target JVM terminated unexpectedly or does not respond.\nWhen tried to send a message to it, got an IOException\:\n{0}
ProfilerClient_UnsupportedJvmMsg=Since the application you are trying to profile runs on {0} VM not supported by the Profiler, profiling will STOP now.\n\nPlease use 1.5.0 VM (Update 4 and higher) or 1.6.0 VM starting from build 26.

TargetAppRunner_ClasspathSettingsIgnoredMsg=The value of '-classpath' specified through 'Profile/Edit Settings' menu will be ignored.\nYou should specify the class path through 'File/Set class path' menu.
TargetAppRunner_ErrorStartingJvmMsg=When starting target JVM, with command: {0}, caught an exception\: {1}
TargetAppRunner_CalibrationSummaryShortMsg=The calibration was successful.\nClick Show Details to see calibration results.\n\nWarning\: If your computer uses dynamic CPU frequency switching,\nplease disable it and rerun calibration as changing the CPU frequency\nduring profiling would produce inaccurate results.
TargetAppRunner_CalibrationSummaryDetailsMsg=Some of the obtained calibration data is as follows\:\n\n
TargetAppRunner_FailedEstablishConnMsg=Failed to establish socket connection with the target JVM.
TargetAppRunner_UnexpectedProblemStartingAppMsg=Unexpected problem when trying to start target application\:\n
TargetAppRunner_JvmTerminatedNotRespondString=Target VM terminated or does not respond
TargetAppRunner_InternalProblemString=Internal problem
TargetAppRunner_FailedStartAppCauseMsg=Failed to start the target application. Cause\:\n{0}
TargetAppRunner_CalibrationResultsMsg=Approximate time in one methodEntry()/methodExit() call pair\:\nWhen getting absolute timestamp only\: {0} microseconds\nWhen getting thread CPU timestamp only\: {1} microseconds\nWhen getting both timestamps\: {2} microseconds\n\nApproximate time in one methodEntry()/methodExit() call pair\nin sampled instrumentation mode\: {3} microseconds\n
TargetAppRunner_CalibrationErrorMsg=Data transfer error during instrumentation calibration
TargetAppRunner_InternalStatisticsOnlyMsg=This is internal statistics that should be used only to estimate the efficiency\nof CPU profiling implementation. It is not for end-user results measurements.\n\n
TargetAppRunner_InstrMethodsCountMsg=Instrumented/hotswapped total of {0} methods
TargetAppRunner_ClassLoadFirstInvCountMsg=Issued {0} class load events, {1} first method invocation events
TargetAppRunner_NonEmptyImgCountMsg=Issued {0} non-empty InstrumentMethodGroup responses
TargetAppRunner_EmptyImgCountMsg=Issued {0} empty InstrumentMethodGroup responses
TargetAppRunner_SingleImgCountMsg=Issued {0} single method InstrumentMethodGroup responses
TargetAppRunner_AvgMethodTimeMsg=Average time per method group hotswapping/instrumentation operation\: {0} ms.
TargetAppRunner_MinMethodTimeMsg=Minimum time per method group hotswapping/instrumentation operation\: {0} ms.
TargetAppRunner_MaxMethodTimeMsg=Maximum time per method group hotswapping/instrumentation operation\: {0} ms.
TargetAppRunner_TotalRunTimeMsg=Total run time\: {0} ms.
TargetAppRunner_InjInstrTimeMsg=Time spent in injected instrumentation code for displayed thread\: {0} ms ({1} %)
TargetAppRunner_TotalInstrHotSwapTimeMsg=Total time spent in instrumentation/hotswapping in server\: {0} ms ({1} %)
TargetAppRunner_ByteCodeCommTimeMsg=Time spent in bytecode analysis/rewriting and wire communication in client\: {0} ms ({1} %)
TargetAppRunner_ClientByteCodeTimeMsg=Time spent in bytecode analysis/rewriting in client\: {0} ms
TargetAppRunner_ClientDiskProcessTimeMsg=Time spent in disk I/O and results processing in client\: {0} ms ({1} %)
TargetAppRunner_ClientResultsProcessTimeMsg=Time spent in results processing in client\: {0} ms.
TargetAppRunner_PerformingCalibrationMsg=Performing calibration, please wait...