Open oveits opened 8 years ago
OSV Prepare Button of Apache Camel Portal does not work as expected, if the OSV has been booted only minutes ago. E.g. we get s.th. like:
################################### # ################################### ERROR: org.apache.camel.component.file.GenericFileOperationFailedException: Cannot store file: ProvisioningScripts.tar.gz ERROR CAUSE: 4: java.io.IOException: inputstream is closed STACK: [direct:sendDeleteFolder, direct:PrepareOSV, direct:OSVMassProvisioning, direct:order, jetty:http://0.0.0.0:{{Provisioning.inputport}}/ProvisioningEngine?continuationTimeout=3600000] TRACE: [direct:sendDeleteFolder, direct:PrepareOSV, direct:OSVMassProvisioning, direct:order, jetty:http://0.0.0.0:{{Provisioning.inputport}}/ProvisioningEngine?continuationTimeout=3600000] HEADERS: {AC=, Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8, Accept-Encoding=gzip, deflate, Accept-Language=en-US,en;q=0.8,de;q=0.6, action=PrepareSystemSendDeleteFolder, actionOrig=PrepareSystem, assignedEmail=, authPassword=(removed), authUsername=srx, breadcrumbId=ID-provisioningenginecamel-44357-1464010703798-0-129664, CamelFileName=null, CamelHttpMethod=POST, CamelHttpPath=, CamelHttpQuery=null, CamelHttpServletRequest=(POST /ProvisioningEngine)@1338479129 org.eclipse.jetty.server.Request@4fc79219, CamelHttpServletResponse=HTTP/1.1 200 , CamelHttpUri=/ProvisioningEngine, CamelHttpUrl=http://192.168.113.104/ProvisioningEngine, CamelServletContextPath=/ProvisioningEngine, CC=1, Content-Length=0, Content-Type=text/html; charset=UTF-8, customerCC=1, customerLanguage=englishUS, customerName=, customerName2=, customerName3=, customerNameWebRegex1=^.{1,16}$, debugFile=src/data/?fileName=wireTapDeleteFolder_87808673_OSV_VR.txt, direct:OSVMassProvisioning:myStackOrig=direct:order__jetty:http://0.0.0.0:80/ProvisioningEngine, EndpointDefaultHomeDnXtension=10000, familyName=, FileName=ProvisioningScripts_systemType=OSV.tar.gz, FolderList=scripts, src/main/resources/scripts, FPAFOmit=true, FPCREATEOmit=true, GatewayIP=, givenName=, Host=192.168.113.104, imAddress=, IntNatPrefix=011, IntNatPrefixLen=3, LOC=, multiTenant=true, myStack=direct:sendDeleteFolder__direct:PrepareOSV__direct:OSVMassProvisioning__direct:order__jetty:http://0.0.0.0:80/ProvisioningEngine, myStackOrig=direct:OSVMassProvisioning__direct:order__jetty:http://0.0.0.0:80/ProvisioningEngine, NatPrefix=1, NatPrefixLen=1, orderID=87808673, Origin=http://192.168.113.104, OSVauthPassword=(removed), OSVauthPasswordRoot=(removed), OSVauthPasswordSysad=(removed), OSVauthUsername=srx, OSVDescription=CSL9DEV, OSVIP=192.168.160.7, OSVMgmtIP=192.168.160.7, OSVSshPort=22, OSVswitchID=2, PNAC=9, PNACLen=1, provisioningControl=true, ProvisioningEngineIP=192.168.113.104, ProvisioningScriptsFolderList=scripts, src/main/resources/scripts, provisionOSV=true, recipientList=sftp://192.168.160.7?username=srx&password=(removed), Referer=http://192.168.113.104/CloudWebPortal, SC=, showLocalGW=true, SiteName=, SiteName2=, systemType=OSV_VR, target=CSL9DEV, targetFolder=/unisphere/srx3000/srx/, targetIP=192.168.160.7, templateNameGenerator=velocity, traceLevel=debug, UCauthPassword=(removed), UCauthUsername=Administrator@system, UCDescription=CSL9DEV, UCIP=192.168.160.7, Upgrade-Insecure-Requests=1, User-Agent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36, velocityBaseUri=http://localhost:3000/text_documents.txt/, WebCDCIP=UNKNOWN, X=, XLen=1, XPRauthPassword=(removed), XPRauthUsername=Administrator, XPRDescription=CSL9DEV, XpressionsForwardAccess=*011, XPRIP=192.168.160.7} BODY: [B@6c470b17
Workaround: wait some minutes and try again. Prio is low, since PrepareOSV is not supported yet on the RoR ProvisioningEngine and we have a workaround.
OSV Prepare Button of Apache Camel Portal does not work as expected, if the OSV has been booted only minutes ago. E.g. we get s.th. like:
Workaround: wait some minutes and try again. Prio is low, since PrepareOSV is not supported yet on the RoR ProvisioningEngine and we have a workaround.