Hi Vincent,

Aside it is "internal server error" of your server, I don't think i can say
more. Am not knowledgeable about AF. Are you sure server log does not
contain anything, would be strange for a server software to respond
"bonkers" to client but not log anything...

T

On Wed, Oct 9, 2024, 06:23 Vincent Sevel <v.se...@lombardodier.com.invalid>
wrote:

> Hello,
> We have an issue when upgrading to 3.9 with the deploy plugin.
> This is working fine with 3.8.
>
> When doing a mvn deploy, we get a 500 on the jar upload:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:3.1.3:deploy (default-deploy)
> on project x: Failed to deploy artifacts: Could not transfer artifact
> x:x:jar:x-20241008.102538-6 from/to artifactory-maven (https://artifactory):
> status code: 500, reason phrase: Internal Server Error (500) -> [Help 1]
>
> It always fails when uploading the jar.
> The pom is always fine.
> And in a multi module project, it can deploy fine a few modules before
> getting an error.
> It is as if it connects to the registry, starts pushing some bytes, then
> stops.
>
> On the other side we have artifactory 7.68.
> Funny thing is that although we have a 500, there are no error logs in
> artifactory we could spot.
>
> I tried with mvn deploy -DskipTests -Dmaven.resolver.transport=wagon  but
> I have the same behavior.
>
> I have traced the issue down to HttpRequestExecutor in
>
> protected HttpResponse doReceiveResponse(
>         final HttpRequest request,
>         final HttpClientConnection conn,
>         final HttpContext context) throws HttpException, IOException {
>     Args.notNull(request, "HTTP request");
>     Args.notNull(conn, "Client connection");
>     Args.notNull(context, "HTTP context");
>     HttpResponse response = null;
>     int statusCode = 0;
>
>     while (response == null || statusCode < HttpStatus.SC_OK) {
>
>         response = conn.receiveResponseHeader();
>
> and LoggingManagedHttpClientConnection
>
> @Override
> public HttpResponse receiveResponseHeader() throws HttpException,
> IOException {
>     ensureOpen();
>     final HttpResponse response = this.responseParser.parse();
>
> but this does not offer more information than it is a 500.
>
> I have activated the apache http loggers, and I see:
>
> [DEBUG] http-outgoing-0: set socket timeout to 0
> [DEBUG] http-outgoing-0: set socket timeout to 1800000
> [DEBUG] http-outgoing-0 >> PUT /x-20241008.152600-2-tests.jar HTTP/1.1
> [DEBUG] http-outgoing-0 >> Cache-Control: no-cache, no-store
> [DEBUG] http-outgoing-0 >> Pragma: no-cache
> [DEBUG] http-outgoing-0 >> Expect: 100-continue
> [DEBUG] http-outgoing-0 >> Content-Length: 40331
> [DEBUG] http-outgoing-0 >> Host: x
> [DEBUG] http-outgoing-0 >> Connection: Keep-Alive
> [DEBUG] http-outgoing-0 >> User-Agent: Apache-Maven/3.9.9 (Java 21.0.1;
> Windows 11 10.0)
> [DEBUG] http-outgoing-0 >> Accept-Encoding: gzip,deflate
> [DEBUG] http-outgoing-0 >> Authorization: Basic c2V2ZWw6ZXlKMlpYSWlPaU...
> [DEBUG] http-outgoing-0 >> "PUT x-4.4.3-20241008.152600-2-tests.jar
> HTTP/1.1[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Cache-Control: no-cache, no-store[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Pragma: no-cache[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Expect: 100-continue[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Content-Length: 40331[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Host: x[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
> [DEBUG] http-outgoing-0 >> "User-Agent: Apache-Maven/3.9.9 (Java 21.0.1;
> Windows 11 10.0)[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
> [DEBUG] http-outgoing-0 >> "Authorization: Basic
> c2V2ZWw6ZXlKMlpYSWlPaUl5SWl3aWRIbHdJam9pU2xkVUlpd2lZV3h...[\r][\n]"
> [DEBUG] http-outgoing-0 >> "[\r][\n]"
> [DEBUG] http-outgoing-0 << "HTTP/1.1 100 Continue[\r][\n]"
> [DEBUG] http-outgoing-0 << "[\r][\n]"
> [DEBUG] http-outgoing-0 << HTTP/1.1 100 Continue
> [DEBUG] http-outgoing-0 >>
> "PK[0x3][0x4][0x14][0x0][0x0][0x8][0x8][0x0]N[0x8b]HY[0xdc]
> [0x9f][0xc9][0xc7][0x0][0x0][0x0][0x1][0x0][0x0][0x14][0x0][0x0][0x0]META-INF/MANIFEST.MF[0x8d][0x90][0xc1][0xe][0x82]0[0x10]D[0xef]M[0xfa][0xf][0xfd][0x81]6[0xa2]\[0xe4][0x6][0xc6]D[\r]"[0x9][0xc4][0xfb][\n]"
> ...
> [0x0][0x0][0xa4][0x81][0xed]2[0x0][0x0]META-INF/maven/x/x/pom.propertiesPK[0x1][0x2][0x14][0x3][0x14][0x0][0x0][0x8][0x8][0x0]'[0x84]HY
> ...
> [DEBUG] http-outgoing-0 >> "[0x0][0x0])[0x93][0x0][0x0][0x0][0x0]"
> [DEBUG] http-outgoing-0 << "HTTP/1.1 500 Internal Server Error[\r][\n]"
> [DEBUG] http-outgoing-0 << "Date: Tue, 08 Oct 2024 15:26:28 GMT[\r][\n]"
> [DEBUG] http-outgoing-0 << "Content-Type:
> application/json;charset=ISO-8859-1[\r][\n]"
> [DEBUG] http-outgoing-0 << "Transfer-Encoding: chunked[\r][\n]"
> [DEBUG] http-outgoing-0 << "Connection: keep-alive[\r][\n]"
> [DEBUG] http-outgoing-0 << "X-JFrog-Version: Artifactory/7.68.7
> 76807900[\r][\n]"
> [DEBUG] http-outgoing-0 << "X-Artifactory-Id:
> 5e00eb405d1afc5216ea55ba033cd506814026c2[\r][\n]"
> [DEBUG] http-outgoing-0 << "X-Artifactory-Node-Id: x[\r][\n]"
> [DEBUG] http-outgoing-0 << "X-Content-Type-Options: nosniff[\r][\n]"
> [DEBUG] http-outgoing-0 << "[\r][\n]"
> [DEBUG] http-outgoing-0 << "46[\r][\n]"
> [DEBUG] http-outgoing-0 << "{[\r][\n]"
> [DEBUG] http-outgoing-0 << "  "errors" : [ {[\r][\n]"
> [DEBUG] http-outgoing-0 << "    "status" : 500,[\r][\n]"
> [DEBUG] http-outgoing-0 << "    "message" : ""[\r][\n]"
> [DEBUG] http-outgoing-0 << "  } ][\r][\n]"
> [DEBUG] http-outgoing-0 << "}[\r][\n]"
> [DEBUG] http-outgoing-0 << "0[\r][\n]"
> [DEBUG] http-outgoing-0 << "[\r][\n]"
> [DEBUG] http-outgoing-0 << HTTP/1.1 500 Internal Server Error
> [DEBUG] http-outgoing-0 << Date: Tue, 08 Oct 2024 15:26:28 GMT
> [DEBUG] http-outgoing-0 << Content-Type:
> application/json;charset=ISO-8859-1
> [DEBUG] http-outgoing-0 << Transfer-Encoding: chunked
> [DEBUG] http-outgoing-0 << Connection: keep-alive
> [DEBUG] http-outgoing-0 << X-JFrog-Version: Artifactory/7.68.7 76807900
> [DEBUG] http-outgoing-0 << X-Artifactory-Id:
> 5e00eb405d1afc5216ea55ba033cd506814026c2
> [DEBUG] http-outgoing-0 << X-Artifactory-Node-Id: x
> [DEBUG] http-outgoing-0 << X-Content-Type-Options: nosniff
> [DEBUG] http-outgoing-0: set socket timeout to 0
>
> Again this does not offer much help.
>
> We tried upgrading artifactory to 7.77.14 with the same behavior.
> We activated the logs on artifactory, and we do not see anything.
>
> Has anybody seen this behavior? Any suggestion?
>
>
> Thanks,
> Vincent
>
>
>
>
> [[ rethink everything. ]]<https://www.lombardodier.com>
>
> [[LinkedIn]]<https://www.linkedin.com/company/lombard-odier>  [[Twitter]]
> <https://twitter.com/lombardodier>   [[Facebook]] <
> https://facebook.com/lombardodier>   [[Instagram]] <
> https://www.instagram.com/lombardodier/>   [[YouTube]] <
> https://www.youtube.com/channel/UCqatbeqXskmWejbm0KPLV3w>
>
> *** IMPORTANT NOTICE REGARDING INSTRUCTIONS by EMAIL ***
> Please be aware that instructions received by e-mail should be
> considered delayed and not executed unless they have been
> specifically confirmed by your relationship manager/banker.
> Email traffic during turbulent times in the financial markets is
> high and cannot always be acted upon at all times.
> Lombard Odier cannot be held liable for such delay in execution
> or for the non-execution of an instruction given by email even
> if it was given in due time. Therefore, instructions requiring
> immediate action must be communicated by telephone by calling
> the bank's registered landline.
> Thank you for your understanding.
>
> *** IMPORTANT INFORMATION ABOUT DATA PROTECTION ***
> You might be receiving this because you have provided us with
> your contact details. If this is the case note that we may process
> your personal data for direct marketing purposes.
> If you wish to object to this processing, please notify the
> Group's Data Protection Officer<mailto:
> group-dataprotect...@lombardodier.com>.
> For more information: www.lombardodier.com/privacy-policy
>
> DISCLAIMER **********************************************
> This message is intended only for use by the person
> to whom it is addressed. It may contain information
> that is privileged and confidential. Its content does
> not constitute a formal commitment by any company
> of the Lombard Odier group. If you are not the intended
> recipient of this message, kindly notify the sender
> immediately and destroy this message. Thank You.
> *******************************************************(dch)*
>
>

Reply via email to