[JBoss Messaging Users] - Re: Conterpart of UIL2XAConnectionFactory?
by Marco.Pehla
Here is the configuration file from JBoss MQ.
uil2-service.xml:
<server>
|
| <!-- JBossMQ using the Unified Invocation Layer
| All communication uses one socket connection -->
|
| <mbean code="org.jboss.mq.il.uil2.UILServerILService"
| name="jboss.mq:service=InvocationLayer,type=UIL2">
|
| <!-- The server chain -->
| <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
| <!-- JNDI binding -->
| <attribute name="ConnectionFactoryJNDIRef">ConnectionFactory</attribute>
| <!-- JNDI binding for XA -->
| <attribute name="XAConnectionFactoryJNDIRef">XAConnectionFactory</attribute>
| <!-- The bind address -->
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| <!-- The bind port -->
| <attribute name="ServerBindPort">8093</attribute>
| <!-- The ping period in millis -->
| <attribute name="PingPeriod">60000</attribute>
| <!-- Whether tcp/ip does not wait for buffer fills -->
| <attribute name="EnableTcpNoDelay">true</attribute>
| <!-- Used to disconnect the client on the serverside if there is no activity -->
| <!-- Ensure this is greater than the ping period -->
| <attribute name="ReadTimeout">120000</attribute>
| <!-- Used to disconnect the client on the clientside if there is no activity -->
| <!-- Ensure this is greater than the ping period -->
| <attribute name="ClientReadTimeout">120000</attribute>
| <!-- The size of the buffer (in bytes) wrapping the socket -->
| <!-- The buffer is flushed after each request -->
| <attribute name="BufferSize">2048</attribute>
| <!-- Large messages may block the ping/pong -->
| <!-- A pong is simulated after each chunk (in bytes) for both reading and writing -->
| <!-- It must be larger than the buffer size -->
| <attribute name="ChunkSize">1000000</attribute>
| </mbean>
|
| <!-- Aliases UIL -> UIL2 for backwards compatibility
| the deprecated UIL deployment can be found in docs/examples/jca -->
| <mbean code="org.jboss.naming.NamingAlias" name="jboss.mq:service=InvocationLayer,type=UIL">
| <attribute name="FromName">UILConnectionFactory</attribute>
| <attribute name="ToName">ConnectionFactory</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| <mbean code="org.jboss.naming.NamingAlias" name="jboss.mq:service=InvocationLayer,type=UILXA">
| <attribute name="FromName">UILXAConnectionFactory</attribute>
| <attribute name="ToName">XAConnectionFactory</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| <mbean code="org.jboss.naming.NamingAlias"
| name="jboss.mq:service=InvocationLayer,type=UIL2,alias=UIL2ConnectionFactory">
| <attribute name="FromName">UIL2ConnectionFactory</attribute>
| <attribute name="ToName">ConnectionFactory</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| <mbean code="org.jboss.naming.NamingAlias"
| name="jboss.mq:service=InvocationLayer,type=UIL2XA,alias=UIL2XAConnectionFactory">
| <attribute name="FromName">UIL2XAConnectionFactory</attribute>
| <attribute name="ToName">XAConnectionFactory</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| <!--
| Two JNDI bindings that act like jms client connections remotely
| but have j2ee defined semantics inside JBoss
| -->
| <mbean code="org.jboss.naming.LinkRefPairService"
| name="jboss.jms:alias=QueueConnectionFactory">
| <attribute name="JndiName">QueueConnectionFactory</attribute>
| <attribute name="RemoteJndiName">ConnectionFactory</attribute>
| <attribute name="LocalJndiName">java:/JmsXA</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| <mbean code="org.jboss.naming.LinkRefPairService"
| name="jboss.jms:alias=TopicConnectionFactory">
| <attribute name="JndiName">TopicConnectionFactory</attribute>
| <attribute name="RemoteJndiName">ConnectionFactory</attribute>
| <attribute name="LocalJndiName">java:/JmsXA</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| </server>
As you can see, we find the implementation of the MBean in the class org.jboss.mq.il.uil2.UILServerILService. An alias UIL2XAConnectionFactory is defined and refers to XAConnectionFactory.
Is it possible to do something similar with JBoss Messaging?
Thank you in advance.
regards
Marco
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269811#4269811
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269811
16 years, 4 months
[jBPM Users] - Re: How a pass signal from state a task or java?? I do not u
by cmjhingeniero
Thanks for answering
I want that when "response" comes in N get out of the event and pass the task, "hello". The variable "response" is filled with
| response = reposicion.verificarCarguePorReposicion(documento, caf); //RETURN N or S
|
I this error when I go out the signal executionService.signalExecutionById (execution.getId ());
When I remove executionService.signalExecutionById (execution.getId ()); I stay in an endless cycle that never goes to the next task
| public void notify(EventListenerExecution executionListener) throws Exception {
| String response = executionListener.getVariable("response")+"";
| if (response.equals(null)) {
| response = new String();
| executionListener.setVariable("response", response);
| }
| ReposicionDao reposicion = new ReposicionDao();
| response = reposicion.verificarCarguePorReposicion(documento, caf); //RETURN N or S
| if (processEngine == null) {
| processEngine = Configuration.getProcessEngine();
| executionService = processEngine.getExecutionService();
| }
| ProcessInstance processInstance = executionService.findProcessInstanceById(executionListener.getId
| ());
| Execution execution = processInstance.findActiveExecutionIn("verify");
| System.out.println("===>"+execution.getId());
| //WHEN response IS EQUAL TO N I MOVE TO ANOTHER TASK AND GET OUT OF THE TIMER
| if(executionListener.getVariable("response").toString().equals("N")){
| processInstance = executionService.signalExecutionById(execution.getId());
| }
| }
|
I hope having explained
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269789#4269789
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269789
16 years, 4 months