I want to cancel then start my build through url:
This how I starting my build:
http://<user name>:<user password>#<server address>/httpAuth/action.html?add2Queue=<build type Id>
but when I'm trying to cancel/stop it:
http://<user name>:<user password>#<server address>/ajax.html?comment=<cancel_comment>&submit=Stop&buildId=<internal_build_id>&kill
I'm getting exception:
Error message: Given kill operation code is null
TeamCity: 8.0.5 (build 27692)
Operating system: Windows Server 2008 R2 (6.1, x86)
Java: 1.7.0_21-b11 (Oracle Corporation)
Servlet container: Apache Tomcat/7.0.37
Trace: java.lang.IllegalArgumentException: Given kill operation code is null
Source: Accessing server by HTTP
I tried through REST API but didn't helped me.
I analyze js code in TeamCity and found 2 solution
Kill build by process id :
yourTeamCityUrl/ajax.html?comment=%somment%&kill=%buildQueueId%&operationKind=2&_readd=&submit=Stop
Kill build by build id:
yourTeamCityUrl/ajax.html?comment=%comment%&submit=Stop&buildId=%active_build%&kill&operationKind=1
only need to add &operationKind=1
Related
I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.
When I am trying to hit my application url, I am getting "ActiveX component can't create object error. WebsiteError:8004e025" error in the browser. This application is hosted in IIS and operating system is Windows Server 2003 32-bit.
When I checked event viewer logs, I got following error:
Event Type: Error
Event Source: COM+
Event Category: (98)
Event ID: 4840
Date: 06/06/2016
Time: 13:24:45
User: N/A
Computer: APW02508WCAPP02
Description:
The IObjectControl::Activate() method failed. The CLSID of the object is:
{CAFBD1A2-73BD-438B-841C-A9C88BD4C248}
Server Application ID: {74CF179D-508C-43FE-AE29-B3480386BDE3}
Server Application Instance ID:{E7855B79-7A03-4E7A-8BA4-37666501917F}
**Error Code** = **0x800a01ad**
COM+ Services Internals Information:
File: d:\nt\com\complus\src\comsvcs\jit\jit.cpp, Line: 475
Comsvcs.dll file version: ENU 2001.12.4720.3959 shp
I tried registering Comsvcs.dll and it got registered, but still I am getting same error. I know that this is not a code issue as this application works on other windows server 2003 machine. Only on this particular machine, I am getting this error. Can anyone please tell me how to resolve this?
I've installed Netbeans 7.2. with GlassFish Server 3.1.2 but when I run web application the default jsp page or any other jsp pages I got the error:
GlassFish Server 3.1.2 Start Failed
C:\Users****\Documents\NetBeansProjects\WebApplication3\nbproject\build-impl.xml:1022:
Deployment error: GlassFish Server 3.1.2 Start Failed See the server
log for details. BUILD FAILED (total time: 47 seconds)
build-impl.xml
< target depends="init,-init-cos,compile,
compile-jsps,-do-compile-single-jsp,-pre-dist,-do-tmp-dist-with-manifest,-do-tmp-dist-without-manifest,-pre-run-deploy,
-pre-nbmodule-run-deploy,-run-deploy-nb,-init-deploy-ant,-deploy-ant,-run-deploy-am,-post-nbmodule-run-deploy,-post-run-deploy,
-do-update-breakpoints" name="run-deploy"/>
< target if="netbeans.home" name="-run-deploy-nb">
< nbdeploy clientUrlPart="${client.urlPart}" debugmode="false"
forceRedeploy="${forceRedeploy}"/>
////////////////////////
glassFish Server 3.1.2
SEVERE: Shutting down v3 due to startup exception : No free port
within range:
8080=com.sun.enterprise.v3.services.impl.monitor.MonitorableSelectorHandler#788a7b
I've found the solution. My 8080 port was reserved by Oracle. So I edited the domain.xml file inside glassfish\domains\domain1\ config\domain.xml file.
I replaced the port 8080 with 9999 and replaced the file. After that I added the glassfish server to netbeans, and now it is working.
Thank You everyone.
The error message states it clearly:
No free port within range: 8080
Probably there is another instance of Glassfish (or any other server) running on your system. Try to find it out by calling http://localhost:8080 in your browser.
**Another option to solve this probs
**Enter the following on the command line:
netstat -ao
The active TCP addresses and ports will be listed — locate the line with local address “0.0.0.0:80″ and note the PID value.
Now right-click the task bar and select Start Task Manager. Navigate to the Processes tab and, if necessary, click View > Select Columns… to ensure “PID (Process Identifier)” is checked. You can now locate the PID you noted above. The description and properties should help you determine which application is using the port.
The Task Manager allows you to kill the process, but be a little wary about doing that — especially if it’s “NT Kernel & System”.**
i had the same problem.
i solved it by configuring the glassfish with jdk7 instead of jdk8.
i dont know why it wasnt working with jdk8 but now the glassfish is running.
I am deploying my BPEL project on Web-logic server through my JDeveloper 11g. its working fine. but when I selected my different environment for deployment(new one) then I got the following error.
Error is due to one of my BPEL prcess "TaskProcess1".
but the same setup when I deploy to my own server its deploying and running very fine.
code=500
[04:53:57 PM] Error deploying archive sca_RegistrationUpload_rev24.0.jar to partition "default" on server DAMS_Batch_Server1 [urasvr140.uradevt.gov.sg:8001, Cluster:DAMS_Batch_Cluster]
[04:53:57 PM] HTTP error code returned [500]
[04:53:57 PM] Error message from server:
#;There was an error deploying the composite on DAMS_Batch_Server1: Operation failed - Member(Id=1, Timestamp=2011-06-02 15:25:57.428, Address=172.16.10.45:8088, MachineId=46637, Location=site:uradevt.gov.sg,machine:urasvr140,process:3968, Role=WeblogicServer):Error occurred during deployment of component: TaskProcess1 to service engine: implementation.bpel, for composite: RegistrationUpload: ORABPEL-01005
#;
#;Failed to compile bpel generated classes.
#;failure to compile the generated BPEL classes for BPEL process "TaskProcess1" of composite "default/RegistrationUpload!24.0*soa_f19c6537-e518-4c05-940c-688c1ddb2593"
#;The class path setting is incorrect.
#;Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
#;; . Please see the server diagnostic logs on DAMS_Batch_Server1 for details.
Please let me know if any suggestion you have.
Is there a dependant jar file that you are accessing from your bpel process?
Check the log files on the server for the soa_server. It will give you more information as to why it failed at the server
I am able to generate code using Autorest with my api when I host it on a server 2012R2 running IIS
However when I try to run it with the localhost url I get a could not read message.
I can read swagger.json in the browser
I am using the command
autorest --input-file=https://localhost:44348/api-docs/v1/swagger.json
--output-folder=generated --csharp --namespace=DD.MyApp.Connector
The output is
AutoRest code generation utility [version: 2.0.4283; node: v10.11.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core 'C:\Users\kirst\.autorest\#microsoft.azure_autorest-core#2.0.4289\node_modules\#microsoft.azure\autorest-core\dist' (2.0.4289)
Loading AutoRest extension '#microsoft.azure/autorest.csharp' (~2.3.79->2.3.82)
Loading AutoRest extension '#microsoft.azure/autorest.modeler' (2.3.55->2.3.55)
FATAL: swagger-document-override/md-override-loader - FAILED
FATAL: Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
FATAL: swagger-document/loader - FAILED
FATAL: Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
Process() cancelled due to exception : Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
After studying the issue on github I tried starting the api using dotnet run
but it did not help.
I tried running autorest in a dos command shell with admin priviledge
As per the github issue I can save the swagger.json to a file and generate the code by referencing the file.
That isn't a great solution.
Are you attempting to use https with localhost ? If you haven't put a certificate on there, you shouldn't be using https.
Try it with http://localhost...