I am having trouble deploying the app on to the worklight developerment server (Liberty profile).
Starting the eclipse from command line with -clean option did not help me. My configuration is
Eclipse Kepler SR2 Java EE - 32 bit version
Java 7 32 bit version
worklight plugin 6.1.0.01
Windows 7, 32G RAM, 512g SSD, core i7
I don't have any proxy network settings.
Whenever I select -> righ click -> Run As -> Run on WorkLight Development Server, the build process is taking very long time, approximately 30 mins. out of which almost entire time is spent at "Worklight application builder: (20%)
I'm almost certain that this happens because of the Java process.
My suggest to you is to kill the Java process running in your system followed by re-starting Eclipse. Then, try to start the server and repeat the Run As... steps.
Related
No information found for this. Is there any way to start weblogic in profiling mode? Or, maybe, it's activated by default?
Profiling action can be initiated 2 ways
1) Pass the profiling action while you execute the startWeblogic.sh. Following parameters can be appended
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8010
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
2) The same parameters can be appended from startup tab in weblogic server
Here's what i got. Mainly focused on remote profiling using NetBeans
generated remote profiling package for target OS and JVM architecture (32 or 64 bit) (Netbeans -> Profile -> Attach Profiler -> Change link, select OS and Java platform -> click "Create a remote profiling package" link)
copy this package to target machine
execute calibration script (calibrate.bat / calibrate.sh (chmod +x))
add specific argument to java_otps with path to this package
-agentpath:PathToProfilerPackage\lib\deployed\jdk16\windows-amd64\profilerinterface.dll=PathToProfilerPackage\lib,5140
restart weblogic. Startup will be interrupted until remote profiler connected
connect to a server using NetBeans profiler. Weblogic startup will continue.
However, i still can't download heap dump (which is available when attaching to local java.exe Weblogic process) but that's something.
During the App Packaging and Deployment for Universal Windows Apps presentation (fast forward to 00:36:00) one specific command line utility - WinAppDeployCmd - was used for deployment Windows 10 Universal application to the phone running Windows 10 Mobile. This utility could be found here:
"c:\Program Files (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe"
But every time I'm trying to deploy sample .appx package to the Lunia 635 phone with Windows Mobile v10.0.12562.84 or Surface 3 device with Windows 10 Pro Insider Preview (all devices on the same network as my dev machine) - I'm getting the same "connection failed" error:
Windows App Deployment Tool Version
10.0.0.0 Copyright (c) Microsoft
Corporation. All rights reserved.
Opening connection to device at '192.168.1.139'.
0x80131500 - Connection Failed
0x800705B4 - Timed out waiting for
network events.
Just in case - I could ping both of the devices from my dev machine without problem and can also deploy to any of them from VS2015RC (also tried with renamed WinAppDeployCmd.exe - to make sure that VS2015RC doing deployment somehow differently without using this tool).
So, I'm wondering - are there anyone who succeeded with app deployment using WinAppDeployCmd.exe?
This is a known issue in the current release. There is no workaround and it will light up in a future Windows 10 Insider Preview SDK and tools release.
https://social.msdn.microsoft.com/Forums/en-US/5c8d6f20-699c-4da2-9460-f73e89bf27c3/known-issue-cannot-sideload-applications-using-winappdeploycmd-windows-10-insider-preview-sdk-and?forum=Win10SDKToolsIssues
I have succeeded to deploy an .appx using the WinAppDeployCmd command line tool. Probably the issue have been correct at the latest versions.
For the ones that are not familiar with this tool, it allows you to deploy an Universal Windows app from a Windows 10 machine to any Windows 10 Mobile device via USB or WiFi (since they're on the same subnet). That's a perfect solution if you doesn't have Visual Studio, doesn't have the app source code or if you're under a Hyper-V Virtual Machine.
Basically you will need:
Windows 10 SDK
Generate the .appx package (PC)
Enable the developer mode (Mobile)
Turn on the discovery mode (Mobile)
Get the code to pair devices (Mobile)
Get mobile IP address using WinAppDeployCmd tool (PC)
Run command (PC)
The command will look like this
WinAppDeployCmd install -file “<path>” -ip <ip> -pin <pin>
The tool can be found at C:\Arquivos de Programas (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe
You can find a detailed step-by-step tutorial here
This happened to me once when the USB socket was faulty and Windows compained about the device not being recognized. I switched sockets and everything worked. So make sure you try other sockets (or even a different computer, to rule out the specific machine).
This tool let's you install but does not run the app after install like it did the first version in windows 8.1
Problem Description:
My Java application is launched using a .cmd file from a network path. It gets launched without any issues. But if I open TestComplete tool and then try to open the application, I get an error as "Could not create the Java Virtual Machine" as a popup with ok button. Upon clicking ok, the application process gets closed. Infact there is only option to click Ok:).
Environment Info:
I use TestComplete to automate a Windows based java application. The Java application is developed using Java 1.6 and TestComplete version is 10.5. The system is of Windows 7 64 bit. JRE in the local machine is of version 1.7
Understandings by googling:
My application is needs a JVM (Java Virtual Machine) with a heap memory of 1GB. TestComplete is somehow not letting it happen.
Trials Attempted:
1.Tried editing the heap size in Java control panel located in control panel with -Xmx1024m.
Does something rings for someone?
I've installed worklight 6 into an existing juno 64 bit eclipse running in windows 7. Runs great. I then install the jazz RTC 4.0.2 plug in into that eclipse environment. After the plugin is installed, there is a noticeable loss of function. The following are examples:
On the create new Hybrid app page, the option for changing the dojo library used is gone. The dialog resembles the WL5 version.
after a dojo hybrid is created, the www folder is missing from the WL project
Some dojo widgets do not work (i.e., not presented on the mobile device emulator or in resulting adroid application) like dojo.mobile.Heading
The only way to resolve is to uninstall the RTC plugin. Any suggestion on how to make this work? Using WL5.0.6.1 and same Jazz RTC plugin has no problems. We want to move to newer WL and upgrading RTC is not an easy option.
Are you using Eclipse Java EE 4.2.2? That's the only supported version for Worklight Studio (i.e. make sure you are not using 4.2.1 or 4.2 alone).
Other things I would try:
1) Use RTC 4.0.3 plug-in instead 4.0.2, that could make some difference and usually these clients have backwards compatibility with the server.
2) Install RTC before Worklight Studio, and see if it makes any difference.
I can't figure out where I am going wrong. I have Eclipse Indigo, JBoss 7.1, JBoss Tools installed. I have this configuration working on my Windows7 64-bit system. I am attempting to set up a co-worker's Windows XP 32-bit machine with the same configuration but am not able to get the server to launch. I have configured the server but when I attempt to start the server, I get an error indicating that it was unable to start the server but there is no specific error listed.
I am able to start JBoss from the command prompt using the standalone.bat file.
I am able to configure the standalone.xml file from within Eclipse. I have confirmed this by checking the file in the standalone/configuration directory.
When I attempt to publish the project from within Eclipse, it does not publish.
Nothing gets written to server.log
The startup parameters match what I have on my computer.
I can't figure out what I am missing. Any suggestions would be appreciated!
Edit:
I have done some more checking. I am able to publish to the server and I am able to start the server (with the published application) fine from the command prompt. That part works. When I attempt to start the server from within Eclipse it gives me "Server JBoss 7.1 Runtime Server failed to start." It never writes anything to the console tab in Eclipse either so I can't tell why it is failing to start.
Also in the Servers tab, there is an entry called "Server Details". When I expand that entry, it says "Not Connected".
The answer to my problem is that Eclipse had be configured to use the java JDK, not the JRE. As soon as I switched over to use the JDK it started working fine. For some reason JBoss will start under 64-bit windows with the JRE but under 32-bit you need to use the JDK. I found the answer here: https://community.jboss.org/thread/169097