When I try to deploy a simple JS HTTP adapter to Bluemix MFP8 I am getting the following error message:
[ERROR] Failed to execute goal
com.ibm.mfp:adapter-maven-plugin:8.0.0:deploy (default-cli) on project
TestAdapter: Unexpected response from
http://nnnnnnnnn-server.mybluemix.net:80/mfpadmin/management-apis/2.0/runtimes/mfp/adapters:
-> [Help 1]
Though I get the error message, the adapter is deployed and works fine. However, the error looks really bad and I cannot go do a customer POC.
I saw a post on this issue in stackoverflow.com Failed to deploy a sample Javascript HTTP adapter on MFP 8 (MobileFoundation Bluemix) for MFP8 beta and the answer was it is a known issue and resolved internally.
Even in MFP8 GA, this issue is not resolved. Any plans to fix this?
PS: When I deploy the same to the local MFP8 server, I do not see this message.
You need to do two things:
Update to the latest CLI build: npm update -g mfpdev-cli and make sure using mfpdev -v that your version is "8.0.0-2016070716"
Delete the .m2 folder, in Mac it is located at the root folder: "~/.m2"
Now you can create a new adapter, build and deploy it to either local servers or remote servers.
Related
I tried to build an app using the GitLab pipeline and it failed with the following error
Execution failed for task ':react-native-reanimated:compileReleaseJavaWithJavac'.
But the app is built locally without any error. Can anyone have an idea why this happened?
I had a similar issue. Basically, your local machine and virtual machine on DevOps have different configurations. I solved it by updating the node and latest VM on azure DevOps. You can update your YAML file with the below code and change the node to the latest version available.
Please follow this solution: Android - `main` module field for "react-native-gesture-handler" lib that could not be resolved in Azure CI & its working fine in local machine
Please refer to the link from the Azure DevOps team for the latest mac os, Xcode, and node available. Cross-check with your local machine
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md
adonis application returns this error message when cloned the project and run after installing npm install, but the same project is working in another mac book pro. even i am using a mac book pro and it returns the following error. it says error 500.
Error
Cannot initiate session store since unable to parse `3b4204e91221f241deaad16ec6e4ddc0rs82L3YRb0FL72WnRgcJACuQ3Pur5KO5XigYeIuvLtuv+r27yI+dQXmZNbUUqX0URC5bzdBT1lnnZdZutBu4rVBPjvTKX00KR/RRsx9zjF0Zx2lqpSDdwJqUoGvJdM4YnJA3D6EK71GRVfpAeEprchMf5E0hdVEgnzVxV0wgqOg=`
The issue was really unknown and once i clean cookies from site settings of the browser, it was fixed itself, also i recommend to test all the sites on Incognito mode,
I have created API's in API connect toolkit. For testing the API locally in Explore tab, I am trying to start server.
But getting "Error: It appears that Docker for Windows has not been installed. To install Docker for Windows, please visit https://docs.docker.com/docker-for-windows/install/ For more information, check the docs" error.
From my understanding you don't need docker to test locally in toolkit. Any suggestions to fix the issue?
More Info: APIC version: API Connect: v5.0.8.3 (apiconnect: v2.7.209) NPM version : 6.1.0
It used to work before suddenly I am getting the above error. I tried re-installing but issue persist.
With new versions of APIC you must have Docker installed and working properly on your Windows environment to be able to install the API Connect Toolkit with DataPower.
Please find the steps to install the APIC toolkit on these pages:
https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/tapim_cli_install.html
https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/tapim_apic_test_with_dpdockergateway.html
I recently installed IBM MobileFirst CLI on my Mac, but I don't seem to be able to start the Server. See error below. I searched the internet and found that there is a bug in JDK which causes the JavaLaunchHelper error. I downloaded the beta version that supposedly fixes the issue from here - JDK Download Link
. But this doesn't help either. Any other help is appreciated.
Imayas-MBP:EmployeeDirectory imaya$ mfp start Initializing
MobileFirst Console. objc[18564]: Class JavaLaunchHelper is
implemented in both
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin/java
and
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib.
One of the two will be used. Which one is undefined. Starting
server worklight. Server worklight start failed. Check server logs
for details.
/Users/imaya/.ibm/mobilefirst/6.3.0/server/wlp/bin/server: line 744:
18563 Abort trap: 6 "${JAVA_CMD}" "$#" > "${JAVA_CMD_LOG}"
2>&1 Error: The MobileFirst server failed to start. The port may be in
use by another instance of a running server, or the server may not
exist.
The JavaLaunchHelper error is not the problem here; Anyone using Java 7 will experience it, but things will work regardless.
The problem here is the second error:
The MobileFirst server failed to start. The port may be in use by
another instance of a running server, or the server may not exist.
Verify you do not have an already running server, that was started either by the CLI or by MFP Studio in an Eclipse installation.
In the command line, run mfp stop
In Eclipse, well, quit it
Make sure the Java process is not running
Then, start over. Using the CLI, create a new project and application and try to start the server. For example:
cd /Users/idanadar/Desktop
mfp create testProject
cd testProject
mfp add hybrid testApp
mfp start
mfp build
mfp deploy
mfp console
On OSX, you can locate and kill a process holding open a port using the following:
Run (assumes port 10080):
$ lsof -i :10080
Then if a process is shown, run the following using the shown Process ID:
$ kill -9 {PID}
We have followed the silent installation procedure on remote server as mentioned in the IBM Developer documentation of 6.3 from the link:
https://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.installconfig.doc/dev/t_silent_installation.html
Downloaded the MobileFirst CLI 6.3 file from the link::
http://public.dhe.ibm.com/ibmdl/export/pub/software/products/en/MobileFirstPlatform/mobilefirst_cli_installer_6.3.0.zip
unzipped it to MobileFirst CLI 6.3.0 and copied installer.properties file with fallowing content in that,
LICENSE_ACCEPTED=TRUE
USER_INSTALL_DIR=/opt/ibm/Worklight-CLI
and staying in the same folder, i installed the CLI 3.0 to the specified folder:
./install_linux.bin -i silent -f installer.properties
App has installed to the /opt/ibm/Worklight-CLI directory.
We then created a sample app as per Command Line commands specified in the link:
http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.dev.doc/dev/r_wl_cli_commands_and_their_definitions.html
$ mfp create MyProject
$ cd MyProject
$ mfp build
$ mfp deploy
After app build and deployment, when we tried to check the MobileFirst Console over browser, with link:
http://xxx.xxx.xxx.xxx:10080/worklightconsole
after logging in to admin/admin credentials, page shows, loading the environments, but after waiting for 30 sec or more, it throws error as in the attached image.
But in log file shows some JAR file are missing. And i tried installing fresh copy of MFP 6.3 many times. but all time the same issue.
Please find the attached logs file and screenshot.
I am not able to find out what is the exact problem.
Server error. Contact the server administrator.
Server Configuration:
Ubuntu 14.04.01 LTS
MobileFirst Version : 6.3.0.00.20141127-1401
java version: "1.7.0_65"
java.home = /usr/lib/jvm/java-7-openjdk-amd64/jre
OpenJDK Runtime Environment (IcedTea 2.5.3) (7u71-2.5.3-0ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
The Console error Message:
Log file:
[12/11/14 10:27:57:376 IST] 0000002f
m.ibm.ws.container.service.app.deploy.ManifestClassPathUtils W
SRVE9967W: The manifest class path jaxb-api.jar can not be found in
jar file
wsjar:file:/home/administrator/.ibm/mobilefirst/6.3.0/server/wlp/usr/servers/worklight/apps/worklightconsole.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar
or its parent.
[12/11/14 10:27:57:376 IST] 0000002f
m.ibm.ws.container.service.app.deploy.ManifestClassPathUtils W
SRVE9967W: The manifest class path activation.jar can not be found in
jar file
wsjar:file:/home/administrator/.ibm/mobilefirst/6.3.0/server/wlp/usr/servers/worklight/apps/worklightconsole.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar
or its parent.
[12/11/14 10:27:57:376 IST] 0000002f
m.ibm.ws.container.service.app.deploy.ManifestClassPathUtils W
SRVE9967W: The manifest class path jsr173_1.0_api.jar can not be found
in jar file
wsjar:file:/home/administrator/.ibm/mobilefirst/6.3.0/server/wlp/usr/servers/worklight/apps/worklightconsole.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar
or its parent.
[12/11/14 10:27:57:377 IST] 0000002f
m.ibm.ws.container.service.app.deploy.ManifestClassPathUtils W
SRVE9967W: The manifest class path jaxb1-impl.jar can not be found in
jar file
wsjar:file:/home/administrator/.ibm/mobilefirst/6.3.0/server/wlp/usr/servers/worklight/apps/worklightconsole.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar
or its parent.
[12/11/14 10:27:57:637 IST] 00000029
com.ibm.ws.webcontainer.osgi.webapp.WebGroup I
SRVE0169I: Loading Web Module: IBMJMXConnectorREST.
You've only linked to the documentation. Please edit the question and describe what you've actually done.
These are the steps I have taken (based on the CLI tutorial) in order to create a new project and application using MobileFirst CLI and then open MobileFirst Console:
System:
OS X 10.10.1
Oracle Java (default installed by the OS)
In Terminal:
cd /Users/idanadar/Desktop
mfp create testProject
cd testProject
mfp add hybrid testApp
mfp start
mfp build
mfp deploy
mfp console
The console was opened:
Check to see if there are any spaces in the path for your eclipse workspace. There is a known limitation with Liberty 8.5.5.3, which is the internal development server included in MobileFirst Platform Foundation 6.3, that you cannot have whitespace in the path name:
https://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.getstart.doc/start/c_known_limitations.html
The failures, which match what shows in your log file, can occur on console startup and app deploy or preview.
The Issue is with the Hosted Server. They have opened the port 10080 partially. as port is allowing one way communication. because of some security reason, Hosting Server organisation has put some restriction over it. Now its resolved. Now we can able to deploy, and check the deployed apps over the worklight Console.
Thank you all for your suggestions and effort to go through my long listed question and trying out to resolve it.
I posted this comment: as some other persons may face same issue. so at least they can rid of this kind of issue ASAP.