|
Scan2x Online New Web Client - Real Time Messaging Troubleshooting
Real-time messaging in the Scan2x Online new web client depends on the correct functioning of the local Kafka infrastructure deployed through Scan2x Win. This document provides a structured troubleshooting procedure to diagnose and resolve issues related to real-time message delivery.
Prerequisites:
- Administrative access to the Windows machine
- Access to services.msc
- File Explorer access to C:\tmp\Logs and C:\Program Files(x86)\Scan2x\Setup.
- Permissions to modify system environment variables.
Diagnostic Procedure
ØVerify KafkaServiceManager Installation and Status
1. Open Services by running services.msc.
2. Locate KafkaServiceManager in the list of services.
3. Confirm:
- The service exists.
- The Startup Type is Automatic (Delayed Start).
- The Status is Running.
4. If the service is stopped, attempt to start it and observe for failures.
ØConfirm Java 25 Installation
1. Open Installed Apps.
2. Ensure Java JDK 25 is present.
3. If missing, install Java 25 before proceeding.
ØValidate JAVA_HOME and PATH System Variables
1. Open System Properties → Advanced → Environment Variables.
2. Ensure JAVA_HOME is set to: C:\Program Files\Java\jdk-25
3. Ensure PATH includes: C:\Program Files\Java\jdk-25\bin
4. Correct any discrepancies and restart KafkaServiceManager.
ØCheck Required Ports (9092 and 2181)
Kafka requires port 9092, and Zookeeper requires port 2181.
1. Open an elevated Command Prompt.
2. Run:
netstat -ano | findstr 9092
netstat -ano | findstr 2181
3. Confirm that:
- Port 9092 is used by the Kafka process.
- Port 2181 is used by the Zookeeper process.
4. If another process is using these ports, Kafka or Zookeeper may fail to start.
ØConfirm Correct CMD Process State
1. Ensure no visible cmd.exe windows are open.
2. Open Task Manager → Details.
3. Verify one background cmd.exe process associated with Kafka.
4. If none exists, restart KafkaServiceManager.
5. Close additional unrelated cmd.exe instances if safe.
ØReview KafkaServiceManager Logs#
1. Navigate to C:\tmp\Logs.
2. Locate today's log file, typically named KafkaServiceManager-YYYYMMDD.
3. Review for startup failures, missing file errors, or Java path issues.
ØManually Start Kafka and Zookeeper for Diagnostics
This step helps identify detailed startup errors.
1. Stop KafkaServiceManager via services.msc.
2. Open an elevated Command Prompt.
3. Then start Zookeeper manually:
C:\kafka\bin\windows\zookeeper-server-start.bat
C:\kafka\config\zookeeper.properties
4. Observe any errors displayed. If Zookeeper does not start, Kafka will not be able
to run.
5. Attempt to start Kafka manually:
C:\kafka\bin\windows\kafka-server-start.bat
C:\kafka\config\server.properties
6. Observe any errors displayed. If Kafka does not start, real time refreshing will not
work.
ØRestore Kafka Installation (If Corrupted)
1. Stop KafkaServiceManager via services.msc.
2. Ensure Scan2x Win is updated to the latest version.
3. Restore the Kafka directory:
- Navigate to C:\Program Files (x86)\Scan2x\Setup
- Copy the kafka folder
- Replace the folder in C:\
4. Start KafkaServiceManager again.
5. Verify background cmd.exe presence and absence of new log errors.
Escalation Guidance
If issues persist, collect logs, screenshots of environment variables, service status, and confirm network conditions (e.g., port 9092 and 2181 availability). If an issue still occurs, please contact the Avantech support team by sending an email to support@avantechsoftware.com
|
