Container Error 110
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://stackoverflow.com/questions/24087900/cics-web-service-requestor-get-container-returns-neither-data-nor-error about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack https://github.com/docker/docker/issues/12547 Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up CICS web service requestor GET CONTAINER returns neither data nor error up response code vote 1 down vote favorite I am developing a CICS web service requestor application to consume a distributed web service. I used the web services assistant DFHWS2LS to transform the wsdl to copybooks successfully. I have no problem issuing the PUT CONTAINER and INVOKE SERVICE api commands, but when I issue GET CONTAINER I am not receiving any containers or data. No response codes or error messages, but no cics get container data. Any ideas on how to debug this would be greatly appreciated. Thanks, web-services cics share|improve this question edited Jun 7 '14 at 15:22 Shog9♦ 108k28183217 asked Jun 6 '14 at 17:52 Namhcir 2652615 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote I have never seen RESP be DFHRESP(NORMAL) and RESP2 be zero and have nothing returned by the server. Verify the WSDL specifies that something is, in fact, returned by the web service. Check the RESP and RESP2 values returned by the INVOKE SERVICE API. You don't mention these explicitly, and I presume the former is DFHRESP(NORMAL) and the latter is 0, but you might have coded NOHANDLE so I thought I'd ask. Take a look in the TD queue mapped to CSSL (the default is the MSGUSR DD) for your CICS region. This is where CICS logs messages when it runs into an error while processing your SOAP request. Look for messages prefixed DFHPI. Try pinging the endpoint from a TSO session running on the same LPAR as your CICS region, it's possible you're being stopped by a firewall. In your comment you indicate the requestor is "seeing whitespace on the
Support Search GitHub This repository Watch 2,911 Star 35,572 Fork 10,455 docker/docker Code Issues 1,794 Pull requests 156 Projects 0 Wiki Pulse Graphs New issue Cannot start container: exit status 4 #12547 Open dnephin opened this Issue Apr 20, 2015 · 8 comments Projects None yet Labels area/networking kind/bug version/1.5 Milestone No milestone Assignees No one assigned 6 participants Docker member dnephin commented Apr 20, 2015 We have a build system which runs across many hosts, and runs 20+ concurrent builds per host. Each build will start/stop a few docker containers. We're consistently hitting this error trying to start containers, it happens on roughly 5% of the builds. We tried adding a retry to the "start container" API call (5 tries with exponential backoff up to 15s) , but that didn't resolve the issue. Earlier related issues: #8912, #6010 docker version Go version (client): go1.4.1 Git commit (client): 5f78bd5 OS/Arch (client): linux/amd64 Server version: 1.5.0 Server API version: 1.17 Go version (server): go1.4.1 Git commit (server): 5f78bd5 docker info (from one random host, they should all be pretty similar) Containers: 0 Images: 200 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 512 Execution Driver: native-0.2 Kernel Version: 3.13.0-43-generic Operating System: