I am using eclipse juno 4.2.1 and IBM worklight 6.0 on my mac mini. since yesterday I am trying to build and deploy my application but its giving me "Worklight application builder" error.
here is the log:
An internal error occurred during: "Worklight application builder".
loader constraint violation: when resolving method "org.apache.commons.io.FileUtils.iterateFiles(Ljava/io/File;Lorg/apache/commons/io/filefilter/IOFileFilter;Lorg/apache/commons/io/filefilter/IOFileFilter;)Ljava/util/Iterator;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, com/worklight/builder/skins/impl/SkinBuilderImpl, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/apache/commons/io/FileUtils, have different Class objects for the type o/filefilter/IOFileFilter;Lorg/apache/commons/io/filefilter/IOFileFilter;)Ljava/util/Iterator; used in the signature
and console shows this message :
[2013-09-25 15:18:46] Starting build process: application 'TestApp', all environments
[2013-09-25 15:18:46] com.worklight.shared.common.messages:tgn309.trigyn.com: tgn309.trigyn.com: nodename nor servname provided, or not known
java.net.InetAddress.getLocalHost(InetAddress.java:1466)
com.worklight.common.util.GeneralUtil.scanIPAddresses(GeneralUtil.java:581)
com.worklight.common.util.GeneralUtil.scanIPAddresses(GeneralUtil.java:549)
com.worklight.common.util.GeneralUtil.getIPscanResults(GeneralUtil.java:642)
com.worklight.studio.plugin.utils.WSTServers.getServerHost(WSTServers.java:174)
com.worklight.studio.plugin.utils.WSTServers.getServerURL(WSTServers.java:661)
com.worklight.studio.plugin.launch.build.apps.WorkspaceApplicationBuilder.buildApplication(WorkspaceApplicationBuilder.java:325)
com.worklight.studio.plugin.launch.build.apps.WorkspaceApplicationBuilder.runInWorkspace(WorkspaceApplicationBuilder.java:158)
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
[2013-09-25 15:18:46] FWLPL0010W: "localhost" was detected from the target server configuration. Using the primary IP address of the host machine, 10.30.1.102, to build the Worklight application(s). Consider using a fully qualified hostname (avoid using "localhost") or a valid IP address instead. The value can be modified by opening the configuration editor of Worklight Development Server from the "Servers" view.
Any help would be appreciated.
Try the suggestion given in the following answer, as it seems somewhat related based on the error in your question: IBM Worklight 6.0 - Migration Issue after importing a project
Copy/paste:
Please try to find if you have apache commons IO installed in your
Eclipse plugin directory. That's the source of the conflict.
If you can, please try to:
stop the Eclipse
move the apache commons IO out of the plugin dir
start Eclipse, then close it
move the commons IO back into the plugin dir
Start Eclipse
Related
I'm trying to debug worklight 6.1 adapter code (java). I figured the most logical way would be to restart the imbedded liberty server in debug mode. That fails with a message:
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
I followed the process documented for 6.0 at Logging and debugging Java on Worklight Server but I get the same issue there.
Ok, this is silly, but I just figured it out. You do not need to set anything for debug mode. Apparently in 6.1 this is already set. To begin debugging of your java code in the adapter you need to do the following:
Create a debug configuration for a "Remote Java Application".
Set the project to your worklight hybrid project
I set the port to 10777. which is what jdwp was set to in the jvm.options file for the worklight server.
Once you click on debug for that configuration, it will allow you to debug your adapter.
You can see the jvm.options file if you expand the Worklight Development Server definition in the Servers view. See below for an example of the contents of that file.
-Dfile.encoding=UTF-8
-Duser.language=en
-Duser.country=US
-Djava.awt.headless=true
-Dwas.debug.mode=true
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=10777
-Dcom.ibm.websphere.ras.inject.at.transform=true
Uploaded video to youtube on how to do this
We are setting up Tridion 2011 SP1 CDS (.net based) on one of our servers.
We are sruck at point 'Installing Monitoring as a Wndows Service'.
Evern after running the batch file 'StartCDInstaller.bat' and following the procedure, we cannot locate the Tridion Monitoring Agent service in the windows services.
Are we missing something?
Also another question regarding CDS, can we change the location of config files (Deployer, Storage_conf etc) post Installation? Or do we need to re-run the installer?
Update:
The same error even after reinstalling the monitoring service.
"The Event log details: The description for Event ID 100 from source TCDmonitor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted"
You can change the location of tridion folder structure by setting the System variable in environment variable(Control panel -> system and security -> System -> Advance -> Environment variables -> system variables) called "Tridion_Home" and value as "d:\tridion" (this is the path of the tridion folder ). You can test this after going to run and type %tridion_home% .
If for some reason the Tridion Monitoring Service was not installed by the installer, you can do it manually.
Locate the file cd_monitor.exe (it is on the installation CD in Content Delivery\roles\monitoring\windows).
Copy it to a location where you keep your executables (e.g. to the Tridion\bin folder)
Start a command prompt as administrator and type 'cd_monitor -install'
Go to the services console and start the monitoring service
Had a similar issue too, it was an x64 Content Delivery server with x64 Java installed. Manually installed the monitoring service but refused to start with:
The description for Event ID 100 from source TCDmonitor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Could not load Java runtime libraries at
the message resource is present but the message is not found in the string/message table
The monitoring service requires 32bit Java, as soon as that is installed it started with no problem.
Hope that helps.
Scott
I'm trying to deploy my Grails application to AppFog using CloudFoundry plugin (ver. 1.1) in Spring Source Suites (STS 2.9.2).
I'm using https://api.appfog.com as server address and MYAPPNAME.aws.af.cm for application address when deploying app.
Application is pushed and started, services are bounded but, after that, I recive error saying that:
Communication with server failed: I/O error: Server returned HTTP response code: 405 for URL: https://api.appfog.com/apps/MYAPPNAME/application
Also, when I try to create Caldecott tunnel toward database I recive response "The URIs: caldecott-85393a.appfog.com have already been taken or reserved. (404 Not Found)" which I also saw when (by mistake) treid to deploy application to MYAPPNAME.api.appfog.com (default AF name instead of particular infrastructure adress).
I suppose that CloudFoundry plugin uses default server address to reach application and also trying to create Caldecott tunnel on default server address (caldecott-85393a.appfog.com instead of caldecott-85393a.aws.af.cm)
Does anybody have idea how to circumvent this situation?
BR
Zoran
this doesn't sound like an issue with the plugin itself but the response coming back from AppFog's cloud. I would take this up as an issue with them and clarify you can use that plugin with their cloud.
AppFog had issues recently with their Java deployments that was specifically affecting Grails apps. This has been resolved and should be working seamlessly as expected now. You can always reach out for more information in the active google group as well: https://groups.google.com/forum/#!forum/appfog-users
I have this project having MSSQL 2008 R2 as its database server. The connection between the Services view of IReport and the database is established and running. The problem here is that the project cannot connect to the database server when running it.
These is the error showned on grails console prior to start-up completion:
ERROR hbm2ddl.SchemaUpdate - could not complete schema update
I've seen similar case but the way to resolve it is having the driver sqljdbc4.jar put inside the [Project Name]\classpath\Grails Dependencies (project explorer heirarchy) where the driver is located in the [Project Name]\lib. But the do how has gone missing.
I've also tried to manually install the dependency following the commmand below but grails return that the driver is not found.
grials> install-dependency sqljdbc4
The question is how can I include the driver into the Grails Dependencies?
Assuming you are running Grails 2+, this article should help you. I also had to restart Eclipse before everything actually showed up correctly.
I've manage to deploy my Grails app on my local pc on Tomcat and database is on MySql server but I cant manage to do it on remote server in the same enviroment.
This is the begining of stacktrace:
java.lang.UnsupportedClassVersionError: org/codehaus/groovy/grails/plugins/springsecurity/SpringSecurityUtils : Unsupported major.minor version 51.0 (unable to load class org.codehaus.groovy.grails.plugins.springsecurity.SpringSecurityUtils)
Either use the same JVM version on the server as you are using on your local pc OR use a higher version on the server. Typically, that should solve your problem
You're compiling and running with different JVM versions.
The JDK version on your computer should be the same that is installed on the remote server.