Alcatel Adapter fails to connect via JMS to NSP with NoClassDefFoundError
search cancel

Alcatel Adapter fails to connect via JMS to NSP with NoClassDefFoundError

book

Article ID: 447414

calendar_today

Updated On:

Products

VMware Smart Assurance Network Observability

Issue/Introduction

The Alcatel (SAM5620) Adapter fails to connect to the Network Services Platform (NSP) via JMS post upgrade.
The adapter logs show continuous reconnection attempts followed by severe exceptions.

The following errors are captured in the logs:

[Date & Time] t@<epoch> ASAM_MESSAGE-*-INFO-.[Connector] CleanUpJmsResources called.
[Date & Time] t@<epoch> ASAM_MESSAGE-*-INFO-.[Connector] Stopping JMS monitor
[Date & Time] t@<epoch> ASAM_MESSAGE-*-INFO-.[Connector] topicConnection closed.
[Date & Time] t@<epoch> ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.
[Date & Time] t@<epoch> ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:java.lang.NoClassDefFoundError
Could not initialize class org.wildfly.security.auth.client.AuthenticationConfiguration
    org.wildfly.naming.client.ProviderEnvironment$Builder.populateFromEnvironment(ProviderEnvironment.java:329)
    org.wildfly.naming.client.WildFlyRootContext.(WildFlyRootContext.java:114)
    org.wildfly.naming.client.WildFlyRootContext.(WildFlyRootContext.java:89)
    org.wildfly.naming.client.WildFlyRootContext.(WildFlyRootContext.java:79)
    org.wildfly.naming.client.WildFlyInitialContextFactory.getInitialContext(WildFlyInitialContextFactory.java:55)
    org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContextFactory.java:247)
    java.naming/javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    java.naming/javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    java.naming/javax.naming.InitialContext.init(Unknown Source)
    java.naming/javax.naming.InitialContext.(Unknown Source)
    com.smarts.asac.SmAsAlarmEmsInterface.buildInitialContext(SmAsAlarmEmsInterface.java:900)
    com.smarts.asac.SmAsAlarmEmsInterface.buildInitialContext(SmAsAlarmEmsInterface.java:869)
    com.smarts.asac.SmAsAlarmEmsInterface.jmsConnect(SmAsAlarmEmsInterface.java:423)
    com.smarts.asac.Connector.run(SmAsAlarmEmsInterface.java:1476)

[Date & Time] t@<epoch> ASAM_MESSAGE-*-SEVERE-.[Connector] -- Initial Cause of exception follows ---
[Date & Time] t@<epoch> ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:java.lang.ExceptionInInitializerError
Exception java.lang.ExceptionInInitializerError [in thread "Connector"]
    org.wildfly.security.auth.client.AuthenticationConfiguration.(AuthenticationConfiguration.java:166)
    ...

[Date & Time] t@<epoch> ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:org.wildfly.naming.client.ExhaustedDestinationsException
WFNAM00055: No more destinations are available to attempt the operation (2 blocklisted, 0 transiently failed). See suppressed exceptions for details
    org.wildfly.naming.client.NamingProvider.getPeerIdentityForNamingUsingRetry(NamingProvider.java:94)
    org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNamingUsingRetry(RemoteNamingProvider.java:91)
    org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:206)

Environment

All Supported Smarts releases

Cause

  1. Java Compatibility: The samOss.jar (e.g., version NFMP-23.11) running on Java 1.8 exhibits compatibility issues with WildFly security classes used in newer environments. Later releases are shipped with Java 17, which does not exhibit this behavior.
  2. Network Connectivity: Connection failures from the ASAM server to the EMS and JMS often due to firewall restrictions or incorrect configuration.
    Reference about these configuration parameters is available at: emsConfig.import Parameters

Resolution

Verify Port Connectivity

Confirm that the ASAM server can communicate with the EMS and JMS over the required ports.

Test connectivity using the following command:

curl -v telnet://#.#.#.#:8080

Ensure the following ports are open in the firewall:

  • 8080 (HTTP/Configuration)
  • 8443 (HTTPS)
  • JMS Port (as per environment configuration)

Software Alignment

For a permanent fix, ensure that the adapter and associated libraries (like samOss.jar) are updated to versions compatible with Java 17, as current releases are optimized for that environment.

Powered by Wolken Software