[JBoss jBPM] - Re: Mail notification
by orochimaru19860000
Well, it doesen't give any exeption, but just a warning:
[ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.TaskNode - this operation breaks ==
My processdefinition.xml is like this:
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition
| xmlns="" name="exempde">
| <start-state name="start">
| <transition name="debuter" to="identification"></transition>
| </start-state>
| <task-node name="identification">
| <task name="identify"></task>
| <transition name="evaluate" to="evaluer"> </transition>
| </task-node>
| <decision name="evaluer">
| <transition name="winner" to="winner">
| <condition>#{nom == 'ettaib'}</condition>
| </transition>
| <transition name="loser" to="loser">
| <condition>#{nom == 'waterman'}</condition>
| </transition>
| </decision>
| <task-node name="winner">
| <task name="win"></task>
| <transition name="fin1" to="end1"></transition>
| </task-node>
| <task-node name="loser">
| <task name="lose"></task>
| <transition name="fin2" to="end1"></transition>
| </task-node>
| <end-state name="end1"></end-state>
| </process-definition>
Should I install a mail server?
Have you already tested it?
If you have any suggestion please let me know very soon.
thx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070043#4070043
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070043
18Â years, 8Â months
[JBoss Tools (users)] - hello iam getting the following error when i do as given in
by amritalekshmy
15:28:25,171 ERROR [MainDeployer] Could not initialise deployment: file:/F:/jboss-3.2.7/server/default/deploy/FiboApp.ear
org.jboss.deployment.DeploymentException: Failed to find module file: FiboWeb.war
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:232)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:696)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:631)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:415)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:191)
at org.jboss.Main$1.run(Main.java:480)
at java.lang.Thread.run(Thread.java:595)
15:28:25,171 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Packages waiting for a deployer:
org.jboss.deployment.DeploymentInfo@c2c1841b { url=file:/F:/jboss-3.2.7/server/default/deploy/http-invoker.sar/invoker.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/http-invoker.sar/invoker.war/
lastDeployed: 1186048703140
lastModified: 1184159755468
mbeans:
org.jboss.deployment.DeploymentInfo@93476f5 { url=file:/F:/jboss-3.2.7/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
lastDeployed: 1186048703140
lastModified: 1184159755609
mbeans:
org.jboss.deployment.DeploymentInfo@a58cbc10 { url=file:/F:/jboss-3.2.7/server/default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/jmx-console.war/
lastDeployed: 1186048705140
lastModified: 1184159763250
mbeans:
org.jboss.deployment.DeploymentInfo@ff1c63df { url=file:/F:/jboss-3.2.7/server/default/deploy/management/web-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/management/web-console.war/
lastDeployed: 1186048705140
lastModified: 1184159764187
mbeans:
Incompletely deployed packages:
org.jboss.deployment.DeploymentInfo@a58cbc10 { url=file:/F:/jboss-3.2.7/server/default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/jmx-console.war/
lastDeployed: 1186048705140
lastModified: 1184159763250
mbeans:
org.jboss.deployment.DeploymentInfo@ff1c63df { url=file:/F:/jboss-3.2.7/server/default/deploy/management/web-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/F:/jboss-3.2.7/server/default/deploy/management/web-console.war/
lastDeployed: 1186048705140
lastModified: 1184159764187
mbeans:
org.jboss.deployment.DeploymentInfo@dde54ab5 { url=file:/F:/jboss-3.2.7/server/default/deploy/FiboApp.ear }
deployer: org.jboss.deployment.EARDeployer@90c06f
status: null
state: FAILED
watch: file:/F:/jboss-3.2.7/server/default/deploy/FiboApp.ear
lastDeployed: 1186048705171
lastModified: 1186048705140
mbeans:
MBeans waiting for other MBeans:
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker
jboss.web:service=WebServer
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.web:service=WebServer
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
15:28:25,359 INFO [Server] JBoss (MX MicroKernel) [3.2.7 (build: CVSTag=JBoss_3_2_7 date=200501280217)] Started in 11s:63ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070041#4070041
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070041
18Â years, 8Â months
[JBossCache] - Re: Performing cache operations while in a catch() section
by dfraser
yes, that is sort of it - I figured it out just before you replied. the entire operation is wrapped in a transaction (it's processing a MDB message) and communication with another system fails, so the code throws an exception to trigger the catch section in the onMessage() method that acts as a general point for rolling back operations. In that catch(), the cache operation happens - and the cache is set up to use transactions. then the overall transaction gets rolled back, so another node could retry processing the message.
so since the overall transaction gets rolled back, transactions within won't complete properly.
so I need to look at whether all the cache operations really need to be transactional (can I suspend the use of transactions in the cache individually?) or figure out how to suspend the overall transaction (but the container is doing all that work right now, so I'd have to get into the guts of things... that does not sound appetizing)
thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070040#4070040
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070040
18Â years, 8Â months
[JBossWS] - Deployment exception with JbossWs 2.0.0 - Cannot find servic
by matt_law
I am deploying a set of EJB3 classes to JBoss 4.0.5 which has EJB3 rc9 & JBossWS 2.0.0 installed. Previously the ejbs have been deployed to jboss 4.0.4 with ejb3 rc9 & jbossws 1.2 with no errors. Now when I start jboss I get the following error
| 11:21:49,965 ERROR [MainDeployer] Could not start deployment: file:/C:/Development/jboss/jboss-4.0.5.GA.TMP/server/default/deploy/GermanPatientHistoryEJB.jar
| javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=AddressServiceBean,service=EJB3,jar=GermanPatientHistoryEJB.jar
| at org.jboss.wsf.container.jboss40.InvocationHandlerEJB3.start(InvocationHandlerEJB3.java:70)
| at org.jboss.wsf.spi.deployment.BasicLifecycleHandler.start(BasicLifecycleHandler.java:57)
| at org.jboss.wsf.stack.jbws.LifecycleHandlerImpl.start(LifecycleHandlerImpl.java:40)
| at org.jboss.wsf.spi.deployment.EndpointLifecycleDeployer.start(EndpointLifecycleDeployer.java:49)
| at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:81)
| at org.jboss.wsf.container.jboss42.MainDeployerHook.deploy(MainDeployerHook.java:46)
| at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy31.start(Unknown Source)
|
This is despite the fact that I can see the WSDL has been deployed and the endpoint registered -
| 11:21:49,903 INFO [BasicEndpointRegistry] register: jboss.ws:context=GermanPatientHistoryEJB,endpoint=AddressServiceBean
|
I can even view the WSDL through the browser once JBoss completes startup. However, any attempt to invoke them fails.
I have not changed any annotations in the beans as it all looks to be the same as per the User Guide. I do not understand where the deployer is looking for the endpoint, or what might cause this problem. Any help, suggestions would be great.
Matt.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070039#4070039
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070039
18Â years, 8Â months