Every time i try to create a new Worklight server all of my resources get duplicated... and I believe its causing errors when i deploy.
What I have tried to fix this issue so far:
Deleted server, and created a new one. Same result
Deleted my workspace and started from scratch. Same result
Completed removed eclipse from my workstation. Same result
Is there any other explaination for this behavior? I am using a fresh Eclipse Luna SR2 install, with a fresh install of the MFP 7.1 plugin.
This is a known APAR: PI50480 ALL MOBILEFIRST SERVER .WAR FILES IN MOBILEFIRST STUDIO APPEAR TWICE
The development team is working on fixing it. That said, this duplication has no effect on your project. You can ignore it.
Related
We just had installed the latest iFix (7.0.0.0-MFPF-Server-IF201611140235) in our app server. Upon checking the version in the MFP Console, it still in the previous version. I've checked the directory /opt/IBM/MobileFirst_Platform_Server/WorklightServer, and found that the .war files not been updated. I've check the installation history and it shows that I successfully installed/updated it. I also noticed that the file worklight-jee-library.jar still in the previous version.
How should I refresh the files? Looks like the installation is not updating the .war files and libraries.
Thanks,
Jonathan
From the comments:
What we did is to manually copy the WAR and JAR files to Tomcat folders (/webapps and/ lib). It is now showing the correct version in the console. We recompile the app using this iFix version (IF201611140235), and deploy the new app WAR file to the server.
Developer server version is
mfp -v: 7.1.0.00.20160206-1603
Production server version is
wladm -version 7.1.0.00.20150807-0630
Project is mfp cordova type.
Building for developer server.
App built with Ant works.
App built with Gradle works.
Building for production server.
App built in release/debug with Ant - works fine.
App built in release/debug with Gradle, gets [...android/init] timeout or 500.
Signing is the same.
Configuration is the same.
wlapp is properly deployed to production and developer server.
On device app looks fine. Everything is ok, but cannot connect to WL server.
Looks like something is wrong with app authenticity.
But Ant signed-release works. Gradle signed-release/debug fails to connect.
Same project, same settings. Whats wrong. Have you seen this?
EDIT
Looking at logcat logs, found this error
java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/.../base.apk"],nativeLibraryDirectories=[/data/app/.../lib/arm, /vendor/lib, /system/lib]]] couldn't find "libauthjni.so"
But when I just change address (wlclient.properties) to local Dev server - everything is ok. No error.
Cordova applications created with the CLI are based on Cordova 3.7.
Cordova 3.7 does not support a Gradle-based project structure.
We upgraded our AIX Environment from WL 6.1.0 to 6.1.0.1 without stopping the WL Server (ApplicationCenter is not installed in this WAS Profile). We have WAS 8 in Netowrk Deployment Configuration.
Installation Manager installed it successfully, then we reboot the server and we got this trying accessing the console:
Error 500: javax.servlet.ServletException: Worklight Console
initialization failed.Logged Exception:
com.worklight.server.database.api.WorklightDataSourceException:
FWLSE0194E: Worklight server cannot be started because of failure
while getting a connection from data-source bound to resource
reference: jdbc/WorklightDS. Make sure the database is up, the
credentials are correct and the driver is available for the server.
[project buytec_worklight]
I searched the right way to upgrade and I saw that we should have stopped the server than we should follow this procedure:
http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.upgrade.doc%2Fdevenv%2Fc_upgrade_to_srvr610_upgrading_wl_console_upgrade_console.html
But at first, with WL 6.1.0 we didn't use the ant-task to deploy the console, we just put the .war found in the Eclipse Studio with the right plugin, so now i cannot manage to understand how to upgrade the console manually.
Have you any suggestions?
I don't know what you mean by "upgrade the console manually". The Worklight Console is part of the .war file you deploy to the application server, but the console doesn't have anything to do with the connection to the database.
If you want to "upgrade the console", you actually mean that you want to update the .war file, so deploy a .war file that was generated using Worklight Studio 6.1.0.1.
You can also follow the manual upgrade instructions for 6.1.0.1: http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_addl_info_manual_app_srvr_upgrade.html
Because you didn't properly start the upgrade process, I suggest that you will take the time to review all upgrade topics, from the start: http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr610_in_production_env.html
In addition, it doesn't matter how you first installed 6.1.0.0, you can still use either Ant or manual upgrading.
I simply re-add the .jar files driver for db2, checking that they are resolved, set again the Data sources JDBC, uploaded a new console.war created with eclipse and it worked!
We have a Live mule server (Community edition ) 3.3.0 running on a Windows 2008 server.
We have several apps running on it.
We tried to hotdeploy a new app in it. It failed saying some port was already in use/bind - this was a JMX port. However we were unable to undeploy it. It didn't create any anchor file as it had failed deployment so we couldn't do the clean undeploy. When we tried to delete the exploded folder it didn't allow as it said the jars in the lib were in use.
We tried to re-deploy the same file with fix again but it had no effect.
Question is irrespective of what caused out application to fail - how can one undeploy or take out a Mule app (failed) completely? It doesn't have anchor file and trying to delete says jar in use. Only way we could do was to stop mule and then delete the folder and restart Mule - totally unacceptable in production environment.
Any clues?
This is a known bug on 3.3.0 that was fixed on 3.3.1.
Somehow, at some point, I installed this version of the Eclipse Glassfish Plugin for Juno:
Oracle GlassFish Server Tools 2.0.1.201207240829
I'm trying to help a co-worker install it too. But the latest version from the marketplace is
Oracle GlassFish Server Tools 2.0.1.201201241920
I think I must have gotten it from here which is referenced in this accepted anser but that site is now dead. That site is also referenced in this question
Does anyone know what the heck is going on with Eclipse Glassfish Plugin for Juno and Glassfish 3.1.2.2, and/or a different place from where we can get the version I seem to have?
Or else, tell me where I can report this problem to the team that maintains this plugin other than SO?
Oracle is currently migrating the GlassFish plugins - see
https://blogs.oracle.com/piotrik/entry/migration_of_eclipse_plugins_java
for details.
The old update site http://dlc.sun.com.edgesuite.net/glassfish/eclipse/juno/ is working again (despite appearing empty when you open the URL in your web browser).