[Clustering/JBoss] - Different GMS addresses for JGroups and TreeCache
by morki
hi
i recently set up a two-node cluster with one instance of jboss running on a vm. seems as everything works just fine. that means that the nodes find each other and jgroups recognizes changes in the current view.
therefore i had to edit the cluster-service.xml in order to set bind_addr to my local address. otherwise it didn't work.
we have a huge and very complex software system for swing-clients running and i just wanted to try to cluster a single ejb. our ejbs are still version 2.1 so i just changed some settings in the deployment descriptor and so added the jndi-name and the clustered tag.
i then started the application. but failing over didn't work with the second server. an exception was raised.
probably there's a mistake in my configuration concering the mentioned bind_addr for the udp protocol stack.
i get these loggings from the server that doesn't run in the vm. as you can see the ip addresses bound to both treecache and protocol stack don't equal whereas on the server in the vm both ip addresses are identical. what have i done wrong?
===============================================================================
| .
| JBoss Bootstrap Environment
| .
| JBOSS_HOME: D:\workspace\profilcs\dist\jboss\bin\\..
| .
| JAVA: D:\Development\tools\java\jdk15\bin\java
| .
| JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=128m -Dsun.rmi.dgc.client.gcInterval=3600
| 000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xnoclassgc -enableassertions -Djava.security.policy=..\server\deg\conf\serv
| er.policy -Ddeg.no.scheduler.lock=true -Dorg.jboss.security.SecurityAssociation.ThreadLocal=true -Djava.awt.headless=tru
| e
| .
| CLASSPATH: D:\Development\tools\java\jdk15\lib\tools.jar;D:\workspace\profilcs\dist\jboss\bin\\run.jar
| .
| ===============================================================================
| .
| 12:45:00,562 INFO [Server] Starting JBoss (MX MicroKernel)...
| 12:45:00,578 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)
| 12:45:00,578 INFO [Server] Home Dir: D:\workspace\profilcs\dist\jboss
| 12:45:00,578 INFO [Server] Home URL: file:/D:/workspace/profilcs/dist/jboss/
| 12:45:00,578 INFO [Server] Patch URL: null
| 12:45:00,578 INFO [Server] Server Name: deg1
| 12:45:00,578 INFO [Server] Server Home Dir: D:\workspace\profilcs\dist\jboss\server\deg1
| 12:45:00,578 INFO [Server] Server Home URL: file:/D:/workspace/profilcs/dist/jboss/server/deg1/
| 12:45:00,578 INFO [Server] Server Log Dir: D:\workspace\profilcs\dist\jboss\server\deg1\log
| 12:45:00,578 INFO [Server] Server Temp Dir: D:\workspace\profilcs\dist\jboss\server\deg1\tmp
| 12:45:00,578 INFO [Server] Root Deployment Filename: jboss-service.xml
| 12:45:01,250 INFO [ServerInfo] Java version: 1.5.0_10,Sun Microsystems Inc.
| 12:45:01,250 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_10-b03,Sun Microsystems Inc.
| 12:45:01,250 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
| 12:45:02,671 INFO [Server] Core system initialized
| 12:45:34,871 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8123/
| 12:45:35,136 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
| log4j:WARN Continuable parsing error 298 and column 23
| log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,appender*,(category|logger)*,root?,c
| ategoryFactory?)".
| 12:45:37,323 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
| 12:45:37,323 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
| 12:45:38,854 INFO [TransactionManagerService] Starting recovery manager
| 12:45:39,651 INFO [TransactionManagerService] Recovery manager started
| 12:45:39,651 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
| 12:45:49,681 INFO [EJB3Deployer] Starting java:comp multiplexer
| 12:45:52,493 INFO [InterceptorChainFactory] interceptor chain is:
| class org.jboss.cache.interceptors.CallInterceptor
| class org.jboss.cache.interceptors.PessimisticLockInterceptor
| class org.jboss.cache.interceptors.UnlockInterceptor
| class org.jboss.cache.interceptors.ReplicationInterceptor
| class org.jboss.cache.interceptors.TxInterceptor
| class org.jboss.cache.interceptors.CacheMgmtInterceptor
| 12:45:52,572 INFO [JChannel] JGroups version: 2.4.1 SP-3
| 12:45:53,228 INFO [FRAG2] frag_size=60000, overhead=200, new frag_size=59800
| 12:45:53,400 INFO [UDP] sockets will use interface 192.168.139.1
| 12:45:53,415 INFO [UDP] socket information:
| local_addr=192.168.139.1:2875, mcast_addr=230.1.2.7:45577, bind_addr=/192.168.139.1, ttl=2
| sock: bound to 192.168.139.1:2875, receive buffer size=20000000, send buffer size=640000
| mcast_recv_sock: bound to 192.168.139.1:45577, send buffer size=640000, receive buffer size=25000000
| mcast_send_sock: bound to 192.168.139.1:2876, send buffer size=640000, receive buffer size=25000000
| 12:45:53,462 INFO [STDOUT]
| -------------------------------------------------------
| GMS: address is 192.168.139.1:2875
| -------------------------------------------------------
| 12:45:55,540 INFO [TreeCache] viewAccepted(): [192.168.139.1:2875|0] [192.168.139.1:2875]
| 12:45:55,587 INFO [TreeCache] TreeCache local address is 192.168.139.1:2875
| 12:45:55,587 INFO [TreeCache] State could not be retrieved (we are the first member in group)
| 12:45:55,587 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
| 12:46:00,508 INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756)
| 12:46:04,633 INFO [SnmpAgentService] SNMP agent going active
| 12:46:06,367 INFO [JChannel] JGroups version: 2.4.1 SP-3
| 12:46:06,414 INFO [FRAG2] frag_size=60000, overhead=200, new frag_size=59800
| 12:46:06,414 INFO [FRAG2] received CONFIG event: {bind_addr=/92.1.5.63}
| 12:46:06,773 INFO [DefaultPartition] Initializing
| 12:46:06,851 INFO [UDP] sockets will use interface 92.1.5.63
| 12:46:06,851 INFO [UDP] socket information:
| local_addr=92.1.5.63:2885, mcast_addr=228.1.2.3:45577, bind_addr=/92.1.5.63, ttl=2
| sock: bound to 92.1.5.63:2885, receive buffer size=20000000, send buffer size=640000
| mcast_recv_sock: bound to 92.1.5.63:45577, send buffer size=640000, receive buffer size=25000000
| mcast_send_sock: bound to 92.1.5.63:2886, send buffer size=640000, receive buffer size=25000000
| 12:46:06,867 INFO [STDOUT]
| -------------------------------------------------------
| GMS: address is 92.1.5.63:2885
| -------------------------------------------------------
| 12:46:09,023 INFO [DefaultPartition] Number of cluster members: 1
| 12:46:09,038 INFO [DefaultPartition] Other members: 0
| 12:46:09,038 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
| 12:46:09,038 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
| 12:46:09,116 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/127.0.0.1
| 12:46:09,132 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI a
| ddress=127.0.0.1:1100
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057652#4057652
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057652
19Â years
[JBossWS] - Re: MTOM + WS Security = problem
by davideling
This time I'm trying a simpler example
MTOM/WS-Security onl with username and password
In my service client,
if I comment out
// ((StubExt) port).setConfigName("Standard WSSecurity Client");
I get MTOM work correctly
| POST /servizioJBossWSSEAttachment/ServizioWSSEAttachment?datatype=JBossWSMessage HTTP/1.1
| Authorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3Jk
| SOAPAction: ""
| Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart(a)ws.jboss.org>";
| start-info="text/xml";
| boundary="----=_Part_0_31571602.1182853646985"
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.0 SP4 (Bluto)
| Host: localhost:8181
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Content-Length: 453280
|
|
| ------=_Part_0_31571602.1182853646985
| Content-Type: application/xop+xml; type="text/xml"
| Content-Transfer-Encoding: 8bit
| Content-ID: <rootpart(a)ws.jboss.org>
|
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns1:inputMessage xmlns:ns1="http://www.tai.it/ServizioWSSEAttachment"><attachment><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:attachment-6707b7bd-51d9-4d4f-b133-f0a4774a2874@ws.jboss.org"/></attachment><name>Davide</name><surname>Ling</surname></ns1:inputMessage></env:Body></env:Envelope>
| ------=_Part_0_31571602.1182853646985
| Content-Type: application/octet-stream
| Content-Transfer-Encoding: binary
| Content-Id: <attachment-6707b7bd-51d9-4d4f-b133-f0a4774a2874(a)ws.jboss.org>
|
| %PDF-1.4
| blablabla...
|
But if I enable WS-Security MTOM doesn't work any more.
The client doesn't send a multipart related message,
but inserts the xop:include tag with the attachment reference.
I use JBoss 4.2.0 GA, JDK 1.5.0_12 on Linux 32 bit
| POST /servizioJBossWSSEAttachment/ServizioWSSEAttachment?datatype=JBossWSMessage HTTP/1.1
| Authorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3Jk
| SOAPAction: ""
| Content-Type: text/xml; charset=UTF-8
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.0 SP4 (Bluto)
| Host: localhost:8181
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Content-Length: 828
|
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
| <env:Header>
| <wsse:Security env:mustUnderstand='1' ... >
| <wsse:UsernameToken wsu:Id='token-1-1182854743065-9708927'>
| <wsse:Username>myusername</wsse:Username>
| <wsse:Password>mypassword</wsse:Password>
| </wsse:UsernameToken></wsse:Security>
| </env:Header>
| <env:Body>
| <ns1:inputMessage xmlns:ns1='http://www.tai.it/ServizioWSSEAttachment'>
| <attachment>
| <xop:Include href='cid:attachment-f4e31927-67ed-4162-8a0e-86e53e96b316@ws.jboss.org' xmlns:xop='http://www.w3.org/2004/08/xop/include'/>
| </attachment>
| <name>Davide</name>
| <surname>Ling</surname>
| </ns1:inputMessage>
| </env:Body>
| </env:Envelope>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057646#4057646
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057646
19Â years