@PostConstruct method not run during initialization












0















I have a weird problem regarding @PostConstruct. I have several classes, which are run during initialization to load background tasks into memory.



I have written 3 of these classes.
Only one of those classes PostConstruct method is run during startup.
I have deleted other methods in these following classes, because they do not matter. SchedulableService only holds helper methods



this one work and is initialized correctly with the message appearing in log



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkTerminationEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkTerminationEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work termination Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


I have written almost the same class, but this does not run at startup. I have tried putting a breakpoint on this class during startup aswell, but it does not break inside this class nor is there anything in the logs. Could someone suggest why? I have been googling around, but without help. The stack during init is clear and the project "boots" up fine.



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkSuspensionEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkSuspensionEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work suspension Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


Why doesn't NightlyWorkSuspensionEmailSender postConstruct method work, when it is basically identical with NightlyWorkTerminationEmailSender










share|improve this question

























  • This smells like a build or packaging problem...

    – Steve C
    Nov 9 '17 at 2:19
















0















I have a weird problem regarding @PostConstruct. I have several classes, which are run during initialization to load background tasks into memory.



I have written 3 of these classes.
Only one of those classes PostConstruct method is run during startup.
I have deleted other methods in these following classes, because they do not matter. SchedulableService only holds helper methods



this one work and is initialized correctly with the message appearing in log



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkTerminationEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkTerminationEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work termination Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


I have written almost the same class, but this does not run at startup. I have tried putting a breakpoint on this class during startup aswell, but it does not break inside this class nor is there anything in the logs. Could someone suggest why? I have been googling around, but without help. The stack during init is clear and the project "boots" up fine.



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkSuspensionEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkSuspensionEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work suspension Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


Why doesn't NightlyWorkSuspensionEmailSender postConstruct method work, when it is basically identical with NightlyWorkTerminationEmailSender










share|improve this question

























  • This smells like a build or packaging problem...

    – Steve C
    Nov 9 '17 at 2:19














0












0








0








I have a weird problem regarding @PostConstruct. I have several classes, which are run during initialization to load background tasks into memory.



I have written 3 of these classes.
Only one of those classes PostConstruct method is run during startup.
I have deleted other methods in these following classes, because they do not matter. SchedulableService only holds helper methods



this one work and is initialized correctly with the message appearing in log



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkTerminationEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkTerminationEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work termination Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


I have written almost the same class, but this does not run at startup. I have tried putting a breakpoint on this class during startup aswell, but it does not break inside this class nor is there anything in the logs. Could someone suggest why? I have been googling around, but without help. The stack during init is clear and the project "boots" up fine.



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkSuspensionEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkSuspensionEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work suspension Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


Why doesn't NightlyWorkSuspensionEmailSender postConstruct method work, when it is basically identical with NightlyWorkTerminationEmailSender










share|improve this question
















I have a weird problem regarding @PostConstruct. I have several classes, which are run during initialization to load background tasks into memory.



I have written 3 of these classes.
Only one of those classes PostConstruct method is run during startup.
I have deleted other methods in these following classes, because they do not matter. SchedulableService only holds helper methods



this one work and is initialized correctly with the message appearing in log



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkTerminationEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkTerminationEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work termination Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


I have written almost the same class, but this does not run at startup. I have tried putting a breakpoint on this class during startup aswell, but it does not break inside this class nor is there anything in the logs. Could someone suggest why? I have been googling around, but without help. The stack during init is clear and the project "boots" up fine.



package ee.rmit.tor.ejb.timer;

import ee.rmit.tor.domain.enums.SystemParameterType;
import ee.rmit.tor.ejb.search.WorkingSearchService;
import org.slf4j.Logger;

import java.util.Calendar;
import java.util.Date;

import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.ScheduleExpression;
import javax.ejb.Singleton;
import javax.ejb.Startup;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.inject.Inject;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

@Singleton
@Startup
@TransactionManagement(TransactionManagementType.BEAN)
public class NightlyWorkSuspensionEmailSender extends SchedulableService {
private final static String TIMER_ID = "WorkSuspensionEmailNotificationServiceTimer";

/**
* Default schedule time
*/
public static final String DEFAULT_SCHEDULE_TIME = "05:00";


@PersistenceContext
EntityManager entityManager;

@Inject
private Logger logger;

@Resource
private TimerService timerService;

@Inject
protected WorkingSearchService workingSearchService;


/**
* Schedules the timer to run at predetermined time
*/

@PostConstruct
public void postConstruct() {
// get the configuration parameter from DB
Date notificationTime = getNextExecutionTime(SystemParameterType.EMAIL_TEAVITUS_TOOTAJALE_AEG,
DEFAULT_SCHEDULE_TIME);

Calendar calendar = Calendar.getInstance();
calendar.setTime(notificationTime);

String timeHhMm = calendar.get(Calendar.HOUR_OF_DAY) + ":" + calendar.get(Calendar.MINUTE);
// create schedule
ScheduleExpression schedule = new ScheduleExpression();
schedule.hour(calendar.get(Calendar.HOUR_OF_DAY)).minute(calendar.get(Calendar.MINUTE));

timerService.createCalendarTimer(schedule, new TimerConfig(TIMER_ID, false));
logger.info("Work suspension Email notification service has been scheduled to run every day at {}", timeHhMm);
}

}


Why doesn't NightlyWorkSuspensionEmailSender postConstruct method work, when it is basically identical with NightlyWorkTerminationEmailSender







java spring ejb weblogic12c postconstruct






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 '18 at 3:08









Cœur

18.5k9110148




18.5k9110148










asked Nov 7 '17 at 9:15









DarkFeudDarkFeud

7810




7810













  • This smells like a build or packaging problem...

    – Steve C
    Nov 9 '17 at 2:19



















  • This smells like a build or packaging problem...

    – Steve C
    Nov 9 '17 at 2:19

















This smells like a build or packaging problem...

– Steve C
Nov 9 '17 at 2:19





This smells like a build or packaging problem...

– Steve C
Nov 9 '17 at 2:19












1 Answer
1






active

oldest

votes


















0














You have 2 Session Beans with same interface. It's not a bad practice, but you need different JNDI names, or will confuse the container. Probably only first EJB is started.



Try creating specializations of your SchedulableService to each Session Bean.






share|improve this answer
























  • I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

    – DarkFeud
    Nov 10 '17 at 7:11













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f47154009%2fpostconstruct-method-not-run-during-initialization%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














You have 2 Session Beans with same interface. It's not a bad practice, but you need different JNDI names, or will confuse the container. Probably only first EJB is started.



Try creating specializations of your SchedulableService to each Session Bean.






share|improve this answer
























  • I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

    – DarkFeud
    Nov 10 '17 at 7:11


















0














You have 2 Session Beans with same interface. It's not a bad practice, but you need different JNDI names, or will confuse the container. Probably only first EJB is started.



Try creating specializations of your SchedulableService to each Session Bean.






share|improve this answer
























  • I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

    – DarkFeud
    Nov 10 '17 at 7:11
















0












0








0







You have 2 Session Beans with same interface. It's not a bad practice, but you need different JNDI names, or will confuse the container. Probably only first EJB is started.



Try creating specializations of your SchedulableService to each Session Bean.






share|improve this answer













You have 2 Session Beans with same interface. It's not a bad practice, but you need different JNDI names, or will confuse the container. Probably only first EJB is started.



Try creating specializations of your SchedulableService to each Session Bean.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 9 '17 at 16:17









Gilliard MacedoGilliard Macedo

1715




1715













  • I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

    – DarkFeud
    Nov 10 '17 at 7:11





















  • I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

    – DarkFeud
    Nov 10 '17 at 7:11



















I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

– DarkFeud
Nov 10 '17 at 7:11







I have 7 nightly processes extending SchedulableService. 5 of them get run during initialization (2 others are just not init as stated above), but I'll try creating specializations for the 2 of them that randomly don't. Thanks for the suggestions, I have been stuck in this old project and can't figure out how to solve this

– DarkFeud
Nov 10 '17 at 7:11






















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f47154009%2fpostconstruct-method-not-run-during-initialization%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







這個網誌中的熱門文章

Xamarin.form Move up view when keyboard appear

Post-Redirect-Get with Spring WebFlux and Thymeleaf

Anylogic : not able to use stopDelay()