I really appreciate the help i've been getting on Stack Overflow, it's helping me become a better programmer.
Im currently learning how to use the Google App Engine, and ive just developed my first app, but im finding it difficult to run. When i run it, it throws the following exceptions:
WARNING: Use on a JRE prior to version 1.6 is deprecated
2011-06-04 12:19:21.190 java[1921:80f] [Java CocoaComponent compatibility mode]: Enabled
2011-06-04 12:19:21.191 java[1921:80f] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Initializing AppEngine server
[WARN] ********************************************************
Warning: Future versions of the Dev App Server will require Java 1.6 or later. Please upgrade your JRE.
********************************************************
Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Successfully processed /Users/josiahuma/Projects/Eclipse/JWorkspace/HelloWorld/war/WEB-INF/appengine-web.xml
Successfully processed /Users/josiahuma/Projects/Eclipse/JWorkspace/HelloWorld/war/WEB-INF/web.xml
Ive tried looking for ways to download and install JRE 1.6 or maybe upgrade it like the error say, but haven't found any on MAC...
Please can anyone help put me through on what exactly i need to do so i can get my first app running. Would really appreciate it.
Upgrade to 10.6. The default JVM is Java 6 there.
Related
I can't run payara 4.1.2.181 with java 7 (Orracle jdk 1.7.0_80).
I have no problem with java 8 and the previous build of Payara (4.1.2.172) runs fine with Java 7. I couldn't find any mention about stopping support for Java 7 in this version.
The error I got is this one (server.log):
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle fish.payara.microprofile.fault-tolerance.microprofile-fault-tolerance [149]: Unable to resolve 149.0: missing requirement [149.0] osgi.wiring.package; (&(osgi.wiring.package=org.eclipse.microprofile.config)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 223.0: missing requirement [223.0] osgi.ee; (&(osgi.ee=JavaSE)(version=1.8))]
Co you have any idea how to solve it?
Regards
Piotr
Payara stopped supporting JDK7 for public releases in 4.1.2.173, as explained in this blog post. It is still available for paying customers until 2023. So either upgrade to JDK8 or get Payara support.
I have failed to install Apache Zeppelin (v. 0.7.1) on my Windows 7 desktop.
I would like to proceed without having to install Docker, however.
I tried reinstalling the Java runtime etc. but Zeppelin does not start.
Any suggestions?
(I am aware of version 0.7.3 but don't feel like wasting even more time trying it on Windows 7).
Please share the errors your are getting. Confirm you have made all the settings (environmental or otherwise) as required.
I am getting the below exception while trying to connect a esx-i 5 machine using vijava vsphere API.
vijava is the VMware Infrastructure JAVA API.
I am using the VI Java API 5.5 Beta vijava55b20130927.
What might be the root cause of this issue.
java.rmi.RemoteException: VI SDK invoke exception:java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException: **Error on line 4 of document : Open quote is expected for attribute "{1}" associated with an element type "rel".** Nested exception: Open quote is expected for attribute "{1}" associated with an element type "rel".|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:131)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1437)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:100)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:84)|
If you will switch to using YAVIJAVA I can help.
The Beta version of VIJAVA has a bug where only a RemoteException is ever thrown. That bug is fixed in YAVJAVA 5.5.08-DEVELOPMENT or newer which as of this comment is only available on github (older versions in maven have this bug)
YAVIJAVA includes logging via log4j and if you enable debug logging when you run the command you can even get the XML payloads that are coming and going from the server which I can use to help you trouble shoot this problem.
I'm using Worklight 6.2 server edition and I can't deploy a working runtime (of other environments) on my server.
I'm using webpshere liberty profile v8.5.5 and when I deploy the runtime via GUI it says success and on server.xml I can see the new configuration for the app.
However when I go to the worklightconsole I don't see my runtime to upload the app.
On messages.log there is a error regarding JMX connection.
The quoted error is
Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured
I'm refering this because I've seen some post on SO saying that these issues might be connected. However I have the restConnector-1.0 on my WLP features.
Reference: No runtime on my Worklight 6.2 Console after installing analytics
On messages.log there is some other things that I found interesting, like the correct start of the runtime I've deployed
[11/12/14 5:50:45:177 CST] 00000012 com.worklight.server.bundle.project.JeeProjectActivator I FWLST0002I: ========= Project /HelloWorld started. The project WAR file version is 6.2.0.00.20140922-2259,running on server version 6.2.0.00.20140613-0730. [project HelloWorld]
and two erros while starting my server
[11/12/14 5:50:49:911 CST] 00000012 SystemErr R 24 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/opt/IBM/WebSphere/Liberty/usr/shared/resources/worklight/lib/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
Second error:
java.lang.RuntimeException: Timeout while waiting for the management service to start up
I don't know what these are but I think it might be related to my problem and this errors eventually appear when I start my server.
Does anyone have any tips for troubleshooting this issue?
Thanks in advance.
This is a known issue from Websphere.
There is a APAR to fix that, a workaround is to restart the server with the --clean option to force a refresh onto the shared libraries.
http://www-01.ibm.com/support/docview.wss?uid=swg1PI17830
I try to use this command to deploy my application to
appspot.google.com:
c:\a\appeng\bin\appcfg.cmd --use_java7 update c:\a\u3e
Generates the error messsage.
C:\a>c:\a\appeng\bin\appcfg.cmd --use_java7 update c:\a\u3e
Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.7', but '1.6' is required.
Error: could not find java.dll
Error: could not find Java SE Runtime Environment.
I tried setting the path to use the Java 1.6 SDK we downloaded
but that did not help or change any thing.
The web resources talk about what version of Java is used
by the application once it appears on Google's servers; I
did not see anything about the Java version for the upload
process including developers.google.com/appengine/docs/java/gettingstarted/uploading and developers.google.com/appengine/docs/java/tools/uploadinganapp#Command_Line_Arguments as well as searching this site specifically and checking google.
Can I deploy
an application from the computer in my house without
deinstalling the Java 1.7 I use for other purposes?
Thank you for looking at this question. I resolved the problem. It was not related to Google Application Development
Server. It was a difficult-to-resolve path problem to the directory where the Java executables were kept.