Error While Running Pre-Registration Application Service

Developer
9

Hi @Veera_Ragavan ,

Thank you for sharing the details of your issue. Here’s what I noticed based on your logs :

  • The Pre-Registration Application Service is trying to connect to external modules such as Masterdata, Authentication, IAM, and Configuration, but these attempts result in failed connections or timeouts. This is because the URLs currently used in your setup (e.g., pointing to dev.mosip.net or localhost) are either inaccessible or incorrect for your setup.

Why This Happens:

  • The issue occurs because the Pre-Registration Application Service depends on external modules (e.g., Masterdata, Authentication, IAM, Configuration) to function properly. Running the application locally without access to these services leads to startup failures—this is expected behavior.
  • These necessary services are part of the MOSIP ecosystem and must be accessible for the Pre-Registration application to function as intended.

What You Can Do :

  1. If You’re Running the Application Locally :
  • Ensure you have access to the required services (Masterdata, Authentication, etc.), which are typically part of the full MOSIP setup.
  • Refer to the Deployment Getting Started Documentation for guidance on setting up the MOSIP ecosystem.
  1. For Exploring the Application (Demo Mode) :
  • If your goal is to test how the application works, we recommend using the pre-deployed Demo Environment at collab.mosip.net.
  • This environment is fully configured with all necessary services, allowing you to explore the application as intended without needing to set up your MOSIP ecosystem.
  • Refer to the Collab Pre-Registration Guide for instructions on accessing and using this environment.
  1. For Exploring the Code :
  • If your objective is to understand the service or review the code structure :
    • Clone the Pre-Registration application’s codebase.
    • Build it locally to explore the logic and structure.
  • However, running the application locally requires access to an environment where these dependent services are hosted and accessible.
    • If you have access to such an environment, update the application.properties file with the relevant service URLs (e.g., spring.cloud.config.uri and mosip.base.url).

Without access to these services, the application will fail to start successfully.

Let me know if this helps or if you need further clarification.

Best regards,
Team MOSIP