You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/spring-cloud/how-to-enterprise-build-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ In Azure Spring Cloud, the existing Standard tier already supports compiling use
22
22
23
23
Tanzu Build Service in the Enterprise tier is the entry point to containerize user applications from both source code and artifacts. There's a dedicated build agent pool that reserves compute resources for a given number of concurrent build tasks. The build agent pool prevents resource contention with your running apps. You can configure the number of resources given to the build agent pool during or after creating a new service instance of Azure Spring Cloud using the **VMware Tanzu settings**.
24
24
25
-
:::image type="content" source="media/enterprise/how-to-enterprise-build-service/agent-pool.png" alt-text="Azure portal screenshot showing Azure Spring Cloud Create page with 'VMWare Tanzu settings' highlighted and 'Allocated Resources' dropdown showing.":::
25
+
:::image type="content" source="media/enterprise/how-to-enterprise-build-service/agent-pool.png" alt-text="Azure portal screenshot showing Azure Spring Cloud Create page with 'VMware Tanzu settings' highlighted and 'Allocated Resources' dropdown showing.":::
26
26
27
27
The Build Agent Pool scale set sizes available are:
Copy file name to clipboardExpand all lines: articles/spring-cloud/troubleshoot.md
+58-55Lines changed: 58 additions & 55 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,7 @@ This article provides instructions for troubleshooting Azure Spring Cloud develo
21
21
22
22
Export the logs to Azure Log Analytics. The table for Spring application logs is named *AppPlatformLogsforSpring*. To learn more, see [Analyze logs and metrics with diagnostics settings](diagnostic-services.md).
23
23
24
-
The following error message might appear in your logs:
25
-
26
-
> "org.springframework.context.ApplicationContextException: Unable to start web server"
24
+
The following error message might appear in your logs: `org.springframework.context.ApplicationContextException: Unable to start web server`
27
25
28
26
The message indicates one of two likely problems:
29
27
@@ -38,23 +36,23 @@ To fix this error, go to the `server parameters` of your MySQL instance, and cha
38
36
39
37
### My application crashes or throws an unexpected error
40
38
41
-
When you're debugging application crashes, start by checking the running status and discovery status of the application. To do so, go to _App management_ in the Azure portal to ensure that the statuses of all the applications are _Running_ and _UP_.
39
+
When you're debugging application crashes, start by checking the running status and discovery status of the application. To do so, go to *App management* in the Azure portal to ensure that the statuses of all the applications are *Running* and *UP*.
42
40
43
-
* If the status is _Running_ but the discovery status is not _UP_, go to the ["My application can't be registered"](#my-application-cant-be-registered) section.
41
+
* If the status is *Running* but the discovery status is not *UP*, go to the ["My application can't be registered"](#my-application-cant-be-registered) section.
44
42
45
-
* If the discovery status is _UP_, go to Metrics to check the application's health. Inspect the following metrics:
43
+
* If the discovery status is *UP*, go to Metrics to check the application's health. Inspect the following metrics:
46
44
47
-
-`TomcatErrorCount` (_tomcat.global.error_):
45
+
*`TomcatErrorCount` (*tomcat.global.error*):
48
46
49
-
All Spring application exceptions are counted here. If this number is large, go to Azure Log Analytics to inspect your application logs.
47
+
All Spring application exceptions are counted here. If this number is large, go to Azure Log Analytics to inspect your application logs.
50
48
51
-
-`AppMemoryMax` (_jvm.memory.max_):
49
+
*`AppMemoryMax` (*jvm.memory.max*):
52
50
53
-
The maximum amount of memory available to the application. The amount might be undefined, or it might change over time if it is defined. If it's defined, the amount of used and committed memory is always less than or equal to max. However, a memory allocation might fail with an `OutOfMemoryError` message if the allocation attempts to increase the used memory such that *used > committed*, even if *used <= max* is still true. In such a situation, try to increase the maximum heap size by using the `-Xmx` parameter.
51
+
The maximum amount of memory available to the application. The amount might be undefined, or it might change over time if it is defined. If it's defined, the amount of used and committed memory is always less than or equal to max. However, a memory allocation might fail with an `OutOfMemoryError` message if the allocation attempts to increase the used memory such that *used > committed*, even if *used <= max* is still true. In such a situation, try to increase the maximum heap size by using the `-Xmx` parameter.
54
52
55
-
-`AppMemoryUsed` (_jvm.memory.used_):
53
+
*`AppMemoryUsed` (*jvm.memory.used*):
56
54
57
-
The amount of memory in bytes that's currently used by the application. For a normal load Java application, this metric series forms a *sawtooth* pattern, where the memory usage steadily increases and decreases in small increments and suddenly drops a lot, and then the pattern recurs. This metric series occurs because of garbage collection inside Java virtual machine, where collection actions represent drops on the sawtooth pattern.
55
+
The amount of memory in bytes that's currently used by the application. For a normal load Java application, this metric series forms a *sawtooth* pattern, where the memory usage steadily increases and decreases in small increments and suddenly drops a lot, and then the pattern recurs. This metric series occurs because of garbage collection inside Java virtual machine, where collection actions represent drops on the sawtooth pattern.
58
56
59
57
This metric is important to help identify memory issues, such as:
60
58
@@ -102,8 +100,8 @@ Before you onboard your application, ensure that it meets the following criteria
102
100
* The configuration items have their expected values. For more information, see [Set up a Spring Cloud Config Server instance for your service](./how-to-config-server.md). For enterprise tier, see [Use Application Configuration Service](./how-to-enterprise-application-configuration-service.md).
103
101
* The environment variables have their expected values.
104
102
* The JVM parameters have their expected values.
105
-
* We recommended that you disable or remove the embedded _Config Server_ and _Spring Service Registry_ services from the application package.
106
-
* If any Azure resources are to be bound via _Service Binding_, make sure the target resources are up and running.
103
+
* We recommended that you disable or remove the embedded *Config Server* and *Spring Service Registry* services from the application package.
104
+
* If any Azure resources are to be bound via *Service Binding*, make sure the target resources are up and running.
107
105
108
106
## Configuration and management
109
107
@@ -138,11 +136,11 @@ When you deploy your application package by using the [Azure CLI](/cli/azure/get
138
136
139
137
If the polling is interrupted, you can still use the following command to fetch the deployment logs:
Ensure that your application is packaged in the correct [executable JAR format](https://docs.spring.io/spring-boot/docs/current/reference/html/executable-jar.html). If it isn't packaged correctly, you will receive an error message similar to the following:
139
+
```azurecli
140
+
az spring-cloud app show-deploy-log --name <app-name>
141
+
```
144
142
145
-
> "Error: Invalid or corrupt jarfile /jar/38bc8ea1-a6bb-4736-8e93-e8f3b52c8714"
143
+
Ensure that your application is packaged in the correct [executable JAR format](https://docs.spring.io/spring-boot/docs/current/reference/html/executable-jar.html). If it isn't packaged correctly, you will receive an error message similar to the following: `Error: Invalid or corrupt jarfile /jar/38bc8ea1-a6bb-4736-8e93-e8f3b52c8714`
146
144
147
145
### I can't deploy a source package
148
146
@@ -152,7 +150,9 @@ When you deploy your application package by using the [Azure CLI](/cli/azure/get
152
150
153
151
If the polling is interrupted, you can still use the following command to fetch the build and deployment logs:
az spring-cloud app show-deploy-log --name <app-name>
155
+
```
156
156
157
157
However, note that one Azure Spring Cloud service instance can trigger only one build job for one source package at one time. For more information, see [Deploy an application](./quickstart.md) and [Set up a staging environment in Azure Spring Cloud](./how-to-staging-environment.md).
158
158
@@ -162,9 +162,9 @@ In most cases, this situation occurs when *Required Dependencies* and *Service D
162
162
163
163
Wait at least two minutes before a newly registered instance starts receiving traffic.
164
164
165
-
If you're migrating an existing Spring Cloud-based solution to Azure, ensure that your ad-hoc _Service Registry_ and _Config Server_ instances are removed (or disabled) to avoid conflicting with the managed instances provided by Azure Spring Cloud.
165
+
If you're migrating an existing Spring Cloud-based solution to Azure, ensure that your ad-hoc *Service Registry* and *Config Server* instances are removed (or disabled) to avoid conflicting with the managed instances provided by Azure Spring Cloud.
166
166
167
-
You can also check the _Service Registry_ client logs in Azure Log Analytics. For more information, see [Analyze logs and metrics with diagnostics settings](diagnostic-services.md)
167
+
You can also check the *Service Registry* client logs in Azure Log Analytics. For more information, see [Analyze logs and metrics with diagnostics settings](diagnostic-services.md)
168
168
169
169
To learn more about Azure Log Analytics, see [Get started with Log Analytics in Azure Monitor](../azure-monitor/logs/log-analytics-tutorial.md). Query the logs by using the [Kusto query language](/azure/kusto/query/).
170
170
@@ -177,35 +177,35 @@ Environment variables inform the Azure Spring Cloud framework, ensuring that Azu
177
177
178
178
1. Go to `https://<your application test endpoint>/actuator/health`.
179
179
180
-
- A response similar to `{"status":"UP"}` indicates that the endpoint has been enabled.
181
-
- If the response is negative, include the following dependency in your *POM.xml* file:
180
+
* A response similar to `{"status":"UP"}` indicates that the endpoint has been enabled.
181
+
* If the response is negative, include the following dependency in your *POM.xml* file:
1. With the Spring Boot Actuator endpoint enabled, go to the Azure portal and look for the configuration page of your application. Add an environment variable with the name `MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE` and the value `*`.
191
191
192
192
1. Restart your application.
193
193
194
194
1. Go to `https://<your application test endpoint>/actuator/env` and inspect the response. It should look like this:
195
195
196
-
```json
197
-
{
198
-
"activeProfiles": [],
199
-
"propertySources": {,
200
-
"name": "server.ports",
201
-
"properties": {
202
-
"local.server.port": {
203
-
"value": 1025
204
-
}
205
-
}
206
-
}
207
-
}
208
-
```
196
+
```json
197
+
{
198
+
"activeProfiles": [],
199
+
"propertySources": {,
200
+
"name": "server.ports",
201
+
"properties": {
202
+
"local.server.port": {
203
+
"value": 1025
204
+
}
205
+
}
206
+
}
207
+
}
208
+
```
209
209
210
210
Look for the child node named `systemEnvironment`. This node contains your application's environment variables.
211
211
@@ -214,9 +214,9 @@ Look for the child node named `systemEnvironment`. This node contains your appl
214
214
215
215
### I can't find metrics or logs for my application
216
216
217
-
Go to **App management** to ensure that the application statuses are _Running_ and _UP_.
217
+
Go to **App management** to ensure that the application statuses are *Running* and *UP*.
218
218
219
-
Check to see whether _JMX_ is enabled in your application package. This feature can be enabled with the configuration property `spring.jmx.enabled=true`.
219
+
Check to see whether *JMX* is enabled in your application package. This feature can be enabled with the configuration property `spring.jmx.enabled=true`.
220
220
221
221
Check to see whether the `spring-boot-actuator` dependency is enabled in your application package and that it successfully boots up.
222
222
@@ -229,33 +229,37 @@ Check to see whether the `spring-boot-actuator` dependency is enabled in your ap
229
229
230
230
If your application logs can be archived to a storage account but not sent to Azure Log Analytics, check to see whether you [set up your workspace correctly](../azure-monitor/logs/quick-create-workspace.md). If you're using a free tier of Azure Log Analytics, note that [the free tier does not provide a service-level agreement (SLA)](https://azure.microsoft.com/support/legal/sla/log-analytics/v1_3/).
231
231
232
-
## Enterprise Tier
232
+
## Enterprise tier
233
233
234
234
### Error 112039: Failed to purchase on Azure Marketplace
235
235
236
236
Creating an Azure Spring Cloud Enterprise tier instance fails with error code "112039". Check the detailed error message for below for more information:
237
237
238
-
-**"Failed to purchase on Azure Marketplace because the Microsoft.SaaS RP is not registered on the Azure subscription."** : Azure Spring Cloud Enterprise tier purchase a SaaS offer from VMWare.
238
+
***"Failed to purchase on Azure Marketplace because the Microsoft.SaaS RP is not registered on the Azure subscription."** : Azure Spring Cloud Enterprise tier purchase a SaaS offer from VMware.
239
239
240
240
You must register the Microsoft.SaaS resource provider before creating Azure Spring Cloud Enterprise instance. See how to [register a resource provider](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider).
241
241
242
-
-**"Failed to load catalog product vmware-inc.azure-spring-cloud-vmware-tanzu-2 in the Azure subscription market."**: Your Azure subscription's billing account address is not in the supported location.
242
+
***"Failed to load catalog product vmware-inc.azure-spring-cloud-vmware-tanzu-2 in the Azure subscription market."**: Your Azure subscription's billing account address is not in the supported location.
243
243
244
244
For more information, see the section [No plans are available for market '\<Location>'](#no-plans-are-available-for-market-location).
245
245
246
-
-**"Failed to purchase on Azure Marketplace due to signature verification on Marketplace legal agreement. Check the Azure subcription has agree terms vmware-inc.azure-spring-cloud-vmware-tanzu-2.tanzu-asc-ent-mtr"**: Your Azure subscription has not signed the terms for the offer and plan to be purchased.
246
+
***"Failed to purchase on Azure Marketplace due to signature verification on Marketplace legal agreement. Check the Azure subscription has agree terms vmware-inc.azure-spring-cloud-vmware-tanzu-2.tanzu-asc-ent-mtr"**: Your Azure subscription has not signed the terms for the offer and plan to be purchased.
247
247
248
248
Go to your Azure subscription and run the following Azure CLI command to agree to the terms:
249
+
249
250
```azurecli
250
-
az term accept --publisher vmware-inc --product azure-spring-cloud-vmware-tanzu-2 --plan tanzu-asc-ent-mtr
251
+
az term accept \
252
+
--publisher vmware-inc \
253
+
--product azure-spring-cloud-vmware-tanzu-2 \
254
+
--plan tanzu-asc-ent-mtr
251
255
```
252
256
253
257
If that doesn't help, you can contact the support team with the following info.
254
258
255
-
-`AZURE_TENANT_ID`: the Azure tenant ID that hosts the Azure subscription
256
-
-`AZURE_SUBSCRIPTION_ID`: the Azure subscription ID used to create the Spring Cloud instance
257
-
-`SPRING_CLOUD_NAME`: the failed instance name
258
-
-`ERROR_MESSAGE`: the observed error message
259
+
*`AZURE_TENANT_ID`: the Azure tenant ID that hosts the Azure subscription
260
+
*`AZURE_SUBSCRIPTION_ID`: the Azure subscription ID used to create the Spring Cloud instance
261
+
*`SPRING_CLOUD_NAME`: the failed instance name
262
+
*`ERROR_MESSAGE`: the observed error message
259
263
260
264
### No plans are available for market '\<Location>'
261
265
@@ -269,8 +273,7 @@ Azure Spring Cloud Enterprise tier needs customers to pay for a license to Tanzu
269
273
270
274
You can view the billing account for your subscription if you have admin access. See [view billing accounts](../cost-management-billing/manage/view-all-accounts.md#check-the-type-of-your-account).
271
275
272
-
273
-
### I need VMware Spring Runtime Support (Enterprise Tier only)
276
+
### I need VMware Spring Runtime Support (Enterprise tier only)
274
277
275
278
Enterprise tier has built-in VMware Spring Runtime Support so you can directly open support tickets to [VMware](https://aka.ms/ascevsrsupport) if you think your issue is in scope of VMware Spring Runtime Support. For more information, see [https://tanzu.vmware.com/spring-runtime](https://tanzu.vmware.com/spring-runtime). For any other issues, directly open support tickets with Microsoft.
0 commit comments