I am using Netbeans 8.2 and Tomcat 9. I just create a new project and trying to run but every time it shows this error and for existing projects also it is running another PC smoothly.
Can you please suggest something for the solution -
ant -f "C:\\Users\\UserName\\Documents\\NetBeansProjects\\Test" -Dnb.internal.action.name=run -Ddirectory.deployment.supported=true -DforceRedeploy=false -Dnb.wait.for.caches=true "-Dbrowser.context=C:\\Users\\Rifat Tanjir\\Documents\\NetBeansProjects\\Test" run
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
In-place deployment at C:\Users\UserName\Documents\NetBeansProjects\Test\build\web
deploy?config=file%3A%2FC%3A%2FUsers%2FRIFATT%7E1%2FAppData%2FLocal%2FTemp%2Fcontext4316755968276891464.xml&path=/Test
Server returned HTTP response code: 500 for URL: http://localhost:80/manager/text/deploy?config=file%3A%2FC%3A%2FUsers%2FRIFATT%7E1%2FAppData%2FLocal%2FTemp%2Fcontext4316755968276891464.xml&path=/Test
C:\Users\UserName\Documents\NetBeansProjects\Test\nbproject\build-impl.xml:1045: The module has not been deployed.
See the server log for details.
BUILD FAILED (total time: 14 seconds)
I am trying to deploy a spring boot microservices application to Google App Engine from Bitbucket Pipelines. I am getting this below error after commiting the code,
INFO: Setting up environment.
echo "${KEY_FILE}" | base64 -d >> /tmp/key-file.json
gcloud auth activate-service-account --key-file /tmp/key-file.json --quiet --verbosity=warning
Activated service account credentials for: [testproject-iamserviceaccoun#testproject.iam.gserviceaccount.com]
gcloud config set project testproject --quiet --verbosity=warning
Updated property [core/project].
> *INFO: Starting deployment to GCP app engine...*
gcloud app --quiet deploy 'app.yaml' --verbosity=warning
**ERROR: (gcloud.app.deploy) [/opt/atlassian/pipelines/agent/build/app.yaml] does not exist.
✖ Deployment failed.**
Please help me to solve this issue. Build Tool used is Maven.
bitbucket-pipelines.yml:
pipelines:
default:
- step:
name: Deploy to Google cloud
deployment: test
script:
- pipe: atlassian/google-app-engine-deploy:0.7.3
variables:
KEY_FILE: $KEY_FILE
PROJECT: 'testproject'
src/main/appengine/app.yaml:
runtime: java
env: flex
handlers:
- url: /.*
script: this field is required, but ignored
You need to specify DEPLOYABLES in your bitbucket-pipelines.yml, pointing to the path of your app.yaml file.
pipelines:
default:
- step:
name: Deploy to Google cloud
deployment: test
script:
- pipe: atlassian/google-app-engine-deploy:0.7.3
variables:
KEY_FILE: $KEY_FILE
PROJECT: 'testproject'
DEPLOYABLES: src/main/appengine/app.yaml
Reference: https://bitbucket.org/atlassian/google-app-engine-deploy/src/master/
There's about a million bug reports regarding the issue on NetBeans bug tracker but none of them brought me a resolution.
The issue is that when I try to profile my program, like this:
I get this:
cd C:\MYSELF\programing\java\AutoCall\AutoClient; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_31" cmd /c "\"\"C:\\Users\\Jakub\\AppData\\Roaming\\NetBeans\\7.4\\maven\\bin\\mvn.bat\" -Dexec.args=\"-agentpath:C:/Users/Jakub/AppData/Roaming/NetBeans/7.4/lib/deployed/jdk16/windows-amd64/profilerinterface.dll=C:\\Users\\Jakub\\AppData\\Roaming\\NetBeans\\7.4\\lib,5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\\MYSELF\\programing\\java\\AutoCall\\AutoClient\\nbproject\\private\\profiler -classpath %classpath cz.autoclient.Main\" -Dexec.executable=\"C:\\Program Files\\Java\\jdk1.8.0_31\\bin\\java.exe\" -DnetbeansProjectMappings= -Dmaven.ext.class.path=C:\\Users\\Jakub\\AppData\\Roaming\\NetBeans\\7.4\\maven-nblib\\netbeans-eventspy.jar org.codehaus.mojo:exec-maven-plugin:1.2.1:exec\""
Running NetBeans Compile On Save execution. Phase execution is skipped and output directories of dependency projects (with Compile on Save turned on) will be used instead of their jar artifacts.
Scanning for projects...
------------------------------------------------------------------------
Building Auto Client 3.0
------------------------------------------------------------------------
--- exec-maven-plugin:1.2.1:exec (default-cli) # autoclient ---
Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds (Protocol version: 14)
Profiler Agent Error: Timed out trying to establish connection with client
Profiler Agent: Initializing...
Profiler Agent: Options: >C:\Users\Jakub\AppData\Roaming\NetBeans\7.4\lib,5140,10<
Profiler Agent: Initialized successfully
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 12.012s
Finished at: Sun Jan 03 20:57:36 CET 2016
Final Memory: 5M/75M
------------------------------------------------------------------------
Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project autoclient: Command execution failed. Process exited with an error: -1 (Exit value: -1) -> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.
For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
This error seems to happen at random - I had several successful profiling sessions, then it happened again.
I was having the same problem, when I tryed to start the netbeans profile to analyze memory, I got the follow message:
Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project saf-desktop: The parameters 'executable' for goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec are missing or invalid -> [Help 1]
So, instead to run de profile mode, I started the application normally and then, I atached the profile mode in the currenty runnig main application.
Increase the timeout. Run netbeans with the following argument:
netbeans64.exe -J-Dprofiler.agent.connect.timeout=60
See https://blogs.oracle.com/nbprofiler/entry/tweaking_profiler_timeouts
I am running Jenkins job and afterwards I am getting timeout error:
get.hudson.release.version:
get.svn.build.version:
[echo] Determinating build version
[echo] Check SVN info for URL:
[svn] started ... Build timed out (after 30 minutes). Marking the build as failed. Build was aborted Archiving artifacts
I've checked configuration of job. It looks fine. URL is working. I can get it via the browser. How can I investigate/understand the root cause of problem?
After upgrading the appengine-maven-plugin from 1.7.5 to 1.7.6, trying to deploy my app now consistently fails with
$ mvn appengine:update
Beginning server interaction for myapp...
5% Using java7 runtime: false
25% Initiating update.
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=myapp&version=1.7.6&
500 Internal Server Error
If I revert to 1.7.5 it works again, so it may be an issue with the 1.7.6 Maven plugin or SDK. I've tried both enabling and disabling java7 but it makes no difference.
Update: deploying with appcfg.sh works fine, so it must be something with the Maven plugin.
Update #2: running with mvn -X shows the following plugin dependencies:
[INFO] --- appengine-maven-plugin:1.7.6:update (default-cli) # myapp ---
[DEBUG] com.google.appengine:appengine-maven-plugin:jar:1.7.6:
...
[DEBUG] com.google.guava:guava:jar:14.0.1:compile
[DEBUG] com.google.appengine:appengine-tools-sdk:jar:1.7.6:compile