-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Windows 10, Jenkins 2.190.2 (LTS)
Since around plugin version 1.10.5, get the following when using Perforce as Source repository:
P4: builds: 35908 P4: Connection retry: 1 Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
[JENKINS-60041] P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Ken Morse
added a comment - Sure, p4karl – log of brand new Freestyle job below and screenshot attached.
Started by user Ken Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on buildvpc10 in workspace E:\WinPC\Main\p4test (p4):cmd:... p4 login -s p4 login -s User p4dti-replicator0 ticket expires in 8 hours 40 minutes. (p4):stop:3 (p4):cmd:... p4 client -o BuildMachine-Perforce-Test p4 client -o BuildMachine-Perforce-Test (p4):stop:4 (p4):cmd:... p4 counter change p4 counter change (p4):stop:5 (p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/... Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2. ' (p4):stop:6 (p4):cmd:... p4 counter change p4 counter change (p4):stop:7 (p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054 p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054 Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2. ' (p4):stop:8 P4: builds: 34054 P4: Connection retry: 1 Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Finished: FAILURE
Ken Morse
added a comment - Sure, p4karl – log of brand new Freestyle job below and screenshot attached.
Started by user Ken
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on buildvpc10 in workspace E:\WinPC\Main\p4test
(p4):cmd:... p4 login -s
p4 login -s
User p4dti-replicator0 ticket expires in 8 hours 40 minutes.
(p4):stop:3
(p4):cmd:... p4 client -o BuildMachine-Perforce-Test
p4 client -o BuildMachine-Perforce-Test
(p4):stop:4
(p4):cmd:... p4 counter change
p4 counter change
(p4):stop:5
(p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...
p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...
Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2.
'
(p4):stop:6
(p4):cmd:... p4 counter change
p4 counter change
(p4):stop:7
(p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054
p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054
Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2.
'
(p4):stop:8
P4: builds: 34054
P4: Connection retry: 1
Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Finished: FAILURE
Paul Allen
added a comment - The error suggests that Identifier.properties is not in your class path; I can verity that we ship the properties file in the p4.hpi file.
unzip p4.hpi cd WEB-INF/lib/ unzip p4.jar ls org/jenkinsci/plugins/p4/Identifier.properties
From the log is seems that the issue occurs on a Windows slave 'buildvpc10' perhaps the slave.jar is old? or a localisation setting has changed the class path?
Please can you verify this by running the job on the master or a different slave.
Perhaps redeploying the Jenkins slave may solve the issue?
Paul Allen
added a comment - The error suggests that Identifier.properties is not in your class path; I can verity that we ship the properties file in the p4.hpi file.
unzip p4.hpi
cd WEB-INF/lib/
unzip p4.jar
ls org/jenkinsci/plugins/p4/Identifier.properties
From the log is seems that the issue occurs on a Windows slave 'buildvpc10' perhaps the slave.jar is old? or a localisation setting has changed the class path?
Please can you verify this by running the job on the master or a different slave.
Perhaps redeploying the Jenkins slave may solve the issue? 
Karl Wirth
added a comment - In addition to Paul's comments above note that I have installed 2.190.2 and P4Plugin 1.10.6 and I cannot reproduce the errors above on my Windows 10 build slave that runs Oracle Java version "1.8.0_77". The slave is started manually with 'java -jar agent.jar -jnlpUrl http://jenkins21902:8080/computer/Windows10_Manual/slave-agent.jnlp -workDir "" '.
Karl Wirth
added a comment - In addition to Paul's comments above note that I have installed 2.190.2 and P4Plugin 1.10.6 and I cannot reproduce the errors above on my Windows 10 build slave that runs Oracle Java version "1.8.0_77". The slave is started manually with 'java -jar agent.jar -jnlpUrl http://jenkins21902:8080/computer/Windows10_Manual/slave-agent.jnlp -workDir "" '. Ken Morse
added a comment - I got suspicious that maybe the Jenkins cache (%USERPROFILE%\.jenkins\cache) had become corrupt so I deleted the folder and restarted the agent. That completely corrected the problem reported. I can't say why this happened in the first place or why the P4 plugin was singled out, but all seems well now. Thank you p4paul and p4karl.
Ken Morse
added a comment - I got suspicious that maybe the Jenkins cache (%USERPROFILE%\.jenkins\cache) had become corrupt so I deleted the folder and restarted the agent. That completely corrected the problem reported. I can't say why this happened in the first place or why the P4 plugin was singled out, but all seems well now. Thank you p4paul and p4karl . Paul Allen
added a comment - Issue resolved. Karl Wirth
added a comment - Hi klm - Great that it's solved and thanks for letting us know. 
Samuel
added a comment - Re-opening this issue since we are seeing it quite a lot. After some investgating it seems like it happens when a Jenkins instance loses connection to p4 server and tries to re-establish the connection. We have seen this issue more often for instances which have a somewhat high latency connection to the perforce server.
When starting/restarting the agent the connection works fine for a long time but when the log file indicates a lost connection and a SEVERE level error message indicates connection retry it fails to load the locale bundle. Not sure if the error message is actually hiding some other error.
SEVERE: P4: Connection retry: 1
mars 16, 2023 3:01:33 FM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Jenkins Version: Jenkins 2.319.3
jenkinsci p4-plugin Version: 1.13.3
Samuel
added a comment - Re-opening this issue since we are seeing it quite a lot. After some investgating it seems like it happens when a Jenkins instance loses connection to p4 server and tries to re-establish the connection. We have seen this issue more often for instances which have a somewhat high latency connection to the perforce server.
When starting/restarting the agent the connection works fine for a long time but when the log file indicates a lost connection and a SEVERE level error message indicates connection retry it fails to load the locale bundle. Not sure if the error message is actually hiding some other error.
SEVERE: P4: Connection retry: 1
mars 16, 2023 3:01:33 FM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Jenkins Version: Jenkins 2.319.3
jenkinsci p4-plugin Version: 1.13.3 
Chaitanya
added a comment - Seeing this issue as well. Attaching relevant agent logs
Mar 21, 2023 2:35:06 PM org.jenkinsci.plugins.p4.client.SessionHelper connectionRetry SEVERE: P4: Connection retry: 1 java.util.logging.ErrorManager: 2 java.io.IOException: An unexpected network error occurred at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354) at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81) at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142) at java.logging/java.util.logging.FileHandler$MeteredStream.flush(FileHandler.java:201) at java.base/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:318) at java.base/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:153) at java.base/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:251) at java.logging/java.util.logging.StreamHandler.flush(StreamHandler.java:247) at java.logging/java.util.logging.FileHandler.publish(FileHandler.java:769) at java.logging/java.util.logging.Logger.log(Logger.java:979) at java.logging/java.util.logging.Logger.doLog(Logger.java:1006) at java.logging/java.util.logging.Logger.log(Logger.java:1029) at java.logging/java.util.logging.Logger.severe(Logger.java:1776) at org.jenkinsci.plugins.p4.client.SessionHelper.connectionRetry(SessionHelper.java:246) at org.jenkinsci.plugins.p4.client.SessionHelper.<init>(SessionHelper.java:54) at org.jenkinsci.plugins.p4.client.ConnectionHelper.<init>(ConnectionHelper.java:72) at org.jenkinsci.plugins.p4.client.ClientHelper.<init>(ClientHelper.java:103) at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:171) at org.jenkinsci.plugins.p4.tasks.WhereTask.invoke(WhereTask.java:35) at org.jenkinsci.plugins.p4.tasks.WhereTask.invoke(WhereTask.java:18) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3329) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:376) at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122) at java.base/java.lang.Thread.run(Thread.java:829) Mar 21, 2023 2:35:09 PM org.jenkinsci.plugins.p4.client.SessionHelper connectionRetry SEVERE: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_GB Mar 21, 2023 2:35:09 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_GB
Jenkins version 2.319.1
p4 plugin version 1.12.2
Chaitanya
added a comment - Seeing this issue as well. Attaching relevant agent logs
Mar 21, 2023 2:35:06 PM org.jenkinsci.plugins.p4.client.SessionHelper connectionRetry
SEVERE: P4: Connection retry: 1
java.util.logging.ErrorManager: 2
java.io.IOException: An unexpected network error occurred
at java.base/java.io.FileOutputStream.writeBytes(Native Method)
at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354)
at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at java.logging/java.util.logging.FileHandler$MeteredStream.flush(FileHandler.java:201)
at java.base/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:318)
at java.base/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:153)
at java.base/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:251)
at java.logging/java.util.logging.StreamHandler.flush(StreamHandler.java:247)
at java.logging/java.util.logging.FileHandler.publish(FileHandler.java:769)
at java.logging/java.util.logging.Logger.log(Logger.java:979)
at java.logging/java.util.logging.Logger.doLog(Logger.java:1006)
at java.logging/java.util.logging.Logger.log(Logger.java:1029)
at java.logging/java.util.logging.Logger.severe(Logger.java:1776)
at org.jenkinsci.plugins.p4.client.SessionHelper.connectionRetry(SessionHelper.java:246)
at org.jenkinsci.plugins.p4.client.SessionHelper.<init>(SessionHelper.java:54)
at org.jenkinsci.plugins.p4.client.ConnectionHelper.<init>(ConnectionHelper.java:72)
at org.jenkinsci.plugins.p4.client.ClientHelper.<init>(ClientHelper.java:103)
at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:171)
at org.jenkinsci.plugins.p4.tasks.WhereTask.invoke(WhereTask.java:35)
at org.jenkinsci.plugins.p4.tasks.WhereTask.invoke(WhereTask.java:18)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3329)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122)
at java.base/java.lang. Thread .run( Thread .java:829)
Mar 21, 2023 2:35:09 PM org.jenkinsci.plugins.p4.client.SessionHelper connectionRetry
SEVERE: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_GB
Mar 21, 2023 2:35:09 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask
SEVERE: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_GB
Jenkins version 2.319.1
p4 plugin version 1.12.2
Karl Wirth
added a comment - Hi avalanche_sale, img_chaitanya - Thanks for letting us know. Once the error is seen is that node broken until it's restarted or is this a transient error? Are the nodes Linux or Windows?
Karl Wirth
added a comment - Hi avalanche_sale , img_chaitanya - Thanks for letting us know. Once the error is seen is that node broken until it's restarted or is this a transient error? Are the nodes Linux or Windows? Samuel
added a comment - Hey Karl. Thanks for answering to this. Yes once this have happened once on a build agent any build initiated on that agent will fail with the same error until restarted. We are mainly using Windows nodes so I believe we have only seen it on Windows.
Samuel
added a comment - Hey Karl. Thanks for answering to this. Yes once this have happened once on a build agent any build initiated on that agent will fail with the same error until restarted. We are mainly using Windows nodes so I believe we have only seen it on Windows. Chaitanya
added a comment - Hi Karl, we observe similar behaviour as avalanche_sale describes. We're using Windows, MacOS and Linux agents, and we see this issue only on Windows.
Chaitanya
added a comment - Hi Karl, we observe similar behaviour as avalanche_sale describes. We're using Windows, MacOS and Linux agents, and we see this issue only on Windows. 
Hi klm - Can you please try creating a new freestyle job that just does an SCM sync from Perforce and see if the same error occurs. If it does please send me the full console log and a screen shot showing the SCM configuration.