Добрый день!
Используется связка BGBilling+mpd5.
При разрыве сессии в мониторе, в логах access сервера появляются ошибки:
Код:
connection 08-28/10:15:24 ERROR [sa-p-13-t-1] RadiusClient - Invalid argument
java.net.SocketException: Invalid argument
<-->at sun.nio.ch.DatagramChannelImpl.send0(Native Method)
<-->at sun.nio.ch.DatagramChannelImpl.sendFromNativeBuffer(DatagramChannelImpl.java:304)
<-->at sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:284)
<-->at sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:254)
<-->at ru.bitel.common.io.DatagramChannelListener.send(DatagramChannelListener.java:275)
<-->at ru.bitel.bgbilling.kernel.network.radius.RadiusClient.sendAsync(RadiusClient.java:446)
<-->at ru.bitel.bgbilling.modules.inet.dyn.device.radius.CoAServiceActivator.connectionClose(CoAServiceActivator.java:116)
<-->at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorSet.connectionClose(ServiceActivatorSet.java:209)
<-->at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doCommand(ServiceActivatorDeviceWorker.java:483)
<-->at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doTask(ServiceActivatorDeviceWorker.java:436)
<-->at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.notify(AsyncEventWorker.java:143)
<-->at ru.bitel.bgbilling.kernel.event.AcknowledgeConsumer.onMessage0(AcknowledgeConsumer.java:81)
<-->at ru.bitel.bgbilling.kernel.event.EventWorker.internalDoTask(EventWorker.java:229)
<-->at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.doTasks(AsyncEventWorker.java:96)
<-->at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runWorker(ServiceActivatorDeviceWorker.java:198)
<-->at ru.bitel.bgbilling.kernel.event.EventWorker.internalRunWorker(EventWorker.java:139)
<-->at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runImpl(ServiceActivatorDeviceWorker.java:136)
<-->at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:86)
<-->at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
<-->at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
<-->at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
<-->at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
<-->at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
<-->at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
<-->at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
<-->at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
<-->at java.lang.Thread.run(Thread.java:662)
<-->at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
Подскажите в чем может быть причина?
_________________
Код:
Клиент: вер. 6.2.874 / 05.02.2018 12:48:36
os: Windows 7; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_151
Сервер: вер. 6.2.1203 / 05.02.2018 12:50:34
os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_45
Вход
Регистрация
FAQ
Поиск
