I am trying to deploy amazon java web app to beanstalk(AWS Elastic Beanstalk for Tomcat 7) from eclipse using aws toolkit.
But i am facing following error,
Unable to update environment with new application version:
Environment named awseclipse is in an invalid state for this operation. Must be Ready.
(Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue; Request ID: da4518bf-13e4-11e4-9c13-97be58285d3c)
You probably have another deployment or change pending. As the error message mentions, you need to wait until your environment is ready to deploy a new version.
Related
When i try to deloy my web application using .war file on docker ubuntu aws ec2. I create container and assign the port to it. When I run it, I get the error 500 HTTP Status 500 - Internal Server Error. But when I execute it on eclipse, it works fine. The .war file I exported from the project followed this git hub link: https://github.com/vophucson/project-cloud
Please give me some advice
I have deploy on IBM Bluemix a spring boot application written in kotlin. I have use liberty for java.
But I cant able to run correctly my app, but on my machine in local it work very well.
When I call my REST API it return me an error or not work.
This is the error:
There was an unexpected error (type=Internal Server Error,
status=500). java.lang.NoClassDefFoundError:
it.gate42.skip.DeviceInfo.DeviceInfo_Accessor_ewee6w (initialization
failure)
I have already tried to change the Java version but the error is the same.
(I have set OPEN_JDK and version 1.8.+)
This is the log of call that return me the cloud foundry app: https://gist.github.com/paranoiasystem/a28a2587c231f2b398c4650ba1c7016c
I have post it on gist because is so long and it is impossible to post all log here.
I have resolved this issue, I have rewrite my manifest.yml like this:
---
applications:
- name: testskipapi
memory: 1G
instances: 1
path: build/libs/skipcode-0.0.1-SNAPSHOT.jar
buildpack: https://github.com/cloudfoundry/java-buildpack.git
env:
JBP_CONFIG_OPEN_JDK_JRE: '{ jre: { version: 1.8.0_+ } }'
I am creating a project using openshift v3 but was not able to find the wildfly
option in my openshift web console anymore from today . Untill yesterday it is coming.
I am not able to find the same anymore
tried creating it through terminal like
oc new-app --name=netsetos08 wildfly~https://github.com/test/test.git
--> Found image 18929ed (2 weeks old) in image stream "openshift/wildfly" under tag "latest" for "wildfly"
WildFly 10.1.0.Final
--------------------
Platform for building and running JEE applications on WildFly 10.1.0.Final
Tags: builder, wildfly, wildfly10
* A source build using source code from https://github.com/sarthak0488/checkincode.git will be created
* The resulting image will be pushed to image stream "netsetos08:latest"
* Use 'start-build' to trigger a new build
* This image will be deployed in deployment config "netsetos08"
* Port 8080/tcp will be load balanced by service "netsetos08"
* Other containers can access this service through the hostname "netsetos08"
--> Creating resources ...
error: User "test#test.com" cannot create imagestreams.image.openshift.io in project "default"
error: User "test#test.com" cannot create buildconfigs.build.openshift.io in project "default"
error: User "test#test.com" cannot create deploymentconfigs.apps.openshift.io in project "default"
error: User "test#test.com" cannot create services in project "default"
--> Failed
Not able to proceed by above also
This is a known issue which is resolved.After some time options come back in the web console
but command line is working as usual fine
oc new-app
It is fixed now
due to some company requirement I have enable the asadmin> create-service and set the GlassFish Server as a windows service while setting it to Start in a Automatic way. I am using Netbean 8.0.
However after I enable the Glassfish server service in auto method and when I try to deploy a Try sample project (Java Web) in Netbeans, after I RUN the project I got the following error in the Internet explorer.
HTTP Status 500 - Internal Server Error
Exception report
Internal Server Error
The server encountered an internal error that prevented it from fulfilling this request.
org.apache.jasper.JasperException: PWC6345: There is an error in invoking javac. A full JDK (not just JRE) is required
The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.0 logs.
However when I remove the Glassfish server from windows service list and when I run the project back, then it successful.
since I have no idea on java and all, can kindly help me to find the root cause of this or what is the workaround?
Thanks
Hasitha
I have a web application running on tomcat. I want to deploy it on a weblogic server but i get some problems.
Error(s) found in module 'BatchMonitoring'. Publish was cancelled. See "Problems" view for details.
Target runtime SpringSource dm Server (Runtime) v1.0 is not defined. at BatchMonitoring
Java compiler level does not match the version of the installed Java project facet. at BatchMonitoring
java.lang.IllegalArgumentException: Cannot find state with id 'displayError' in flow 'admin_main' -- Known state ids are 'array<String>['queryAll', 'mainForm', 'register']'
at org.springframework.webflow.engine.Flow.getStateInstance(Flow.java:348)
at org.springframework.webflow.engine.support.DefaultTargetStateResolver.resolveTargetState(DefaultTargetStateResolver.java:60)
at org.springframework.webflow.engine.Transition.execute(Transition.java:217)
at org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:391)
at org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214)
at org.springframework.webflow.engine.support.TransitionExecutingFlowExecutionExceptionHandler.handle(TransitionExecutingFlowExecutionExceptionHandler.java:110)
at org.springframework.webflow.engine.FlowExecutionExceptionHandlerSet.handleException
Seems like you had problems with Java versions of what Tomcat is using(points to JAVA_HOME) at environmental variable and JDK of Weblogic. Also it would be good if you send some logs and exception messages.