[Clustering/JBoss] - Re: discarded message from non-member
by bmelloni
Yes, we are a support customer. I am a new employee for the company and I just requested from my boss the info needed to open a ticket.
Thank you for helping until I am able to open the formal ticket.
Your suggestion (3) to start with -b took care of the discarded message. But I still get some errors. After starting .103 first and .102 second, the following is still happening:
A) I see these errors on .102 at about a 2 minute interval:
09:02:22,093 WARN [ConnectionTable] peer closed connection, trying to re-send msg
09:02:22,093 ERROR [ConnectionTable] 2nd attempt to send data failed too
B) Deployment after placing a WAR in the farm folder seems to be horrendously slow (like if it was failing a lot, timing out, and recovering). I see the WAR file being placed in the all/tmp folder, but the byte count goes up at a crawl. In both servers logs I see quite a few debug statements for TORecoveryModule and XARecoveryModule. Once the push finally finished (after 30-60 min!) the application worked on both servers.
Here are the details you requested in your previous email:
1) I am using the default clustering configuration, since the instructions say you should get default clustering by just starting in the 'all' configuration. If that is UDP multicast, then yes.
I believe the only changes I did to the defaults are:
a) What is indicated in the post-Installation instructions (i.e.: enable the admin accounts so that I can get to the web pages.
b) Start with "-c all', to get default clustering.
c) Since I noticed that with the defaults I couldn't access the server by IP, after I capture the logs I posted, I changed the start to include '-b '.
2)
=====================
Log snippet from .103:
=====================
08:51:58,433 INFO [ServerInfo] Java version: 1.6.0_11,Sun Microsystems Inc.
08:51:58,433 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.0-b16,Sun Microsystems Inc.
08:51:58,433 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
08:51:58,824 INFO [Server] Core system initialized
08:52:02,621 INFO [WebService] Using RMI server codebase: http://192.168.11.103:8083/
08:52:02,621 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
08:52:03,058 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
08:52:03,058 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
08:52:03,168 INFO [TransactionManagerService] Starting recovery manager
08:52:03,215 INFO [TransactionManagerService] Recovery manager started
08:52:03,215 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
08:52:07,996 INFO [EJB3Deployer] Starting java:comp multiplexer
08:52:09,840 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.103:1733
-------------------------------------------------------
08:52:11,871 INFO [TreeCache] viewAccepted(): [192.168.11.103:1733|0] [192.168.11.103:1733]
08:52:11,918 INFO [TreeCache] TreeCache local address is 192.168.11.103:1733
08:52:11,918 INFO [TreeCache] State could not be retrieved (we are the first member in group)
08:52:11,918 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
08:52:12,074 INFO [STDOUT] no object for null
08:52:12,074 INFO [STDOUT] no object for null
08:52:12,121 INFO [STDOUT] no object for null
08:52:12,137 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
08:52:12,137 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
08:52:16,480 INFO [NativeServerConfig] JBoss Web Services - Native
08:52:16,496 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
08:52:18,090 INFO [SnmpAgentService] SNMP agent going active
08:52:18,433 INFO [DefaultPartition] Initializing
08:52:18,465 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.103:1738
-------------------------------------------------------
08:52:20,480 INFO [DefaultPartition] Number of cluster members: 1
08:52:20,480 INFO [DefaultPartition] Other members: 0
08:52:20,480 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
08:52:20,480 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
08:52:20,543 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/192.168.11.103
08:52:20,558 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /192.168.11.103:1102, group=230.0.0.4, HA-JNDI addr
ess=192.168.11.103:1100
08:52:20,933 INFO [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
08:52:21,027 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.103:1742
-------------------------------------------------------
08:52:23,043 INFO [TreeCache] viewAccepted(): [192.168.11.103:1742|0] [192.168.11.103:1742]
08:52:23,043 INFO [TreeCache] TreeCache local address is 192.168.11.103:1742
08:52:23,324 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.103:1746
-------------------------------------------------------
08:52:25,324 INFO [TreeCache] viewAccepted(): [192.168.11.103:1746|0] [192.168.11.103:1746]
08:52:25,324 INFO [TreeCache] TreeCache local address is 192.168.11.103:1746
================================
Snippet from .102:
================================
09:01:43,031 INFO [ServerInfo] Java version: 1.6.0_10,Sun Microsystems Inc.
09:01:43,031 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.0-b15,Sun Microsystems Inc.
09:01:43,031 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
09:01:43,531 INFO [Server] Core system initialized
09:01:45,359 INFO [WebService] Using RMI server codebase: http://192.168.11.102:8083/
09:01:45,359 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
09:01:45,750 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
09:01:45,750 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
09:01:45,921 INFO [TransactionManagerService] Starting recovery manager
09:01:45,968 INFO [TransactionManagerService] Recovery manager started
09:01:45,968 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
09:01:47,781 INFO [EJB3Deployer] Starting java:comp multiplexer
09:01:49,296 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.102:1577
-------------------------------------------------------
09:01:51,515 INFO [TreeCache] viewAccepted(): [192.168.11.103:1733|1] [192.168.11.103:1733, 192.168.11.102:1577]
09:01:51,578 INFO [TreeCache] TreeCache local address is 192.168.11.102:1577
09:01:51,640 INFO [TreeCache] received the state (size=1024 bytes)
09:01:51,656 INFO [TreeCache] state was retrieved successfully (in 78 milliseconds)
09:01:51,656 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
09:01:51,703 INFO [STDOUT] no object for null
09:01:51,703 INFO [STDOUT] no object for null
09:01:51,718 INFO [STDOUT] no object for null
09:01:51,750 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
09:01:51,765 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
09:01:53,000 INFO [NativeServerConfig] JBoss Web Services - Native
09:01:53,000 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
09:01:53,453 INFO [SnmpAgentService] SNMP agent going active
09:01:53,687 INFO [DefaultPartition] Initializing
09:01:53,718 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.102:1583
-------------------------------------------------------
09:02:00,562 INFO [DefaultPartition] Number of cluster members: 2
09:02:00,562 INFO [DefaultPartition] Other members: 1
09:02:00,562 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
09:02:00,750 INFO [DefaultPartition] state was retrieved successfully (in 188 milliseconds)
09:02:00,953 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/192.168.11.102
09:02:00,953 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /192.168.11.102:1102, group=230.0.0.4, HA-JNDI addr
ess=192.168.11.102:1100
09:02:01,218 INFO [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
09:02:01,312 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.102:1589
-------------------------------------------------------
09:02:03,578 INFO [TreeCache] viewAccepted(): [192.168.11.103:1742|1] [192.168.11.103:1742, 192.168.11.102:1589]
09:02:03,640 INFO [TreeCache] TreeCache local address is 192.168.11.102:1589
09:02:03,734 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.11.102:1594
-------------------------------------------------------
09:02:06,031 INFO [TreeCache] viewAccepted(): [192.168.11.103:1746|1] [192.168.11.103:1746, 192.168.11.102:1594]
09:02:06,093 INFO [TreeCache] TreeCache local address is 192.168.11.102:1594
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203345#4203345
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203345
17 years, 5 months
[Microcontainer] - bean undeployment in server (as5/jboss mc) shutdown
by emmartins
I have a bean that is injected with the RealTransactionManager from JBoss AS5, and a second bean that is injected with the first one, and when I shutdown the server the RealTransactionManager is removed from the first bean before the second one undeploy completes, how can I avoid that behavior? I tried to add a for RealTransactionManager in the second one but it doesn't do any good...
This is the beans xml:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:bean-deployer:2.0">
|
| <bean name="Mobicents.JAINSLEE.TransactionManagerMBean"
| class="org.mobicents.slee.runtime.transaction.SleeTransactionManagerImpl">
| <!-- jboss as tx manager bean -->
| <property name="transactionManager"><inject bean="RealTransactionManager"/></property>
| </bean>
|
| <bean name="Mobicents.JAINSLEE.SleeManagement"
| class="org.mobicents.slee.container.management.jmx.SleeManagementMBeanImpl">
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="slee:service=SleeManagement",exposedInterface=org.mobicents.slee.container.management.jmx.SleeManagementMBeanImplMBean.class, registerDirectly=true)</annotation>
| <property name="sleeTransactionManager"><inject bean="Mobicents.JAINSLEE.TransactionManagerMBean"/></property>
| </bean>
|
|
| <!-- ... -->
|
| </deployment>
|
Thanks in advance :)
-- Eduardo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203334#4203334
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203334
17 years, 5 months
[EJB/JBoss] - Deploying multiple ears with
by hamtho2
Hi,
I am currently facing the following problem:
I need to configure my ear for multiple environments. Therefor I used the hibernate.properties in the root folder of the ear to configure my persistence-layer. This works perfectly so far, because Hibernate finds the properties through itôs Environment and loads them.
BUT:
if I now deploy another ear, holding a hibernate.properties for configuring the second application, the hibernate.properties are simply ignored and - even more - the hibernate.properties from the first deployment are used for my second deployment as well.
While looking in the Hibernate source code I saw that the corresponding variable is defined as a static variable.
private static final Properties GLOBAL_PROPERTIES;
It seems as if this class will be loaded only once and the first deployment wins. I already tried to work with isolated classloaders and set the value for
| <attribute name="Isolated">true</attribute>
|
in the ear-deployer.xml to false. But this didnÃÂôt make any difference.
Does anyone has an idea how to use multiple hibernate.properties or any other way to handle multiple configurations for the persistence-layer?
Thanks for any input
Thomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203330#4203330
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203330
17 years, 5 months
[Persistence, JBoss/CMP, Hibernate, Database] - Re: XAException XAER_DUPID in CMP EJB finder invoked from a
by torf
Hi,
yes, it was solved somehow, but unfortunately i don't know how.
It is still running on JBoss 4.0.4GA. Maybe it works due to a newer Informix JDBC driver (we are using 3.00 JC3 now)?
Or maybe the datasource config was changed. It currently looks like this:
<?xml version="1.0" encoding="UTF-8"?>
| <datasources>
| <xa-datasource>
| <jndi-name>SystemDefaultDS</jndi-name>
| <xa-datasource-class>com.informix.jdbcx.IfxXADataSource</xa-datasource-class>
| <xa-datasource-property name="IfxIFXHOST">...</xa-datasource-property>
| <xa-datasource-property name="PortNumber">1723</xa-datasource-property>
| <xa-datasource-property name="DatabaseName">system_default_02</xa-datasource-property>
| <xa-datasource-property name="ServerName">zap_db_net</xa-datasource-property>
| <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
| <user-name>...</user-name>
| <password>...</password>
| <track-connection-by-tx>true</track-connection-by-tx>
| <prepared-statement-cache-size>100</prepared-statement-cache-size>
| <isSameRM-override-value>false</isSameRM-override-value>
| <no-tx-separate-pools/>
| <new-connection-sql>set lock mode to wait</new-connection-sql>
| <check-valid-connection-sql>set lock mode to wait</check-valid-connection-sql>
| <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorter</exception-sorter-class-name>
| <!--pooling parameters-->
| <min-pool-size>1</min-pool-size>
| <max-pool-size>50</max-pool-size>
| <blocking-timeout-millis>5000</blocking-timeout-millis>
| <idle-timeout-minutes>5</idle-timeout-minutes>
| <metadata>
| <type-mapping>InformixDB</type-mapping>
| </metadata>
| </xa-datasource>
| </datasources>
|
I'm sorry that i cannot be more helpful.
Christoph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203329#4203329
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203329
17 years, 5 months