View Issue Details

IDProjectCategoryView StatusLast Update
0004513SymmetricDS ProBugpublic2020-09-01 12:21
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.11.0 
Target Version3.12.3Fixed in Version3.12.3 
Summary0004513: Setup of load only node hangs because of NPE
DescriptionSetup a load only node and the in-progress dialog will run forever until you dismiss it. In the log, it hit a null pointer exception.

ERROR [client-1] [BackgroundRefresherService] [background-refresher-2] Exception while refreshing class com.jumpmind.symmetric.console.ui.common.InProgressDialog$2 java.lang.NullPointerException
    at com.jumpmind.symmetric.console.ui.wizard.setup.SummaryScreen$InstallWorker.doWork(SummaryScreen.java:99)
    at com.jumpmind.symmetric.console.ui.common.InProgressDialog$2.onBackgroundDataRefresh(InProgressDialog.java:99)
    at com.jumpmind.symmetric.console.ui.BackgroundRefresherService.refresh(BackgroundRefresherService.java:99)
    at com.jumpmind.symmetric.console.ui.BackgroundRefresherService$3.run(BackgroundRefresherService.java:142)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
TagsNo tags attached.

Relationships

related to 0004512 closedelong Setup of load only node hangs because of NPE 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2020-08-28 13:00 elong New Issue
2020-08-28 13:00 elong Status new => assigned
2020-08-28 13:00 elong Assigned To => elong
2020-08-28 13:00 elong Issue generated from: 0004512
2020-08-28 13:00 elong Relationship added related to 0004512
2020-08-28 13:03 elong Status assigned => resolved
2020-08-28 13:03 elong Resolution open => fixed
2020-08-28 13:03 elong Fixed in Version => 3.12.3
2020-09-01 12:21 elong Status resolved => closed