microsoftgraph / microsoftgraph/msgraph-sdk-java

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

Offen
#2,500 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

status:waiting-for-triage
Vorherrschende Sprache
Java
Sterne
444
Forks
154
Ø Merge
18 Std. 28 Min.
Gemergte PRs (30 T.)
4

Beschreibung

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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit der Dokumentation zum Hochladen großer Dateien von Microsoft Graph und dem gemeldeten Stack Trace, insbesondere mit UploadResponseHandler.java:71, UploadSliceRequestBuilder.java:69 und LargeFileUploadTask.java:210. Reproduziere den Fehler mit dem bereitgestellten Java-21-Code und untersuche das Upload-Response- oder Request-Verhalten. Erledigt ist die Aufgabe, wenn festgestellt wurde, ob das SDK oder der Request verantwortlich ist, und eine bestätigte Lösung dokumentiert wurde.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java
Bereich
api
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.