Getting: "No Response Received for upload." exception using LargeFileUploadTask
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 25/100
Piste de recherche
Commencez par la documentation de Microsoft Graph sur l’envoi de fichiers volumineux et la trace de pile signalée, en particulier UploadResponseHandler.java:71, UploadSliceRequestBuilder.java:69 et LargeFileUploadTask.java:210. Reproduisez l’échec avec le code Java 21 fourni et examinez le comportement de la réponse ou de la requête d’envoi. C’est terminé lorsque vous avez déterminé si le SDK ou la requête est responsable et documenté une résolution confirmée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- Java
- Étoiles
- 444
- Forks
- 154
- Merge moyen
- 18 h 28 min
- PR mergées (30 j)
- 4
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoftgraph/msgraph-sdk-java
-
status:waiting-for-triage type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
microsoftgraph/msgraph-sdk-java#2610 ·
-
status:waiting-for-triage type:bug
Difficulté 3/5 1-2 jours Accessibilité débutants 55/100
microsoftgraph/msgraph-sdk-java#2656 ·
-
status:waiting-for-triage type:bug
Difficulté 4/5 3-5 jours Accessibilité débutants 38/100
microsoftgraph/msgraph-sdk-java#2654 ·
-
status:waiting-for-triage
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
microsoftgraph/msgraph-sdk-java#2639 ·
-
Error in PATCH onlineMeeting Ouvertestatus:waiting-for-triage type:bug
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
microsoftgraph/msgraph-sdk-java#2589 · 1 commentaire ·
Toutes les issues de microsoftgraph/msgraph-sdk-java
Issues similaires
-
Bug Java Platform: Java
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
getsentry/sentry-java#6138 · 1 commentaire ·
-
bug needs triage p2
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
GoogleCloudPlatform/DataflowTemplates#4273 · 1 commentaire ·
-
[Studio][Bug] Bulk-deleting a full page of alert rules steps the page back while more rules remain Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
apache/rocketmq-dashboard#4654 · 1 commentaire ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100