[JCA/JBoss] - Re: Possible failure to cleanup connection when returned to
by tapina
Actually I'm not sure it would.
The physical and logical connections are both in the same autocommit state (FALSE) at the time of the set transaction isolation call. Inbetween, the logical connection had autocommit TRUE but this was not applied to the physical connection at the time because no other methods were called on the connection whilst it was logically in this state. If the connection has not been committed or rolled back explicitly, then a newly returned connection could be part of an old transaction, I think.
Is there a reason why set autocommit is not passed down to the physical connection immediately but instead checked on every other call and passed down then?
The more I think about this the more I think such a fundamental mistake probably wasn't made and my interpretation is wrong.. but I'd love it if someone could put my mind to rest!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236932#4236932
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236932
16 years, 10 months
[EJB/JBoss] - Error readind from a MDB (v 2.1) on a remote Topic
by Chopper
Hello, my name is Giuseppe,
This is the situation:
I have 2 JBoss installed on my PC (kubuntu 9.04).
JBoss A (v 4.2.3) updated with Messaging and JBoss B (v 5.0.0, native Messaging, JBPM installed).
With this commands i obtain 2 "virtual" ip address on my pc:
sudo ip addr add 192.168.0.203 dev lo
sudo ip addr add 192.168.0.209 dev lo
A Java web application with servlet must be deployed on JBoss A: it sends messages on a topic.
I made this topic adding this code to the file destination-services.xml into directory...deploy/messaging of JBoss A
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=pyTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
then i added into jms-ds.xml in JBoss B the following JMSProvider:
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider,server=http://192.168.0.203">
| <attribute name="ProviderName">RemoteJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <!-- The connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <!-- Connect to JNDI on the host "the-remote-host-name" port 1099-->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=192.168.0.203:1099
| </attribute>
| </mbean>
|
and Into my standardjboss.xml (JBoss B) i added an
| <invoker-proxy-binding>
| <name>my-mdb-invoker</name>
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>RemoteJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
finally in jboss.xml (into the MDB) i have something like this:
| <?xml version="1.0" encoding="UTF-8"?>
| <jboss>
| <enterprise-beans>
| <message-driven>
| <ejb-name>NotificationHandlerBean</ejb-name>
| <destination-jndi-name>topic/pyTopic</destination-jndi-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>my-mdb-invoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| </enterprise-beans>
| </jboss>
|
|
I used Netbeans 6.5.1 developing both Sender (servlet) and Receiver (MDB) application.
Now i execute jbossA on 192.168.0.203 and jbossB on 192.168.0.209..
I tryed different solution but the error seems to be always the same:
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:binding=my-mdb-invoker,jndiName=local/NotificationHandlerBean@2732525,plugin=invoker,service=EJB -> org.jboss.deployment.DeploymentException: Themessage-destination 'pyTopic' has no jndi-name in jboss.xml
Please help me..i'm in trouble!!!
Thanks a lot...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236924#4236924
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236924
16 years, 10 months
[JNDI/Naming/Network] - JNDI Error reading on remote Topic
by Chopper
Hello, my name is Giuseppe,
This is the situation:
I have 2 JBoss installed on my PC (kubuntu 9.04).
JBoss A (v 4.2.3) updated with Messaging and JBoss B (v 5.0.0, native Messaging, JBPM installed).
With this commands i obtain 2 "virtual" ip address on my pc:
sudo ip addr add 192.168.0.203 dev lo
sudo ip addr add 192.168.0.209 dev lo
A Java web application with servlet must be deployed on JBoss A: it sends messages on a topic.
I made this topic adding this code to the file destination-services.xml into directory...deploy/messaging of JBoss A
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=pyTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
then i added into jms-ds.xml in JBoss B the following JMSProvider:
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider,server=http://192.168.0.203">
| <attribute name="ProviderName">RemoteJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <!-- The connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <!-- Connect to JNDI on the host "the-remote-host-name" port 1099-->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=192.168.0.203:1099
| </attribute>
| </mbean>
|
and Into my standardjboss.xml (JBoss B) i added an
| <invoker-proxy-binding>
| <name>my-mdb-invoker</name>
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>RemoteJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
finally in jboss.xml (into the MDB) i have something like this:
| <?xml version="1.0" encoding="UTF-8"?>
| <jboss>
| <enterprise-beans>
| <message-driven>
| <ejb-name>NotificationHandlerBean</ejb-name>
| <destination-jndi-name>topic/pyTopic</destination-jndi-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>my-mdb-invoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| </enterprise-beans>
| </jboss>
|
|
I used Netbeans 6.5.1 developing both Sender (servlet) and Receiver (MDB) application.
Now i execute jbossA on 192.168.0.203 and jbossB on 192.168.0.209..
I tryed different solution but the error seems to be always the same:
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:binding=my-mdb-invoker,jndiName=local/NotificationHandlerBean@2732525,plugin=invoker,service=EJB -> org.jboss.deployment.DeploymentException: Themessage-destination 'pyTopic' has no jndi-name in jboss.xml
Please help me..i'm in trouble!!!
Thanks a lot...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236923#4236923
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236923
16 years, 10 months