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
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.
I am trying to run SonarQube for my Xamarin Forms project, I am on the path where my .SLN file is there and executing the following command
Command:
$ mono /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/MSBuild.SonarQube.Runner.exe begin /k:"HIDReaderManagerApp" /d:sonar.host.url="http://localhost:9000" /d:sonar.login="My Login Token"
Error:
SonarQube Scanner for MSBuild 4.0.2
Default properties file was found at /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/SonarQube.Analysis.xml
Loading analysis properties from /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/SonarQube.Analysis.xml
Pre-processing started.
Preparing working directories...
17:29:10.391 Updating build integration targets...
17:29:10.414 Fetching analysis configuration settings...
17:29:10.517 Failed to request and parse 'http://localhost:9000/api/settings/values?component=HIDReaderManagerApp': The remote server returned an error: (401) .
17:29:10.517 Could not authorize while connecting to the SonarQube server. Check your credentials and try again.
17:29:10.518 Pre-processing failed. Exit code: 1
The api/settings/values API requires Browse permission when the component argument is used. Please, see if the user you are authenticating with has the aforementioned permission.
More details about security and permissions here:
https://docs.sonarqube.org/latest/instance-administration/security
I have a cloud service on Windows Azure, I created a Asp.net WebAPI project and published to the cloud service, that was working fine from Visual Studio to publish before i updated visual studio to update 4 and azure SDK 2.2 to 2.6. But after updating when I publish, I got the following error messages. I tried several times, all failed. Can anyone help me?
even i am not able to publish a new created project on new azure service !
11:00:31 PM - Warning: There are package validation warnings.
11:00:31 PM - Checking for Remote Desktop certificate...
11:00:39 PM - Preparing deployment for TempAzure - 2/12/2014 10:58:23
PM with Subscription ID 'e94e9aeb-7003-4eae-be92-7b7ac0a1ba2c' using
Service Management URL 'https://management.core.windows.net/'...
11:00:39 PM - Connecting...
11:00:39 PM - Verifying storage account 'jasontest'...
11:00:41 PM - Uploading Package...
11:06:48 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:11:50 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:26:16 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:00:27 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:05:05 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:27:54 AM - Unable to write data to the transport connection: An
existing connection was forcibly closed by the remote host.
After updating from Azure SDK2.5 to SDK 2.6, I had the same problem when trying publish to my Azure service from VS2013: Any deployment effort using Visual Studio fails after some minutes with 500 Internal server error.
As I found the reason is the very slow upload of the Azure package to the cloud - sometimes only between 30kB/s and 50kB/s. The deployment fails because of an timeout which also explains, that the Azure instance logs show no sign of any deployment...
Work around: Deploy from Azure storage
1: Package the Azure solution, either via VisualStudio or via command line:
MSBuild /t:Publish /p:TargetProfile=Cloud /P:Configuration=Release
2: Create an Azure storage container to upload your package to.
Continue using AzurePowerShell cmdlets:
3: Login
Add-AzureAccount
4: Upload the package to the your Azure storage container
$Ctx = New-AzureStorageContext -StorageAccountName "yourstoragename" -StorageAccountKey "yourkey"
Set-AzureStorageBlobContent -File "...\app.publish\yourservice.cspkg" -Container "yourazurestoragecontainer" -Blob "yourservice.cspkg" -Context $Ctx -Force
Determine the PackageURL of the uploaded package.
5: Deploy the cloud service referring to the package just uploaded to Azure cloud storage.
Set-AzureDeployment -Upgrade -Slot "Staging" -Package "PackageURL" -Configuration "PathToYourCloudConfiguration.cscfg" -label "SomeDeploymentInfo" -ServiceName "yourservicename" -Force
(Of course the entire process is scriptable. Kemp Brown wrote a great article: with a script you could adapt to explictly upload the package:
Continuous Delivery for Cloud Services in Azure)
Actually the problem was my network connection.
to identify this problem i created VM on azure with same windows 8.1 OS and same VS. i tried to deploy from there. deployment worked fine. latter I disconnected all other devices from my internet connection and i tried to publish from my machine. it worked !
so conclusion is slow internet connection or may be now we have less timeout time for publish from VS !
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
An application which developed with EJB, ADFFaces on JDeveloper 11.1.2.4 ide. Could be deployed on server at last, but many error lines out about .xsd files. How can i solve that issue?
brgds
...
File: file:/C:/glassfish3/glassfish/domains/domain1/generated/jsp/RestaurantAuto
mation/RestaurantAutomation_RestAutomationVC_webapp1_war/loader_962515257/oracle
/adfdt/model/dvt/schema/binding/gauge.xsd
[Error]: Line -1, Column -1: Invalid reference: ':ledStyleEnum'
[#|2013-11-08T17:27:25.647+0200|INFO|glassfish3.1.2|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=18;_ThreadName=admin-thread-pool-4848
(3);|WEB0671: Loading application [RestaurantAutomation#RestaurantAutomation_Res
tAutomationVC_webapp1.war] at [RestAutomation]|#]
[#|2013-11-08T17:27:26.068+0200|INFO|glassfish3.1.2|javax.enterprise.system.tool
s.admin.org.glassfish.deployment.admin|_ThreadID=18;_ThreadName=admin-thread-poo
l-4848(3);|RestaurantAutomation was successfully deployed in 75,528 milliseconds
.|#]