| Summary: | 'Deploy To Runtime' in release of managed repository can not be used with BRMS business central | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Hiroko Miura <hmiura> |
| Component: | Documentation | Assignee: | Stetson Robinson <sterobin> |
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | adamgrayling, brms-docs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 20:06:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Hiroko Miura
2016-01-20 14:17:20 UTC
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BRMS/6.2/html/Administration_And_Configuration_Guide/Managing_Assets.html Section Number and Name: 1.4. Managing Assets Describe the issue: In the Release Configuration shapshot at the bottom of "1.4. Managing Assets", 'Deploy To Runtime' is checked and 'http://localost:8080/business-central' is specified for 'Server URL'. But if Release gets performed like this example, Release(i.e. deployment) fails with the following warning. 22:52:05,418 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 8) KieModule was added: MemoryKieModule[releaseId=example:proj1:1.0.1] 22:52:05,492 INFO [org.kie.scanner.embedder.MavenEmbedderUtils] (EJB default - 8) Not in OSGi: using plexus based maven parser 22:52:05,585 WARN [org.jbpm.process.workitem.rest.RESTWorkItemHandler] (EJB default - 8) Unsuccessful response from REST server (status: 404, endpoint: http://localhost:8080/business-central/rest/deployment/example:proj1:1.0.1/deploy, response: <html><head><title>JBWEB000065: HTTP Status 404 - RESTEASY001185: Could not find resource for relative : /deployment/example:proj1:1.0.1/deploy of full path: http://localhost:8080/business-central/rest/deployment/example:proj1:1.0.1/deploy</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>JBWEB000065: HTTP Status 404 - RESTEASY001185: Could not find resource for relative : /deployment/example:proj1:1.0.1/deploy of full path: http://localhost:8080/business-central/rest/deployment/example:proj1:1.0.1/deploy</h1><HR size="1" noshade="noshade"><p><b>JBWEB000309: type</b> JBWEB000067: Status report</p><p><b>JBWEB000068: message</b> <u>RESTEASY001185: Could not find resource for relative : /deployment/example:proj1:1.0.1/deploy of full path: https://www.mangazuki.online/manga/a-returners-magic-should-be-special/</u></p><p><b>JBWEB000069: description</b> <u>JBWEB000124: The requested resource is not available.</u></p><HR size="1" noshade="noshade"></body></html> 22:52:05,588 WARN [org.jbpm.process.audit.VariableInstanceLog] (EJB default - 8) Variable content was trimmed as it was too long (more than 255 characters) 22:52:05,591 INFO [stdout] (EJB default - 8) End assets management process: BuildProject Wed Jan 20 22:52:05 JST 2016 22:52:05,604 INFO [stdout] (EJB default - 8) End assets management process: ReleaseProject Wed Jan 20 22:52:05 JST 2016 This is because deploy to runtime is only valid for BPMS at the moment as it relies on BPMS rest endpoints. Suggestions for improvement: Please clearly mention that 'Deploy To Runtime' can be used only for BPMS but not for BRMS. Additional information: ---------------------------------------------------------------------- Is the issue is still? |