[JBoss jBPM] - Re: TaskInstance.setActorId(String) causes set TaskInstance
by Octomac
It might be a bug, but I think it may be more likely that Hibernate is receiving the wrong data -- that is, it's expecting a '1' or a '0' perhaps, and is instead getting, say, a "T" or "F" string, which is causing it to always assume "TRUE".
This is a newbie question, but is there a way to turn on transaction logging so that I can see each statement and its corresponding data that is sent to the database? I have the hibernate.show_sql property in my hibernate.cfg.xml set to "true," but this only gives me the query or statement, not the data that goes along with it (that is, I see "UPDATE **** SET **** = ? WHERE blah blah," but the '?' in the statement doesn't have a corresponding value). Being able to see what data is being put into the database will help me immensely.
Thanks again for everyone's help!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158494#4158494
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158494
17 years, 10 months
[JBoss jBPM] - Re: Node as a milestone
by pjacobsen
Thanks for the quick reply Ronald.
I was aware of the term milestone being used in a workflow pattern for synchronizing parallel branches... although I assume this was not fully baked yet as the "milestone-node" doesn't appear the jPDL schema. Looks like there is a test case that exercises it, though.
Anyway... I was having trouble understanding you last sentence or two. Are you saying that what I'm proposing is not inherently bad when using reporting tool like SeeWhy? And what did you mean by anonymous wrote : not use specific queries to retrieve start and end date of normal tasks/nodes/joins/... whatever
FYI... the reason we are doing this is that processes can involve tens or sometimes 100+ steps and process designers want to place milestones to logically mark of points that are of importance to them. Their goal is to set up processes so that any could be viewed from a macro perspective by looking at the progress of the milestone nodes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158489#4158489
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158489
17 years, 10 months
[JBoss/Spring Integration] - Spring integration via AbstractSpringAction
by jakkur
Not sure if this is the right group to post this in, but I will try...
I am integrating Spring framework into my ESB project using AbstractSpringAction where I extend my action classes as shown in the jboss-soa-p.4.2.0 spring_helloworld quickstart sample. While I can build/deploy/run fine the sample, I am getting the following exception when I did the same in my app. Can somebody explain what these exceptions mean and what I am missing if any. Thanks,
2008-06-16 15:49:39,170 WARN [org.jboss.system.ServiceController] Problem starting service jboss.esb:deployment=NDE_DHS_INS.esb
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:188)
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:150)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:69)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:83)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
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 $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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 $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.soa.esb.ConfigurationException: Unexpected exception during lifecycle initialisation
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.initialise(ActionProcessingPipeline.java:264)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:184)
... 51 more
Caused by: java.lang.NullPointerException
at org.jboss.soa.esb.actions.AbstractSpringAction.initialise(AbstractSpringAction.java:60)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.initialise(OverriddenActionLifecycleProcessor.java:123)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.initialise(ActionProcessingPipeline.java:259)
... 52 more
2008-06-16 15:49:39,201 INFO [org.jboss.ejb3.JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
2008-06-16 15:49:39,201 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=business_service-ejb.jar,name=DataFileValidatorEJB,service=EJB3 with dependencies:
2008-06-16 15:49:39,216 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.noaa.espc.nde.dhs.ingest.ejb.DataFileValidatorBean ejbName: DataFileValidatorEJB
2008-06-16 15:49:39,216 INFO [org.jboss.ejb3.JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
2008-06-16 15:49:39,216 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=business_service-ejb.jar,name=MD5ChecksumGeneratorEJB,service=EJB3 with dependencies:
2008-06-16 15:49:39,232 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.noaa.espc.nde.dhs.ingest.ejb.MD5ChecksumGeneratorBean ejbName: MD5ChecksumGeneratorEJB
2008-06-16 15:49:39,248 INFO [org.jboss.ejb3.JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
2008-06-16 15:49:39,248 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=business_service-ejb.jar,name=MetadataExtractorEJB,service=EJB3 with dependencies:
2008-06-16 15:49:39,248 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.noaa.espc.nde.dhs.ingest.ejb.MetadataExtractorBean ejbName: MetadataExtractorEJB
2008-06-16 15:49:39,263 INFO [org.jboss.ejb3.JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
2008-06-16 15:49:39,263 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=business_service-ejb.jar,name=MetadataPersistorEJB,service=EJB3 with dependencies:
2008-06-16 15:49:39,263 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.noaa.espc.nde.dhs.ingest.ejb.MetadataPersistorBean ejbName: MetadataPersistorEJB
2008-06-16 15:49:39,279 INFO [org.jboss.ejb3.EJB3Deployer] Deployed: file:/C:/jboss/jboss-soa-p.4.2.0/jboss-as/server/production/tmp/deploy/tmp39016NDE_DHS_INS.esb-contents/business_service-ejb.jar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158488#4158488
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158488
17 years, 10 months
[Tomcat, HTTPD, Servlets & JSP] - Re: Tomcat 6 comet support in 4.2.2
by jonasb
Thanks for answering.
You're referring to org.jboss.web.comet.CometProcessor, right? But that interface is not available in 4.2.2, I can only find org.apache.catalina.CometProcessor in the jbossweb jar. Also, the rename was made in january this year according to some svn commit log I found, so I guess it's in a later jbossweb than the one bundled with 4.2.2.
I tried to simply copy catalina.jar from a jbossweb 2.1.0 GA to the jboss-web deployer in my jboss 4.2.2 installation, and my "event" method was called, so I'm guessing that I need to upgrade.
However, I can't find any documentation on how to properly upgrade the version of jbossweb that is bundled with 4.2.2 to jbossweb 2.1.0. Could you help me out? Would it work to just replace the jbossweb* jars with the jars found in the lib directory of jbossweb-2.1.0?
Thanks / Jonas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158485#4158485
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158485
17 years, 10 months