Bug 1079867
| Summary: | Getting error [JBWEB000065: HTTP Status 500 - mark/reset not supported] when trying to upload artifact without a valid pom.xml | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Hao Wu <hwu> | ||||
| Component: | Business Central | Assignee: | manstis | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Livora <tlivora> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.0 | CC: | hwu, kverlaen | ||||
| Target Milestone: | ER1 | ||||||
| Target Release: | 6.0.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Mac OS | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 19:50:56 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Hi Hao, would it be possible to attach the jar you have used? I'm sure it will help engineering to faster reproduce the issue and QE to verify it. Thank you. Regards! Marek Can you please confirm this is on Tomcat (and the version)? Michael Anstis <michael.anstis> updated the status of jira GUVNOR-2084 to Resolved Verified on BPMS 6.0.2 ER1 |
Created attachment 877949 [details] Full stack trace Description of problem: When I tried to add an artifact without a valid pom.xml file into the repository, I get the following error: JBWEB000065: HTTP Status 500 - mark/reset not supported Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. In Business Central, go to Authoring->Artifact repository. 2. Click Upload and choose a .jar file with a pom.xml and click the Upload button. 3. An error message states that the GAV information must be inputted manually. 4. Fill in the GroupID, ArtifactID, and VersionID and click Upload again. 5. An error occurs. Actual results: An error occurs. Expected results: The jar file is uploaded to the repository. Additional info: