[JBoss jBPM] - Re: Process Definition Deployment using ZipInputStream
by jbarrez
I included a test case for this in the test suite, but the test succeeds. So either I'm testing the wrong thing or you are doing something wrong:
| public void testZippedResourceDeployment() {
| FileInputStream fip = null;
| try {
|
| fip = new FileInputStream("src/test/resources/org/jbpm/test/deploy/process.zip");
| ZipInputStream zis = new ZipInputStream(fip);
|
| NewDeployment newDeployment = repositoryService.createDeployment();
| newDeployment.addResourcesFromZipInputStream(zis);
| String deployId = newDeployment.deploy();
|
| ProcessDefinition procDef = repositoryService.createProcessDefinitionQuery()
| .deploymentId(deployId)
| .uniqueResult();
| assertNotNull(procDef);
| assertEquals("ImageTest", procDef.getName());
| repositoryService.deleteDeploymentCascade(deployId);
|
| } catch (IOException e) {
| fail(e.getMessage());
| } finally {
| if (fip != null) {
| try {
| fip.close();
| } catch (IOException e) {
| fail(e.getMessage());
| }
| }
| }
|
| }
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247209#4247209
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247209
16 years, 3 months
[Performance Tuning] - JBOSS 5.1.x :: Unused services ...
by preetam_pict
Hello all,
I am trying to stop / remove some of the JBoss unused services which my application does not use.
Basically I have an enterprise application (EAR) with some EJB3s and Servlets etc.
I have removed following files
1. remove hdscanner-jboss-beans.xml
2. remove ejb2-timer-service.xml
3. remove ejb3-timerservice-jboss-beans.xml
4. remove profileservice-jboss-beans.xml
5. remove profileservice-secured.jar
6. remove schedule-manager-service.xml
7. remove scheduler-service.xml
8. remove uuid-key-generator.sar
9. remove quartz-ra.rar
10. http-invoker.sar
Now, when I deploy my application EAR, the deployment fails with following error ...
| 14:00:51,053 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of
| incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "jboss.j2ee:ear=QueryGeneratorEnterprise.ear,jar=QueryGeneratorEJB.
| jar,name=RequestListnerMDBBean,service=EJB3" is missing the following dependenci
| es:
| Dependency "<UNKNOWN jboss.j2ee:ear=QueryGeneratorEnterprise.ear,jar=QueryGe
| neratorEJB.jar,name=RequestListnerMDBBean,service=EJB3>" (should be in state "De
| scribed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJB
| TimerService' **")
|
Looks like that my MDB "ResponseListnerMDBBean" is causing the problem..
I am not able to understand, since I am not used any EJB timer service why my MDB is shown as having dependency over EJBTimerService!
Please help me experts here to understand what is happening !
Thanks
~PP
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247205#4247205
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247205
16 years, 3 months
[JBoss Messaging] - connection failure message should report client ip
by AdrianWoodhead
In JBM 2.0.0.BETA3, if a client shuts down without closing its connections (e.g. it crashes) you see the following in the server log file:
anonymous wrote : 09:37:31,347 WARNING [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive ping from client. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3
| 09:37:31,348 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 0687b9f5-7d74-11de-9648-0019b9ebba6b
| 09:37:31,348 WARNING [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session 0687b9f5-7d74-11de-9648-0019b9ebba6b
If possible it would be great if this message could output the IP address of the client that caused this. This would help to determine the location of a faulty client.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247200#4247200
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247200
16 years, 3 months