Клиент: вер. 5.2 сборка 1177 от 06.06.2013 19:18:20
os: Windows 7; java: Java HotSpot(TM) 64-Bit Server VM, v.1.6.0_41
Сервер: вер. 5.2 сборка 1507 от 06.06.2013 19:18:28
os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.6.0_22
inet вер. 5.2 сборка 1188 от 07.06.2013 19:05:13
Создаю сервис скриптом через вызов
InetServService.inetServUpdate()
Сервис создаётся, но состояние пишет "удалён", при авторизации он не находится, а в логах вот такая ошибка:
Код:
connection 06-13/12:44:01 INFO [sa-p-11-t-14] ServiceActivatorSet - Connecting to device
connection 06-13/12:44:01 INFO [sa-p-11-t-14] ServiceActivatorDeviceWorker - Do task deviceId: 16; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent] moduleId: 30; pluginId: no; cid: global; scid: -1; userId: -1; oldInetServ: null; newInetServ: Gi0/0.20110126; newInetServState: 1; newInetServOptionList: ; timestamp: 1371095041174
connection 06-13/12:44:01 INFO [sa-p-11-t-14] InetServRuntimeMap - Adding new InetServRuntime: 2365
connection 06-13/12:44:01 INFO [sa-p-11-t-14] InetServRuntimeMap - Loading inetServ from database.
connection 06-13/12:44:01 ERROR [sa-p-11-t-14] InetServRuntimeMap -
java.lang.NullPointerException
at ru.bitel.bgbilling.modules.inet.runtime.InetServRuntimeMap.newRuntime(InetServRuntimeMap.java:381)
at ru.bitel.bgbilling.modules.inet.runtime.InetServRuntimeMap.newRuntime(InetServRuntimeMap.java:885)
at ru.bitel.bgbilling.modules.inet.runtime.InetServRuntimeMap.onInetServModified(InetServRuntimeMap.java:825)
at ru.bitel.bgbilling.modules.inet.runtime.InetServRuntimeMap.addRuntime(InetServRuntimeMap.java:802)
at ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent.toSaEvent(InetSaServModifyEvent.java:194)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doTask(ServiceActivatorDeviceWorker.java:254)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.notify(AsyncEventWorker.java:122)
at ru.bitel.bgbilling.kernel.event.AcknowledgeConsumer.onMessage0(AcknowledgeConsumer.java:75)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalDoTask(EventWorker.java:179)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.doTasks(AsyncEventWorker.java:75)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runWorker(ServiceActivatorDeviceWorker.java:180)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalRunWorker(EventWorker.java:115)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runImpl(ServiceActivatorDeviceWorker.java:118)
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 06-13/12:44:01 ERROR [sa-p-11-t-14] ServiceActivatorDeviceWorker - Device:16 - null
java.lang.NullPointerException
at ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent.toSaEvent(InetSaServModifyEvent.java:220)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.doTask(ServiceActivatorDeviceWorker.java:254)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.notify(AsyncEventWorker.java:122)
at ru.bitel.bgbilling.kernel.event.AcknowledgeConsumer.onMessage0(AcknowledgeConsumer.java:75)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalDoTask(EventWorker.java:179)
at ru.bitel.bgbilling.kernel.event.AsyncEventWorker.doTasks(AsyncEventWorker.java:75)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runWorker(ServiceActivatorDeviceWorker.java:180)
at ru.bitel.bgbilling.kernel.event.EventWorker.internalRunWorker(EventWorker.java:115)
at ru.bitel.bgbilling.modules.inet.access.sa.ServiceActivatorDeviceWorker.runImpl(ServiceActivatorDeviceWorker.java:118)
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)
Лечится передёргиванием статуса сервиса.
My guess - проблема с commit-ом в базу.