Обновился вчера на 5.2 до крайней версии:
Сервер: вер. 5.2 сборка 1616 от 11.12.2014 18:58:11
os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.6.0_22
inet вер. 5.2 сборка 1354 от 19.01.2015 16:28:32
Код:
#./access_status.sh
Java Runtime: Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM [1.6.0_22] /opt/sun-jdk-1.6.0.22/jre
Runtime name: 23434@bg1.dsi.srv
Java endorsed dirs: /lib/endorsed:/etc/java-config-2/current-system-vm/lib/endorsed
OS: Linux 2.6.33-gentoo [amd64], file.encoding: UTF-8, user.name: root
Heap sizes: current=245248k free=243967k max=3639104k
Kernel version 5.2 build 1616 from 11.12.2014 18:58:11
Inet version 5.2 build 1354 from 19.01.2015 16:28:32
Смотрю логи в BGInetAccess-Inet-IPoE (mid=28), вижу ошибки.
Сегодня в 8:49 переоформляли договор cid : 188306->217721:
Код:
connection 01-21/08:49:01 INFO [sa-p-12-t-9] ServiceActivatorSet - Connecting to device
connection 01-21/08:49:01 INFO [sa-p-12-t-9] ServiceActivatorDeviceWorker - Do task deviceId: 23; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent] moduleId: 28; pluginId: no; cid: 188306; scid: -1; userId: -1; oldInetServ: IPoE: asr1 - Te0/1/0.14120297; newInetServ: null; newInetServState: 0; newInetServOptionList: ; timestamp: 1421801341959
connection 01-21/08:49:01 ERROR [sa-p-12-t-9] InetSaServModifyEvent -
java.lang.NullPointerException
at ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent.toSaEvent(InetSaServModifyEvent.java:265)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doTask(ServiceActivatorDeviceWorker.java:277)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.internalDoTaskImpl(AsyncEventWorker.java:209)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.notify(AsyncEventWorker.java:199)
at ru.bitel.bgbilling.kernel.event.AcknowledgeConsumer.onMessage0(AcknowledgeConsumer.java:83)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.internalDoTask(AsyncEventWorker.java:174)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.doTasks(AsyncEventWorker.java:107)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runWorker(ServiceActivatorDeviceWorker.java:203)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalRunWorker(EventWorker.java:139)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runImpl(ServiceActivatorDeviceWorker.java:133)
at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:86)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
connection 01-21/08:49:01 INFO [sa-p-12-t-9] InetApplication - TariffOptionMap: {}
connection 01-21/08:49:02 INFO [sa-p-12-t-9] InetApplication - OptionSet: [155, 203, 74, 15]
connection 01-21/08:49:02 INFO [sa-p-12-t-9] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=3; inetServId: 10333; call: true; oldState: 0; newState: 0; oldOptionSet: 155,203,74,15; newOptionSet: 155,203,74,15
connection 01-21/08:49:02 INFO [sa-p-12-t-9] ServiceActivatorDeviceWorker - Processing deviceId:23; command ServiceActivatorEvent type=3; inetServId: 10333; call: true; oldState: 0; newState: 0; oldOptionSet: 155,203,74,15; newOptionSet: 155,203,74,15
connection 01-21/08:49:02 INFO [sa-p-12-t-9] ServiceActivatorSet - Invoking serviceCancel
connection 01-21/08:49:02 INFO [sa-p-12-t-9] ServiceActivatorDeviceWorker - Process event type[3] result=true
connection 01-21/08:49:02 INFO [sa-p-12-t-9] ServiceActivatorDeviceWorker - Do task deviceId: 23; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent] moduleId: 28; pluginId: no; cid: 217721; scid: -1; userId: -1; oldInetServ: null; newInetServ: IPoE: asr1 - Te0/1/0.14120297; newInetServState: -1; newInetServOptionList: ; timestamp: 1421801342577
connection 01-21/08:49:02 INFO [sa-p-12-t-9] InetServRuntimeMap - Adding new InetServRuntime: 10899
connection 01-21/08:49:02 INFO [sa-p-12-t-9] InetServRuntimeMap - Loading inetServ from database.
connection 01-21/08:49:02 WARN [sa-p-12-t-9] ContractRuntimeMap - Contract id=217721 not found
connection 01-21/08:49:02 ERROR [sa-p-12-t-9] InetServRuntimeMap - Contract not found with id=217721 but inetServ exist
connection 01-21/08:49:02 ERROR [sa-p-12-t-9] ServiceActivatorDeviceWorker - Device:23 - null
java.lang.NullPointerException
at ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent.toSaEvent(InetSaServModifyEvent.java:248)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doTask(ServiceActivatorDeviceWorker.java:277)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.internalDoTaskImpl(AsyncEventWorker.java:209)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.notify(AsyncEventWorker.java:199)
at ru.bitel.bgbilling.kernel.event.AcknowledgeConsumer.onMessage0(AcknowledgeConsumer.java:83)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.internalDoTask(AsyncEventWorker.java:174)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.doTasks(AsyncEventWorker.java:107)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runWorker(ServiceActivatorDeviceWorker.java:203)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalRunWorker(EventWorker.java:139)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runImpl(ServiceActivatorDeviceWorker.java:133)
at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:86)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
...
Сессия поднялась потом в 09:02 из апдейта, так что перерыва связи вроде не было, да и не жаловался никто.
Просто вот эксепшены в логах увидел.