microsoftgraph / microsoftgraph/msgraph-sdk-java

Getting: "No Response Received for upload." exception using LargeFileUploadTask

Abierto
#2,500 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

status:waiting-for-triage
Lenguaje dominante
Java
Estrellas
444
Forks
154
Merge medio
18 h 28 min
PR fusionados (30 d)
4

Descripción

Hello, we are experiencing this exception and we don't find much information about It so we are creating this issue because we are not sure if It is a bug or It is something else.

We are trying to upload Large Files (more than 3 MB) to a draft Outlook Message from our Java 21 Maven Project with Microsoft Graph Java SDK v6.54.0. The POM.xml dependency looks like this:

        <dependency>
            <groupId>com.microsoft.graph</groupId>
            <artifactId>microsoft-graph</artifactId>
            <version>6.54.0</version>
        </dependency>

We are following the Microsoft Docs to do this: https://learn.microsoft.com/en-us/graph/sdks/large-file-upload?tabs=java#upload-large-attachment-to-outlook-message

So when we do the task.upload() we are getting the following Stack Trace:

SEVERE: Exception during large attachment upload for 'document (1).pdf'. Error: No Response Received for upload.
[INFO] GCLOUD: com.microsoft.kiota.ApiException: No Response Received for upload.
[INFO] GCLOUD: 	at com.microsoft.graph.core.requests.upload.UploadResponseHandler.handleResponse(UploadResponseHandler.java:71)
[INFO] GCLOUD: 	at com.microsoft.graph.core.requests.upload.UploadSliceRequestBuilder.put(UploadSliceRequestBuilder.java:69)
[INFO] GCLOUD: 	at com.microsoft.graph.core.tasks.LargeFileUploadTask.uploadSlice(LargeFileUploadTask.java:210)
[INFO] GCLOUD: 	at com.microsoft.graph.core.tasks.LargeFileUploadTask.upload(LargeFileUploadTask.java:134)
[INFO] GCLOUD: 	at plenion.officeware.services.OutlookMailService.addAttachmentsToDraft(OutlookMailService.java:1472)

Our code looks like this:

                   CreateUploadSessionPostRequestBody req = new CreateUploadSessionPostRequestBody();
                    AttachmentItem item = new AttachmentItem();
                    item.setAttachmentType(AttachmentType.File);
                    item.setName(name);
                    item.setSize(size);
                    item.setIsInline(isInline);
                    if (contentType != null) item.setContentType(contentType);
                    req.setAttachmentItem(item);

                    UploadSession session = graphClient
                            .users()
                            .byUserId(userMail)
                            .messages()
                            .byMessageId(draftMessageId)
                            .attachments()
                            .createUploadSession()
                            .post(req);


                    InputStream in = graphClient
                            .drives()
                            .byDriveId(driveId)
                            .items()
                            .byDriveItemId(a.getId())
                            .content()
                            .get();

                    try (in) {
                        log.info("Starting upload for attachment: " + name);
                        log.info("Upload session URL: " + session.getUploadUrl());
                        log.info("Upload session expiration: " + session.getExpirationDateTime());

                        int maxChunkSize = 4 * 1024 * 1024; // 4 MiB

                        LargeFileUploadTask<FileAttachment> task = new LargeFileUploadTask<>(
                                graphClient.getRequestAdapter(),
                                session,
                                in,
                                size,
                                maxChunkSize,
                                FileAttachment::createFromDiscriminatorValue
                        );


                        IProgressCallback callback = (current, max) -> log.info(
                                String.format("Uploaded %d bytes of %d total bytes", current, max)
                        );

                        UploadResult<FileAttachment> uploadResult = task.upload(5, callback);

                        if (uploadResult.isUploadSuccessful()) {
                            log.info("Upload complete. Item ID: " + uploadResult.itemResponse.getId());
                        } else {
                            log.severe("Upload failed. No response received.");
                        }
                    } catch (Exception e) {
                        log.severe("Exception during large attachment upload for '" + name + "'. Error: " + e.getMessage());
                        e.printStackTrace();
                        throw new RuntimeException(e);
                    }

If this information is useful also we are using Google App Egine Standard to host our APIs but this error also occurs while localhost development too, so at first instance this is not related with Google.

What is wrong here? Is It normal to get that message? Are we missing something?

We can provide more information if needed, please just let us know and we will update the issue. Thank you in advance.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con la documentación de Microsoft Graph sobre la carga de archivos grandes y el stack trace informado, especialmente UploadResponseHandler.java:71, UploadSliceRequestBuilder.java:69 y LargeFileUploadTask.java:210. Reproduce el fallo con el código Java 21 proporcionado e inspecciona el comportamiento de la respuesta o la solicitud de carga. Se considera terminado cuando se haya identificado si el SDK o la solicitud es responsable y se haya documentado una resolución confirmada.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
api
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.