[JBoss Messaging] - Problem publishing message from one Jboss server to another
by jhd
Environment:
Jboss 4.2.2
Jboss Messaging 1.4.0 SP3
Jdk 1.5.0_06
Windows XP
Two Jboss servers running on different hosts. No clustering is used for Jboss or Jboss Messaging. Server1 has a topic deployed, topic\securityReload. Server two does not.
Use case:
A message may be published from either Server1 or Server2 to topic\securityReload. If the message originates from Server1 message gets consumed successfully. If the message originates from Server2 no exceptions are observed on either server but message never gets through.
I have a stand-alone Java client that is able to send/receive messages successfully to two different queues deployed on Server1.
Why would a JMS client running in another instance of Jboss AS have trouble publishing to a topic on a remote Jboss AS?
Configuration files follow:
twia-destinations-service.xml:
| <server>
| <!-- Destination without a configured SecurityManager or without a
| a SecurityConf will default to role guest with read=true, write=true,
| create=false.
| -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=testQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="noacc" read="false" write="false" create="false"/>
| </security>
| </attribute>
| </mbean>
|
| <!-- reload destination is hosted on this server so this section is needed -->
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=securityReload"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=claimBatch"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=taskActionExecute"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=requestReply"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| </server>
|
jms-ds.xml:
| <connection-factories>
|
| <!-- ==================================================================== -->
| <!-- JMS Stuff -->
| <!-- ==================================================================== -->
|
| <!-- The JMS provider loader -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
| <!-- Uncomment to use HAJNDI to access JMS
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=localhost:1100
| </attribute>
| -->
| </mbean>
|
| <!-- The server session pool for Message Driven Beans -->
| <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
| name="jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool">
| <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
| <attribute name="PoolName">StdJMSPool</attribute>
| <attribute name="PoolFactoryClass">
| org.jboss.jms.asf.StdServerSessionPoolFactory
| </attribute>
| </mbean>
|
| <!-- bug 2370 -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=RemoteMQProvider,server=localhost">
| <attribute name="ProviderName">QueuehostJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <attribute name="QueueFactoryRef">ConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">ConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=jnp://remotehostname:1099
| </attribute>
| </mbean>
|
| <tx-connection-factory>
| <jndi-name>JmsXARemote</jndi-name>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/QueuehostJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application />
| </tx-connection-factory>
| <!-- bug 2370 -->
|
|
| <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
| <tx-connection-factory>
| <jndi-name>JmsXA</jndi-name>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| </tx-connection-factory>
|
| </connection-factories>
|
remoting-bisocket-service.xml:
| <server>
|
| <!-- Standard bisocket connector - the bisocket transport only opens connection from client->server
| so can be used with firewalls where only outgoing connections are allowed.
| For examples of HTTP and SSL transports see docs/examples -->
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <!-- End immutable parameters -->
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="numberOfRetries" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- Use these parameters to specify values for binding and connecting control connections to
| work with your firewall/NAT configuration
| <attribute name="secondaryBindPort">xyz</attribute>
| <attribute name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
| </server>
|
from standardjboss.xml:
| <invoker-proxy-bindings>
|
| <!-- bug 2370 -->
| <invoker-proxy-binding>
| <name>RemoteSecurityReloadInvoker</name>
| <invoker-mbean>default</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>QueuehostJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <CreateJBossMQDestination>false</CreateJBossMQDestination>
| <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
| <MinimumSize>1</MinimumSize>
| <MaximumSize>3</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>1</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| <!-- bug 2370 -->
|
| ...
|
from MDB deployment - jboss.xml:
| <!-- bug 2370 -->
| <message-driven>
| <ejb-name>SecurityReloadMDB</ejb-name>
| <destination-jndi-name>topic/securityReload</destination-jndi-name>
| <configuration-name>Standard Message Driven Bean</configuration-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>RemoteSecurityReloadInvoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| <!-- bug 2370 -->
|
This seems like it should be a simple configuration problem but I haven't been able to track it down.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163091#4163091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163091
17 years, 9 months
[JBoss Getting Started Documentation] - Re: Install JBOSS 4.2.2 - HELP
by nelsonrp24
Peter, Thanks very Much for you answer,
I'm Looking information in link "http://wiki.jboss.org/wiki/JBossOnPort80" but don't exist the directory "jbossweb-tomcat50.sar" in "jboss:\server\default\deploy", is It bat that?, I See two files server.xml: jboss-4.2.2.GA/server/all/deploy/jboss-web.deployer/server.xml and jboss-4.2.2.GA/server/default/deploy/jboss-web.deployer/server.xml, I did changes over those. The server running ok, but only when i open the page in the same machine, when i try open the page "http://ip_server_jboos", don't work in other pc.
I check iptables and both ports is open, port 80 and port 8080.-
PD: I work with CentOS release 5.2, JBoss 4.2.2
Thanks.-
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163079#4163079
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163079
17 years, 9 months
[Clustering/JBoss] - Re: Clustering JBoss 4.0.5, not working, stuck
by egandt
First off I turned org.jgroups to "TRACE", however I'm unsure how to read the results of this,but then I also started the 2 cluster members and attempted to probe the jgroup, as discussed at http://wiki.jboss.org/wiki/Probe:
root@oraclelinuxoracle11clusterA lib]# /opt/jdk1.6.0_02/bin/java -cp jgroups.jar org.jgroups.tests.Probe -timeout 500
java.lang.NullPointerException: null buffer || null address
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:612)
at org.jgroups.tests.Probe.start(Probe.java:33)
at org.jgroups.tests.Probe.main(Probe.java:93)
Fails so lets give it all the possible options as suggested:
[root@oraclelinuxoracle11clusterA lib]# /opt/jdk1.6.0_02/bin/java -cp jgroups.jar:commons-logging.jar org.jgroups.tests.Probe -timeout 500 -bind_addr 172.19.2.10 -port 7500 -addr 224.0.0.75
-- send probe on /224.0.0.75:7500
Find nothing, so lets change the port since the jboss log shows that it is listening at> 1099, 1100 or 1102:
JBOSS log> 23:09:04,979 INFO [DefaultPartition] I am (172.19.2.10:1099) received membershipChanged event:
JBOSS log> 23:09:04,991 INFO [DefaultPartition] Dead members: 0 ([])
JBOSS log> 23:09:05,032 INFO [DefaultPartition] New Members : 0 ([])
JBOSS log> 23:09:05,034 INFO [DefaultPartition] All Members : 1 ([172.19.2.10:1099])
JBOSS log> 23:09:05,124 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/172.19.2.10
JBOSS log> 23:09:05,187 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /172.19.2.10:1102, group=230.0.0.4, HA-JNDIaddress=172.19.2.10:1100
Ok testing on Ports 1099, 1100 or 1102 finds nothing, same as looking on port 7500, I also tried ports 1485, 1486 and 45571 since they showed up in the server.log file, this time (the 1485, 1486 and 45571 addresses change every time I restart JBoss so I'm assuming they are not what I want.
It would appear based on this information, that jgroups is not running at all, yet JBoss says its running and it shows in the server.log file when set to org.jgroup is set to TRACE. I also thought that perhaps the multicast address is wrong, but then I could not find any place in JBoss where the jgroup multicast port is set so I have no idea what it is if not the default. The only multicast set in the logs is "228.1.2.3", yet it appears in a different section and even running the probe on that address fails to find any groups.
The following chunk of the JBoss server.log when I start the second cluster member. I am not sure, but it appears that there is no connections made from the second member (to this the first member), which makes sense as probing does not even show that the jgroup is started.
| 2008-07-08 23:03:35,248 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:03:35,248 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:03:37,172 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:03:39,573 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:03:39,575 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:03:45,511 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Creating an empty ClusteredSession
| 2008-07-08 23:03:45,512 DEBUG [org.jboss.web.tomcat.tc5.session.SessionIDGenerator] getSessionId called: vTrmYfRCYsIAhMcEFPpSxA**
| 2008-07-08 23:03:45,512 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] createSession(): useJK is true. Will append JvmRoute: node2
| 2008-07-08 23:03:45,512 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Session with id=vTrmYfRCYsIAhMcEFPpSxA**.node2 added. Current active sessions 2
| 2008-07-08 23:03:45,512 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Created a ClusteredSession with id: vTrmYfRCYsIAhMcEFPpSxA**.node2
| 2008-07-08 23:03:45,559 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: vTrmYfRCYsIAhMcEFPpSxA**.node2 -- is it local? false
| 2008-07-08 23:03:45,561 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from store with id: vTrmYfRCYsIAhMcEFPpSxA**
| 2008-07-08 23:03:45,561 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from distributed store. Fqn: /JSESSION/localhost/cs/vTrmYfRCYsIAhMcEFPpSxA**
| 2008-07-08 23:03:45,561 WARN [org.jboss.cache.TreeCache] node /JSESSION/localhost/cs/vTrmYfRCYsIAhMcEFPpSxA** not found
| 2008-07-08 23:03:47,176 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:03:57,181 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:03:59,779 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:03:59,786 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:04:07,190 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:04:15,522 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Creating an empty ClusteredSession
| 2008-07-08 23:04:15,523 DEBUG [org.jboss.web.tomcat.tc5.session.SessionIDGenerator] getSessionId called: YgTiVX5lLdOoM63lthxGkQ**
| 2008-07-08 23:04:15,523 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] createSession(): useJK is true. Will append JvmRoute: node2
| 2008-07-08 23:04:15,540 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Session with id=YgTiVX5lLdOoM63lthxGkQ**.node2 added. Current active sessions 2
| 2008-07-08 23:04:15,540 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Created a ClusteredSession with id: YgTiVX5lLdOoM63lthxGkQ**.node2
| 2008-07-08 23:04:15,567 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: YgTiVX5lLdOoM63lthxGkQ**.node2 -- is it local? false
| 2008-07-08 23:04:15,568 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from store with id: YgTiVX5lLdOoM63lthxGkQ**
| 2008-07-08 23:04:15,569 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from distributed store. Fqn: /JSESSION/localhost/cs/YgTiVX5lLdOoM63lthxGkQ**
| 2008-07-08 23:04:15,570 WARN [org.jboss.cache.TreeCache] node /JSESSION/localhost/cs/YgTiVX5lLdOoM63lthxGkQ** not found
| 2008-07-08 23:04:17,200 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:04:20,494 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:04:20,495 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:04:27,237 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:04:32,946 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:04:32,962 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:04:37,242 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:04:45,519 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Creating an empty ClusteredSession
| 2008-07-08 23:04:45,520 DEBUG [org.jboss.web.tomcat.tc5.session.SessionIDGenerator] getSessionId called: wUDdoVz3jmRKktZhk2HGJQ**
| 2008-07-08 23:04:45,520 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] createSession(): useJK is true. Will append JvmRoute: node2
| 2008-07-08 23:04:45,521 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Session with id=wUDdoVz3jmRKktZhk2HGJQ**.node2 added. Current active sessions 2
| 2008-07-08 23:04:45,521 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Created a ClusteredSession with id: wUDdoVz3jmRKktZhk2HGJQ**.node2
| 2008-07-08 23:04:45,551 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: wUDdoVz3jmRKktZhk2HGJQ**.node2 -- is it local? false
| 2008-07-08 23:04:45,561 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from store with id: wUDdoVz3jmRKktZhk2HGJQ**
| 2008-07-08 23:04:45,562 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from distributed store. Fqn: /JSESSION/localhost/cs/wUDdoVz3jmRKktZhk2HGJQ**
| 2008-07-08 23:04:45,562 WARN [org.jboss.cache.TreeCache] node /JSESSION/localhost/cs/wUDdoVz3jmRKktZhk2HGJQ** not found
| 2008-07-08 23:04:47,247 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:04:53,133 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:04:53,135 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:04:53,591 DEBUG [org.jgroups.protocols.UDP]
| sending msgs:
| 230.1.2.7:45577: 1 msgs
|
| 2008-07-08 23:04:55,562 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:04:55,563 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:04:57,251 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:05:06,152 DEBUG [org.jgroups.protocols.PING] initial mbrs are []
| 2008-07-08 23:05:06,152 DEBUG [org.jgroups.protocols.MERGE2] initial_mbrs=[]
| 2008-07-08 23:05:07,258 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
| 2008-07-08 23:05:15,508 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Creating an empty ClusteredSession
| 2008-07-08 23:05:15,509 DEBUG [org.jboss.web.tomcat.tc5.session.SessionIDGenerator] getSessionId called: qt6x6A+8rq5zyFVD3EFJbg**
| 2008-07-08 23:05:15,509 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] createSession(): useJK is true. Will append JvmRoute: node2
| 2008-07-08 23:05:15,509 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Session with id=qt6x6A+8rq5zyFVD3EFJbg**.node2 added. Current active sessions 2
| 2008-07-08 23:05:15,509 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Created a ClusteredSession with id: qt6x6A+8rq5zyFVD3EFJbg**.node2
| 2008-07-08 23:05:15,519 DEBUG [org.jboss.web.tomcat.tc5.session.ClusteredSession] The session has expired with id: qt6x6A+8rq5zyFVD3EFJbg**.node2 -- is it local? false
| 2008-07-08 23:05:15,520 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Removing session from store with id: qt6x6A+8rq5zyFVD3EFJbg**
| 2008-07-08 23:05:15,521 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheService] Remove session from distributed store. Fqn: /JSESSION/localhost/cs/qt6x6A+8rq5zyFVD3EFJbg**
| 2008-07-08 23:05:15,521 WARN [org.jboss.cache.TreeCache] node /JSESSION/localhost/cs/qt6x6A+8rq5zyFVD3EFJbg** not found
| 2008-07-08 23:05:17,263 DEBUG [org.jboss.web.tomcat.tc5.session.JBossCacheManager] Looking for sessions that have expired ...
I'm just at a loss here it appears that while using the "all" profile and having followed the instructions on setting up a cluster with Apache 2.2 and modproxyhttp or modproxyajp the required jgroup is not either starting (which the log says it is) or broadcasting its existance (which seems more likely) so that other nodes can find it.
Any ideas?
ERIC
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163069#4163069
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163069
17 years, 9 months