Error while deploying API using zOS Connect EE
While trying to deploy API using zOS connect EE , I am getting error 'An error was received for z/OS Connect EE connection "zOS_Server" (server ip): 500 Internal Server Error, BAQR7033E: Internal server error.API deployment problem'.
Can anyone tell me what could be the problem.
I got this error message because something is wrong with the z/OS Connect service location, which stay in USS folder, e.g. no space on device or no authority to write, the location is defined in server.xml. You can find some error description in ffdc folder.
<zosconnect_services updateTrigger="polled" pollingRate="5s" location="~/zosconnect/services" />
Hi , Thanks for your inputs. I am still facing problem in deploying API on the server using toolkit. Please find attached the request log f[link text][1]ile and the server.xml (renamed) for your reference. Although we are getting the messages of successful deployment of zOS Service project but facing issue in deploying API. Below is the specific error log: [3/12/18 12:05:05:476 GMT] 00001009 com.ibm.wsspi.webcontainer.async W SRVE8025E: An error or timeout occured while doing async servlet processing. java.lang.NoClassDefFoundError: java.nio.file.FileSystems$DefaultFileSystemHolder (initialization failure) at java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:96) at java.nio.file.FileSystems.getDefault(FileSystems.java:187) at java.io.File.toPath(File.java:2245) at com.ibm.zosconnect.internal.ApiManagerImpl.installNewApiPackage(Unknown Source) at com.ibm.zosconnect.internal.ApiManagerImpl.installApiFromApiArchive(Unknown Source) at com.ibm.zosconnect.internal.web.ServiceProxyServlet$22.run(Unknown Source) at com.ibm.ws.webcontainer.async.ServiceWrapper.wrapAndRun(ServiceWrapper.java:202) at com.ibm.ws.webcontainer.async.ContextWrapper.run(ContextWrapper.java:28) at com.ibm.ws.webcontainer.async.WrapperRunnableImpl.run(WrapperRunnableImpl.java:89) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.lang.Thread.run(Thread.java:811) Caused by: java.lang.RuntimeException: default directory must be absolute at sun.nio.fs.UnixFileSystem.(UnixFileSystem.java:67) at sun.nio.fs.ZosFileSystem.(ZosFileSystem.java:26) at sun.nio.fs.ZosFileSystemProvider.newFileSystem(ZosFileSystemProvider.java:32) at sun.nio.fs.ZosFileSystemProvider.newFileSystem(ZosFileSystemProvider.java:19) at sun.nio.fs.UnixFileSystemProvider.(UnixFileSystemProvider.java:68) at sun.nio.fs.ZosFileSystemProvider.(ZosFileSystemProvider.java:22) at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1762) at sun.nio.fs.DefaultFileSystemProvider.createProvider(DefaultFileSystemProvider.java:60) at sun.nio.fs.DefaultFileSystemProvider.create(DefaultFileSystemProvider.java:80) at java.nio.file.FileSystems$DefaultFileSystemHolder.getDefaultProvider(FileSystems.java:119) at java.nio.file.FileSystems$DefaultFileSystemHolder.access$000(FileSystems.java:100) at java.nio.file.FileSystems$DefaultFileSystemHolder$1.run(FileSystems.java:109) at java.nio.file.FileSystems$DefaultFileSystemHolder$1.run(FileSystems.java:107) at java.security.AccessController.doPrivileged(AccessController.java:638) at java.nio.file.FileSystems$DefaultFileSystemHolder.defaultFileSystem(FileSystems.java:107) at java.nio.file.FileSystems$DefaultFileSystemHolder.(FileSystems.java:101) at java.nio.file.FileSystems.getDefault(FileSystems.java:187) at java.io.File.toPath(File.java:2245)
After read the messages.log file, I suspect there is network connection issue. Let's fix the "CWWKO0801E: Unable to initialize SSL connection" first.
1) Add SSL configuration in server.xml. It's required for https connection. For example:
You can reference topic Configuring security with a basic user registry in the z/OS Connect EE documentation.
2) Add two z/OS Connect server connection in API toolkit, with port 9080 and 9443 separately. Test the connection is working well or not.
3) Deploy the API again via port 9080, then 9443, see what happen.
One tip for debugging, you can disable the user authentication with setting in server.xml as following:
try to deploy the API with port 9080. This is to avoid error "CWWKS1100A: Authentication did not succeed for user ID Y00894". If successful, we can make sure there is no network issue. Then remove this setting, continue to use basic authentication validation.