Not able to publish code with jar size greater that 2MB

Help
,
1

Hi Team

I have developed project in which I am calling a jar which is of size 15 MB nearly.

While publishing it to orchestrator getting issue.

while debugging found issue with file size.

logs of studio::
Error: The request was aborted: The request was canceled. —> System.Net.WebException: The request was aborted: The request was canceled. —> System.IO.IOException: Cannot close stream until all bytes are written.
at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting)
— End of inner exception stack trace —
at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting)
at System.Net.ConnectStream.System.Net.ICloseEx.CloseEx(CloseExState closeState)
at System.Net.ConnectStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at System.IO.Stream.Dispose()
at NuGet.MultipartWebRequest.CreateMultipartRequest(WebRequest request)
at NuGet.PackageServer.<>c__DisplayClass4.b__2(Object sender, WebRequestEventArgs e)
at System.EventHandler1.Invoke(Object sender, TEventArgs e) at NuGet.HttpClient.RaiseSendingRequest(WebRequest webRequest) at NuGet.RequestHelper.GetResponse() at NuGet.HttpClient.GetResponse() at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode)
at NuGet.PackageServer.PushPackageToServer(String apiKey, Func`1 packageStreamFactory, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at NuGet.PackageServer.PushPackage(String apiKey, IPackage package, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at UiPath.Project.Deploy.ProjectPackageManager.Push(WorkflowProjectPackage pack, Int32 timeout)
at UiPath.Project.ProjectManager.Publish(Int32 timeoutMS)
at UiPath.Workflow.ViewModels.MainViewModel.PackAndPush()
— End of inner exception stack trace —

Request you to help.

Thanks and regards
Kishor Srivastava

1 Like
2

Please make this settings on your ORchestrator installation

3

@kishor9096
Getting Same Issue,Did you resolved this?

4

Hi Navulurin

You can try one workaround.
Place the Jar to some reference path and provide the reference path in script.
and you can have the versioning of Jar using svn or any.

Regards
Kishor Srivastava