A exceção ocorre durante a manipulação de uma grande quantidade de informações, que acaba consumindo muito tempo e excede o default-timeout de 5 minutos.
Solução:
Adicionar a linha abaixo no standalone.xml do WildFly/JBoss,
The @Asynchronous annotation was introduced in EJB 3.1 as a simple way of creating asynchronous processing.
Every time a method annotated @Asynchronous is invoked by anyone it will immediately return regardless of how long the method actually takes. Each invocation returns a Future object that essentially starts out empty and will later have its value filled in by the container when the related method call actually completes. Returning a Future object is not required and @Asynchronous methods can of course return void.
Example
Here, in JobProcessorTest,
finalFuture<String> red = processor.addJob("red"); proceeds to the next statement,
without waiting for the addJob() method to complete. And later we could ask for the result using the Future<?>.get() method like
assertEquals("blue", blue.get());
It waits for the processing to complete (if its not completed already) and gets the result. If you did not care about the result, you could simply have your asynchronous method as a void method.
A Future represents the result of an asynchronous computation. Methods are provided to check if the computation is complete, to wait for its completion, and to retrieve the result of the computation. The result can only be retrieved using method get when the computation has completed, blocking if necessary until it is ready. Cancellation is performed by the cancel method. Additional methods are provided to determine if the task completed normally or was cancelled. Once a computation has completed, the computation cannot be cancelled. If you would like to use a Future for the sake of cancellability but not provide a usable result, you can declare types of the form Future and return null as a result of the underlying task
The code
@SingletonpublicclassJobProcessor{@Asynchronous@Lock(READ)@AccessTimeout(-1)publicFuture<String> addJob(String jobName){// Pretend this job takes a while
doSomeHeavyLifting();// Return our resultreturnnewAsyncResult<String>(jobName);}privatevoid doSomeHeavyLifting(){try{Thread.sleep(SECONDS.toMillis(10));}catch(InterruptedException e){Thread.interrupted();thrownewIllegalStateException(e);}}}
Test
publicclassJobProcessorTestextendsTestCase{publicvoid test()throwsException{finalContext context =EJBContainer.createEJBContainer().getContext();finalJobProcessor processor =(JobProcessor) context.lookup("java:global/async-methods/JobProcessor");finallong start =System.nanoTime();// Queue up a bunch of workfinalFuture<String> red = processor.addJob("red");finalFuture<String> orange = processor.addJob("orange");finalFuture<String> yellow = processor.addJob("yellow");finalFuture<String> green = processor.addJob("green");finalFuture<String> blue = processor.addJob("blue");finalFuture<String> violet = processor.addJob("violet");// Wait for the result -- 1 minute worth of work
assertEquals("blue", blue.get());
assertEquals("orange", orange.get());
assertEquals("green", green.get());
assertEquals("red", red.get());
assertEquals("yellow", yellow.get());
assertEquals("violet", violet.get());// How long did it take?finallong total =TimeUnit.NANOSECONDS.toSeconds(System.nanoTime()- start);// Execution should be around 9 - 21 seconds// The execution time depends on the number of threads available for asynchronous execution.// In the best case it is 10s plus some minimal processing time.
assertTrue("Expected > 9 but was: "+ total, total >9);
assertTrue("Expected < 21 but was: "+ total, total <21);}}
Running
-------------------------------------------------------
T E S T S
-------------------------------------------------------Running org.superbiz.async.JobProcessorTestApacheOpenEJB4.0.0-SNAPSHOT build:20110801-04:02
http://tomee.apache.org/
INFO - openejb.home = G:\Workspace\fullproject\openejb3\examples\async-methods
INFO - openejb.base= G:\Workspace\fullproject\openejb3\examples\async-methods
INFO -Using'javax.ejb.embeddable.EJBContainer=true'
INFO -ConfiguringService(id=DefaultSecurityService, type=SecurityService, provider-id=DefaultSecurityService)
INFO -ConfiguringService(id=DefaultTransactionManager, type=TransactionManager, provider-id=DefaultTransactionManager)
INFO -FoundEjbModulein classpath: g:\Workspace\fullproject\openejb3\examples\async-methods\target\classes
INFO -Beginning load: g:\Workspace\fullproject\openejb3\examples\async-methods\target\classes
INFO -Configuring enterprise application: g:\Workspace\fullproject\openejb3\examples\async-methods
INFO -ConfiguringService(id=DefaultSingletonContainer, type=Container, provider-id=DefaultSingletonContainer)
INFO -Auto-creating a container for bean JobProcessor:Container(type=SINGLETON, id=DefaultSingletonContainer)
INFO -ConfiguringService(id=DefaultManagedContainer, type=Container, provider-id=DefaultManagedContainer)
INFO -Auto-creating a container for bean org.superbiz.async.JobProcessorTest:Container(type=MANAGED, id=DefaultManagedContainer)
INFO -Enterprise application "g:\Workspace\fullproject\openejb3\examples\async-methods" loaded.
INFO -Assembling app: g:\Workspace\fullproject\openejb3\examples\async-methods
INFO -Jndi(name="java:global/async-methods/JobProcessor!org.superbiz.async.JobProcessor")
INFO -Jndi(name="java:global/async-methods/JobProcessor")
INFO -Jndi(name="java:global/EjbModule100568296/org.superbiz.async.JobProcessorTest!org.superbiz.async.JobProcessorTest")
INFO -Jndi(name="java:global/EjbModule100568296/org.superbiz.async.JobProcessorTest")
INFO -CreatedEjb(deployment-id=org.superbiz.async.JobProcessorTest, ejb-name=org.superbiz.async.JobProcessorTest, container=DefaultManagedContainer)
INFO -CreatedEjb(deployment-id=JobProcessor, ejb-name=JobProcessor, container=DefaultSingletonContainer)
INFO -StartedEjb(deployment-id=org.superbiz.async.JobProcessorTest, ejb-name=org.superbiz.async.JobProcessorTest, container=DefaultManagedContainer)
INFO -StartedEjb(deployment-id=JobProcessor, ejb-name=JobProcessor, container=DefaultSingletonContainer)
INFO -DeployedApplication(path=g:\Workspace\fullproject\openejb3\examples\async-methods)Tests run:1,Failures:0,Errors:0,Skipped:0,Time elapsed:13.305 sec
Results:Tests run:1,Failures:0,Errors:0,Skipped:0[INFO]------------------------------------------------------------------------[INFO] BUILD SUCCESS
[INFO]------------------------------------------------------------------------[INFO]Total time:21.097s[INFO]Finished at:WedAug0322:48:26 IST 2011[INFO]FinalMemory:13M/145M[INFO]------------------------------------------------------------------------
How it works under the covers
Under the covers what makes this work is:
The JobProcessor the caller sees is not actually an instance of JobProcessor. Rather it's a subclass or proxy that has all the methods overridden. Methods that are supposed to be asynchronous are handled differently.
Calls to an asynchronous method simply result in a Runnable being created that wraps the method and parameters you gave. This runnable is given to an Executor which is simply a work queue attached to a thread pool.
After adding the work to the queue, the proxied version of the method returns an implementation of Future that is linked to the Runnable which is now waiting on the queue.
When the Runnable finally executes the method on the realJobProcessor instance, it will take the return value and set it into the Future making it available to the caller.
Important to note that the AsyncResult object the JobProcessor returns is not the same Future object the caller is holding. It would have been neat if the real JobProcessor could just return String and the caller's version of JobProcessor could return Future<String>, but we didn't see any way to do that without adding more complexity. So the AsyncResult is a simple wrapper object. The container will pull the String out, throw the AsyncResult away, then put the String in the realFuture that the caller is holding.
To get progress along the way, simply pass a thread-safe object like AtomicInteger to the @Asynchronous method and have the bean code periodically update it with the percent complete.
Related Examples
For complex asynchronous processing, JavaEE's answer is @MessageDrivenBean. Have a look at the simple-mdb example
O banco de dados PostgreSQL nos disponibiliza algumas ferramentas, que são pequenos executáveis que fazem esse serviço de backup e restore.
Através do prompt de comando:
Localize a pasta de instalação do PostgreSQL (c:\Arquivos de Programas\PostgreSQL\9.0\bin) especificamente a basta bin, dentro dela está localizado o executável pg_dump.exe que fará a exportação (dump).
Digite o comando: pg_dump.exe --host localhost --port 5432 --username postgres --format tar --file c:\nome_arquivo_que_sera_gerado.backup ManagerEDoc
O comando é auto explicativo, porém vamos ver em mais detalhes: --host localhost : define o local onde o banco se encontra, pode ser localmente ou externamente em outra rede. --port 5432 : é definida a porta utilizada, nesse caso a padrão postgres 5432. --username postgres : define qual é o usuário utilizado na comunicação. --format tar : o tipo de compressão do arquivo gerado. --file nomedoarquivo.backup : define com qual nome e caminho completo do arquivo que será gerado. ManagerEDoc : por último vai o nome do banco que se estará exportando, atenção neste ponto, pois é case sensitive, ou seja ele considera letras maiúsculas e minúsculas.
Pronto, basta executar o comando e verificar se o arquivo exportado, está conforme definido no nome do arquivo.
Como fazer o restore binário do banco postgres
Através do prompt de comando:
Localize a pasta de instalação do PostgreSQL (c:\Arquivos de Programas\PostgreSQL\9.0\bin) especificamente a basta bin, dentro dela está localizado o executável pg_restore.exe que fará o restore.
O comando é auto explicativo, porém vamos ver em mais detalhes: --host localhost : define o local onde o banco se encontra, pode ser localmente ou externamente em outra rede. --port 5432 : é definida a porta utilizada, nesse caso a padrão postgres 5432. --username postgres : define qual é o usuário utilizado na comunicação. --dbname ManagerEDoc : o nome do banco que se estará exportando, atenção neste ponto, pois é case sensitive, ou seja ele considera letras maiúsculas e minúsculas.
por último, vai o caminho completo do arquivo que deseja restaurar.
Pronto, basta executar o comando e verificar se o banco foi restaurado com sucesso.
Como realizar a exportação do sql de um banco com inserts
Este modo de dump, é arriscado pois muitas tabelas possuem relacionamentos, handles e sequences em andamento o que pode comprometer inserir em um novo banco de dados, porém pode ser útil em determinado momento.
Ele consiste em fazer o dump de uma tabela em específico, segue abaixo um exemplo do comando.
1 - Localize a pasta de instalação do PostgreSQL (c:\Arquivos de Programas\PostgreSQL\9.0\bin) especificamente a basta bin, dentro dela está localizado o executável pg_dump.exe que fará a exportação (dump).
2 - Estando lá, basta executar o seguinte comando: pg_dump.exe --host localhost --port 5432 --username postgres --format plain --data-only --inserts --column-inserts --table "public.\"TspdNFCe\"" --file c:\TspdNFCe.sql ManagerEDoc
O TspdNFCe se refere à qual tabela será feito dump
3 - Feito isso, será gerado o arquivo com todos os inserts da tabela solicitada, conforme definido.
