April 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Thread pools...

by clebert.suconic＠jboss.com

During the process of looking for the QueueControl leak today, the profiler was indirectly showing lots references on RemotingConnectionImpl, going through two static fields, that are using some sort of thread pool: - InVMConnection::factory - ConnectionManagerImpl::pingExecutor The references were aways inside the method. Probably those references would be gone as soon as the pool is used, but it would be much easier to cleanup leaks if we aways recreate those pools on tearDowns(). (a simple kill -3 would show a cleaned memory if setting the dump-memory option on the VM) I was thinking about creating a method named recreatePingExecutor on ConnectionManagerImpl and another named recreateFactory on InVMConnection, and those methods would be marked to be used by tests only. Is there a problem on that approach? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225416#4225416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225416

16 years, 12 months

1
0
0 / 0

[Design of JBoss ESB] - jbossESB4.5+jbpm3.2+pop3

by ailing.qin

Hello, I went to receive the email in my jbpm, so, i create a service in jboss-esb.xml, the code of jboss-esb.xml like this: <services> | <service category="Architecture-Journal" | name="MailProcUsingJCAAndjBPM" | description="Exemplo de Gateway POP e processamento com jBPM"> | <jca-gateway name="mailListener" | adapter="mail-ra.rar" endpointClass="com.aj.soa.jbossesb.gateways.JBossESBMailGateway" | is-gateway="true" | transacted="false"> | <activation-config> | <property name="mailServer" value="pop3.toto.fr" /> | <property name="storeProtocol" value="imap" /> | <property name="mailFolder" value="inbox" /> | <property name="userName" value="test(a)toto.fr" /> | <property name="password" value="test" /> | <property name="pollingInterval" value="5000" /> | </activation-config> | </jca-gateway> | <jms-listener name="jmsListener" | busidref="mailProcJmsChannel" | maxThreads="1" /> | <action name="execute-process" class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor"> | <property name="command" value="StartProcessInstanceCommand" /> | <property name="process-definition-name" value="ticketManagements" /> | <property name="esbToBpmVars"> | <mapping esb="BODY_CONTENT" bpm="theBody"/> | </property> | </action> and my processdefinition.xml like this: <node name="Receive mail"> | <action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler"> | <esbCategoryName>Architecture-Journal</esbCategoryName> | <esbServiceName>MailProcUsingJCAAndjBPM</esbServiceName> | <bpmToEsbVars> | <mapping bpm="theBody" esb="BODY_CONTENT" /> | </bpmToEsbVars> | <esbToBpmVars> | <mapping esb="BODY_CONTENT" bpm="theBody"/> | </esbToBpmVars> | </action> | <transition to="Analyse" name="trAnalyse"></transition> | </node> when I try run the process in jbpm-console,I got error [17:32:02,436 ERROR [GraphElement] action threw exception: org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler | java.lang.ClassCastException: org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler | at org.jbpm.graph.def.Action.execute(Action.java:121) | 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.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) | at org.jbpm.graph.def.Action_$$_javassist_150.execute(Action_$$_javassist_150.java) | at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:255) | at org.jbpm.graph.def.Node.execute(Node.java:338) | at org.jbpm.graph.def.Node.enter(Node.java:318) | 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.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) | at org.jbpm.graph.def.Node_$$_javassist_136.enter(Node_$$_javassist_136.java) | at org.jbpm.graph.def.Transition.take(Transition.java:151) | at org.jbpm.graph.def.Node.leave(Node.java:393) | at org.jbpm.graph.node.StartState.leave(StartState.java:70) | 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.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) | at org.jbpm.graph.def.Node_$$_javassist_136.leave(Node_$$_javassist_136.java) | at org.jbpm.graph.exe.Token.signal(Token.java:194) | at org.jbpm.graph.exe.Token.signal(Token.java:157) | at org.jbpm.jsf.core.action.SignalActionListener.handleAction(SignalActionListener.java:56) | at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82) | at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88) | at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:771) | at javax.faces.component.UICommand.broadcast(UICommand.java:372) | at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) | at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) | at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82) | at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) | at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) | at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595)] Thanks in advance! anonymous wrote : View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225397#4225397 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225397

16 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: schema for mail template and activity

by bradsdavis

I would have really liked the templates to be defined in the same way as in the jPDL. If you think about it, templates really are just mail nodes that have been externalized from the process definition. Keeping then consistent with jPDL would have allowed people to pick that up pretty easily. However, if we want to have a seperate language for templates, I think what you are doing looks good. My only suggestion from the last post is that the producer attribute be moved within the template as well. This will allow users to change the email template type outside of deploying a new process. @tom: I think making it body-text and body-html would be fine. I also agree that attachments should have a name element. Also Tom, I can install skype if you want to walk over the basis for producers. I also have written a bit of documentation thats in the email_branch if you check it out and package the documentation module. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225378#4225378 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225378

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Heuristic Example --- We are not ready for it?

by gaohoward

OK, I understand now. Thanks Tim/Clebert. Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225366#4225366 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225366

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Heuristic Example --- We are not ready for it?

by clebert.suconic＠jboss.com

The Heuristic API was prepared for a Human. That means: - You list the XIDs... - You read the report... - You type (or copy & paste) the XID String - You call the method on an admin console. Doing that on an example is going to be a challenge... unless you give instructions to the user on how to interact with the Console, which would be a good idea. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225363#4225363 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225363

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Heuristic Example --- We are not ready for it?

by timfox

That's not the the purpose of the heuristic XA example. With this example the idea is to a) Start and prepare one or more transactions, do not commit or roll them back yet. b) List the transactions in prepared state. c) Heuristically roll back or commit, via the management interface View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225361#4225361 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225361

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Heuristic Example --- We are not ready for it?

by gaohoward

I'm taking "heuristic commit/rollback example" as listed in the wiki page. So for this example I need to figure out what to show to the users about heuristic scenario -- get a heuristic exception thrown and handle it by forget() call. So I need to create a scenario with JBM XASession where the xa commit() on XAResource can throw a heuristic exception. Then I'll tell the xa resource to forget about this transaction. I investigated out code and found it's not possible to simulate this process. So probably we drop this example for the moment? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225355#4225355 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225355

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE in transaction commit

by timfox

"clebert.suconic(a)jboss.com" wrote : [ | | We could have the example downloading it from the repo.. http-get. | Yes we could do that. How about we have two XA examples, one that uses the tx mgr and one that does not (which Howard has already done) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225352#4225352 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225352

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken

by clebert.suconic＠jboss.com

"timfox" wrote : ... and paging Paging started failing after one of the refactoring on clustering. We talked about that before and you asked me to look at it after Beta, so I raised a JIRA. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225349#4225349 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225349

16 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken (Repost)

by clebert.suconic＠jboss.com

"timfox" wrote : The only failover tests with significant failures are related to large messages and paging, which are both your areas. | | The other failover tests I can run hundreds of times in a loop without failure. | | They need to be fixed. The only reason the other failover tests are not failing is because of the size of the messages. I used to run them hundreds of times also, and some of the recent changes broke them. I will fix them before commit of my changes today. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225346#4225346 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225346

16 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009