Sorry I do not understand your response. From the stacktrace T5 is building
your service. In the constructor of the service currently created you are
spawning a new thread which again needs services from the T5 app in the run
method, right?
Can't you defer thread creation to a method in your mo
No, not at all. New Thread is spawned at some moment while initializing
T5 app. And there is nothing special about a code:
new Thread(new Runnable() {
@Override
public void run() {
if (logger.isDebugEnabled()) logger.debug(etlName + "
initializing... ")
Are you spawning a new thread in your MongoDBImpl.java:30 which makes use of T5
services, too? From the Stacktrace you are (well T5 IOC is) building the
mongodb service right now. What happens in the ctor of your class? Can you
paste some code??
Jens
Sent from my iPhone
On 18.04.2013, at 17:
Hi,
We are using T5 version 5.3.6. I found that Tapestry runs into a dead
lock while building registry (initializing) if I start a new Thread what
uses some T5 services.
Right now we have disabled multi threading while initializing app. But I
would like to know, is it a T5 bug and I should fil
