Update timeout handling in MessageConsumerImpl

Replaced millisecond-based timing with nanosecond precision for more accurate timeout calculations during message waiting. This change improves reliability in scenarios with tight timing constraints.

Author: iitsoftware

src/main/java/com/swiftmq/jms/v750/MessageConsumerImpl.java

@@ -33,6 +33,7 @@
 import javax.jms.IllegalStateException;
 import javax.jms.*;
 import java.util.List;
+import java.util.concurrent.TimeUnit;
 import java.util.concurrent.atomic.AtomicBoolean;
 import java.util.concurrent.atomic.AtomicInteger;
 import java.util.concurrent.locks.Lock;
@@ -371,9 +372,9 @@ Message receiveMessage(boolean block, long timeout) throws JMSException {
                             } else {
                                 long to = timeout;
                                 do {
-                                    long startWait = System.currentTimeMillis();
+                                    long startWait = System.nanoTime();
                                     waiter.doWait(to);
-                                    long delta = System.currentTimeMillis() - startWait;
+                                    long delta = TimeUnit.NANOSECONDS.toMillis(System.nanoTime() - startWait);
                                     to -= delta;
                                 }
                                 while (to > 0 && messageCache.getSize() == 0 && fillCachePending.get() && !cancelled.get() && !isClosed());