[weld-issues] [JBoss JIRA] Commented: (WELDSERVLET-6) Conversation should work on AppEngine

[ https://jira.jboss.org/jira/browse/WELDSERVLET-6?page=com.atlassian.jira.... ] Paul Bakker commented on WELDSERVLET-6: --------------------------------------- How did you test this? I just built Weld from the trunk but it still doesn't work (neither on the development server and the production server). If I look at the code I still find the following in SingleThreadScheduledExecutorServiceFactory: *code* this.executorService = Executors.newScheduledThreadPool(1); *code* and in AbstractConversationManager: *code* private Future<?> scheduleForTermination(String cid, long timeout) { Runnable terminationTask = new TerminationTask(cid); return Container.instance().services().get(ScheduledExecutorServiceFactory.class).get().schedule(terminationTask, timeout, TimeUnit.MILLISECONDS); } *code* Calling schedule on a ScheduledExecutorService is not possible on AppEngine as far as I know. I tested this with the following code too in a plain servlet: *code* ScheduledExecutorService exec = Executors.newSingleThreadScheduledExecutor(); Runnable r = new Runnable() { @Override public void run() { System.out.println("test"); } }; //Throws exception exec.schedule(r, 5, TimeUnit.SECONDS); *code* Although this code creates a single thread, it's still an extra thread, and that's not allowed by AppEngine. I think Pete's solution is the only way (using the task queue). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira