We recently upgrade our java from
java-1.8.0-openjdk-devel-1.8.0.262.b10-0.el7_8.x86_64
to
java-1.8.0-openjdk-devel-1.8.0.282.b08-1.el7_9.x86_64
and Bamboo wont come up using https
we reverted the java version and bamboo came up successfully
Please advise
As per documentation, it should have worked without any errors.
But please check with Atlassian Team to know more on this by raising a support ticket.
https://confluence.atlassian.com/bamboo0610/supported-platforms-980468664.html
Thanks,
Pramodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
bellow is what I see in my log file
09-Feb-2021 08:43:50.244 INFO [http-nio-8083-exec-1] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
09-Feb-2021 08:43:50.244 INFO [http-nio-8083-exec-2] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
connector in the server.xml looks like this
<Connector port="8446"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxHttpHeaderSize="8192"
SSLEnabled="true"
keystoreFile="/opt/atlassian/application-data/XXXXXXXXXXXX" keystorePass="XXXXXXXXXX"
maxThreads="200" enableLookups="false"
disableUploadTimeout="true" acceptCount="100"
scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
URIEncoding="UTF-8"
compression="force"
compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css"
useBodyEncodingForURI="true" />
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We may have to change the protocol and maxHttpHeaderSize when it's in
"java-1.8.0-openjdk-devel-1.8.0.282.b08-1.el7_9.x86_64" version
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's better to get support from Atlassian Team on this configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Response from Atlassian Team
Miguel Alonso commented:
Hi Yusuf,
Thanks for contacting us!
It looks like you're running into an existing bug, which can be found here:
There are two workarounds available in the bug report. One is to downgrade the JDK version which is what you already did or if you prefer to stick with version 282 you'll have to carry some additional steps which I quote below:
Disable RSASSA-PSS:
Edit the $JAVA_HOME/jre/lib/security/java.security and add RSASSA-PSS to the jdk.tls.disabledAlgorithms or create another file containing:
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \EC keySize < 224, 3DES_EDE_CBC, anon, NULL, RSASSA-PSS
and add this to the $BAMBOO_INSTALL/bin/setenv.sh, in JVM_SUPPORT_RECOMMENDED_ARGS:
-Djava.security.properties=/path/to/file/created.above
This alone will fix the connection between agents and the server via the JMS broker.
If you are experiencing SSL error with HTTPS requests directly to Tomcat, in addition to disabling RSASSA-PSS above, you'll also need to disable TLSv1.3 by setting sslEnabledProtocols="TLSv1.2". Example:
<Connector port="8443" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" disableUploadTimeout="true" acceptCount="100" enableLookups="false" maxHttpHeaderSize="8192" useBodyEncodingForURI="true" URIEncoding="UTF-8" keystoreFile="/path/to/keystore.p12" keystorePass="changeit" scheme="https" secure="true" SSLEnabled="true" sslProtocol="TLS" sslEnabledProtocols="TLSv1.2" clientAuth="false" />
Please let me know if you have any further questions!
Best regards,
Miguel
Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.