SpringBoot创建MQConnectionFactory时遇EL1008e属性找不到异常求助

Let’s walk through why you’re hitting these EL1008E exceptions and how to resolve them step by step.

What’s Causing the Error? #

The exceptions EL1008E: Property or field 'queueManagerName' cannot be found and EL1008E: Property or field 'queueManager' cannot be found mean Spring’s SpEL (Spring Expression Language) is trying to access a property that doesn’t exist in the current Bean Expression Context. This almost always boils down to one of a few common issues: incorrect SpEL syntax, mismatched configuration property names, or missing property injection.

Common Fixes #

1. Mixing Up #{} and ${} Syntax

SpEL has two key syntaxes, and using the wrong one is a frequent culprit:

• ${property.name}: Used to reference external configuration properties (from application.properties/application.yml).
• #{beanName.property}: Used to reference properties of beans already registered in the Spring context.

If you’re trying to pull a value from your config file but used #{} instead of ${}, Spring will look for a bean or context variable with that name (which doesn’t exist).

Wrong Example:

@Bean
public MQConnectionFactory mqConnectionFactory() {
    MQConnectionFactory factory = new MQConnectionFactory();
    // This tries to find a context property named "queueManagerName" (not a config value)
    factory.setQueueManagerName("#{queueManagerName}");
    return factory;
}

Correct Example:
Use @Value to inject the config property, then assign it:

@Value("${mq.queue-manager-name}") // Matches your config file key
private String queueManagerName;

@Bean
public MQConnectionFactory mqConnectionFactory() {
    MQConnectionFactory factory = new MQConnectionFactory();
    factory.setQueueManagerName(queueManagerName);
    return factory;
}

Or inject directly into the @Bean method parameter:

@Bean
public MQConnectionFactory mqConnectionFactory(
    @Value("${mq.queue-manager-name}") String queueManagerName
) {
    MQConnectionFactory factory = new MQConnectionFactory();
    factory.setQueueManagerName(queueManagerName);
    return factory;
}

2. Mismatched Config Property Names

Double-check that the property name in your code exactly matches what’s in your application.properties/application.yml (Spring Boot does auto-convert hyphens to camelCase, but typos still happen).

Example Config (application.yml):

mq:
  queue-manager-name: MY_QUEUE_MANAGER

Make sure your @Value annotation uses either ${mq.queue-manager-name} or ${mq.queueManagerName} (both work due to Spring’s hyphen-to-camelCase mapping). If you wrote ${queueManagerName} without the mq. prefix, Spring won’t find the property.

3. Issues with @ConfigurationProperties (If Used)

If you’re using @ConfigurationProperties to bind config values to a class, ensure the class properties match your config keys:

Wrong Example:

@ConfigurationProperties(prefix = "mq")
public class MQConfigProps {
    private String queueManager; // Doesn't match "queue-manager-name" in config
    // Getters/Setters
}

Fix:
Either rename the config key to mq.queue-manager, or update the class property and optionally use @JsonProperty to map explicitly:

@ConfigurationProperties(prefix = "mq")
public class MQConfigProps {
    @JsonProperty("queue-manager-name")
    private String queueManagerName;
    // Getters/Setters
}

Then inject this props class into your @Bean method:

@Bean
public MQConnectionFactory mqConnectionFactory(MQConfigProps mqProps) {
    MQConnectionFactory factory = new MQConnectionFactory();
    factory.setQueueManagerName(mqProps.getQueueManagerName());
    return factory;
}

4. Verify Config File Location and Activation

Ensure your application.properties/application.yml is in the correct location (src/main/resources for standard Spring Boot projects) and that you’re activating the right profile if using multi-environment configs (e.g., spring.profiles.active=dev in your main config).

Final Check #

After making these changes, rebuild your project and restart the Spring Boot app. The SpEL errors should disappear once Spring can correctly resolve the queueManagerName/queueManager property from your config or context.

内容的提问来源于stack exchange，提问作者Prashant Pandey