“[ISP.0090.0008E] [ISS.0086.9310] Could not restore pipeline from file ****” error occurs when attend to debug in Wm9.10 while I can make it on Wm9.7. May I know what is wrong with Wm9.10?
I know it’s silly, but can you try placing pub.flow:tracePipeline service as the first step in your service and check if the service invocation is happening in the first place?
- set Pipeline debug: Save
- call service
- set Pipeline debug: restore(Overide)
The below error still there:
com.wm.app.b2b.server.ServiceException: [ISS.0086.9310] Could not restore pipeline from file XXXXX.xml.
at pub.flow.restorePipelineFromFile(flow.java:277)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:406)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:650)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:303)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:377)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:549)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:363)
at com.wm.app.b2b.server.invoke.PipelineProcessor.restorePipeline(PipelineProcessor.java:127)
at wm.server.flowdebugger.startFlow(flowdebugger.java:886)
at wm.server.flowdebugger.start(flowdebugger.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:416)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:650)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:303)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:377)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:549)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:238)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:156)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:179)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:387)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:745)
Hi Aaron,
Can you check if the pipeline file is present under
IntegrationServer\instances\default\pipeline
If the pipeline are not getting saved, check the extended setting if savepipeline is disabled.
The pipeline are not getting saved. I shared my all extended setting. Could you advise which one is the related one that disable the savepipeline?
watt.debug.logfile=/logs/sag/wm910/is/server.log
watt.net.jsse.client.enabledCipherSuiteList=TLS_RSA_WITH_AES_128_CBC_SHA256,default
watt.net.jsse.client.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2
watt.net.jsse.server.enabledCipherSuiteList=TLS_RSA_WITH_AES_128_CBC_SHA256,default
watt.net.jsse.server.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2
watt.net.ssl.client.strongcipheronly=false
watt.net.ssl.client.useJSSE=true
watt.net.ssl.server.handshake.maxVersion=TLSv1.2
watt.net.ssl.server.handshake.minVersion=tls
watt.net.ssl.server.strongcipheronly=true
watt.server.audit.logDir=/logs/sag/wm910/is/
watt.server.compile=/sag/wm910/jvm/jvm/bin/javac -classpath {0} -d {1} {2}
watt.server.debugFIPS=true
watt.server.http.x-frame-options=
watt.server.soap.validateResponse=false
watt.server.SOAP.validateSOAPMessage=false
watt.server.stats.logfile=/logs/sag/wm910/is/stats.log
watt.server.url.alias.partialMatching=true
watt.ssl.iaik.debug=false
watt.WmMQAdapter.SSL.Support=true
watt.server.SOAP.MTOMStreaming.cachedFiles.location=temp/mtom/cachedfiles
watt.server.SOAP.MTOMStreaming.enable=true
watt.server.SOAP.MTOMStreaming.threshold=4000
watt.server.SOAP.MTOMThreshold=0
Hi,
Go to extended settings.
Click on “Show/hide extended settings”.
Search for string “pipelineProcessor”.
You should find a watt setting with that string. Select the check box to make it visible.
Save changes.
Check if the value for this setting is FALSE… (False means save pipeline is disabled). Make it TRUE
Under watt.server.pipeline.processor=true, the save pipeline still disable. In other words, the debug error still exists.
Is that already true or did you change it to true now? If you changed it now then it requires a server restart.
Hi Aaron,
can you please share the package if possible ? and properties screen shot
Are you getting this issue only on a particular service or its the same issue across all the services?
Can you try creating a sample service and test the same.
Hi Pokala,
It seems that it is a must to show watt.server.pipeline.processor to enable debug in Wm9.10. For now it works fine after a server restart. Thx so much.