Purpose (problem description)
This page provides assistance when receiving the error message 'Connection Exception: 400 - Bad Request' when packaging an HTTP Maven Repository. The error can be seen in the screenshot of the package extraction log as shown below:
Figure 1
For assistance with finding logs, please see the page: CAST Management Studio - Information - How to find logs
For assistance with the HTTP Maven Repository extension, please see the page: JEE Maven Http Extractor
Observed in CAST AIP
Release | Yes/No |
---|---|
8.3.x | |
8.2.x | |
8.1.x | |
8.0.x |
Observed on RDBMS
RDBMS | Yes/No |
---|---|
Oracle Server | |
Microsoft SQL Server | |
CSS2 |
Step by Step scenario
- Use DMT to package a Maven http repository
- Encountered error in log during packaging
Action Plan
Perform the below actions
- This issue is due to the fact that some variables are defined in the dependencies and have no values. This issue can be ignored as it has no impact in this case. You can do the following to resolve:
- Provide a value to the variable as a remediation. See the following documentation for further details on this: Remediating items in DMT
- Run the packaging again.
- Provide a value to the variable as a remediation. See the following documentation for further details on this: Remediating items in DMT
- The best solution is to upgrade the HTTP Maven Repository extension to version 1.3.0 or higher which resolves this issue.
- If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input
Relevant input
- The entire contents of the delivery folder as defined in CAST-MS: CMS - Preferences - Platform Settings
- A detailed list of the steps done
- Screenshots from DMT showing the issue
Notes/comments
Ticket #10101
Related Pages