[Clustering/JBoss] - Re: Cluster members don't see each other
by nitesh
I ran the jgroups Probe utility on the cluster and this is what I found. There are two group-names "Tomcat-Cluster" and "DefaultPartition". While "Tomcat-Cluster" sees both the JBoss nodes, "DefaultPartition" only sees the local node. Obviously, there is some difference is the partition configuration between Tomcat-Cluster and DefaultPartition.
However, I'm not sure how to decode the differences, so if someone can help me, it'll be much appreciated.
Thanks,
Nitesh
java -cp jgroups-2.4.1.jar org.jgroups.tests.Probe -addr 239.0.1.113 -query jmx -query props
---------------------------------------------------------------------------
-- send probe on /239.0.1.113:7500
#1 (2235 bytes): 10.191.10.147:32912 (DefaultPartition)
local_addr=10.191.10.147:32912
group_name=DefaultPartition
version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
view: [10.191.10.147:32912|0] [10.191.10.147:32912]
group_addr=239.0.1.113:45566
stats:
UNICAST={num_bytes_sent=1505, num_xmit_requests_received=0, num_acks_sent=1, num_msgs_sent=1, num_acks_received=1, num_msgs_received=1, num_bytes_received=1505}
NAKACK={xmit_rsps_received=0, xmit_rsps_sent=0, missing_msgs_received=0, xmit_reqs_sent=0, sent_msgs=[381 - 435] (55), received_msgs=10.191.10.147:32912: received_msgs: [], delivered_msgs: [382 - 435] (size=53)
, xmit_reqs_received=0}
UDP={num_bytes_sent=113355, num_msgs_sent=954, num_msgs_received=954, num_bytes_received=1749}
channel={received_bytes=0, sent_msgs=0, received_msgs=0, sent_bytes=0}
props:
<UDP mcast_port="45566"
mcast_recv_buf_size="150000"
mcast_send_buf_size="800000"
mcast_addr="239.0.1.113"
loopback="false"
ip_mcast="true"
ucast_recv_buf_size="150000"
ip_ttl="8"
ucast_send_buf_size="800000" />
<PING num_initial_members="3"
up_thread="true"
timeout="2000"
down_thread="true" />
<MERGE2 max_interval="20000"
min_interval="10000" />
<FD max_tries="5" shun="true"
up_thread="true"
timeout="2500"
down_thread="true" />
<FD_SOCK up_thread="false"
down_thread="false" />
<VERIFY_SUSPECT num_msgs="3"
up_thread="true"
timeout="3000"
down_thread="true" />
<NAKACK max_xmit_size="8192"
up_thread="true"
retransmit_timeout="300,600,1200,2400,4800"
down_thread="true"
gc_lag="50" />
<UNICAST min_threshold="10"
window_size="100"
timeout="300,600,1200,2400,4800"
down_thread="true" />
<STABLE up_thread="true"
desired_avg_gossip="20000"
down_thread="true" />
<FRAG up_thread="true"
frag_size="8192"
down_thread="true" />
<GMS shun="true"
print_local_addr="true"
join_timeout="5000"
join_retry_timeout="2000" />
<STATE_TRANSFER
up_thread="true"
down_thread="true" />
#2 (2259 bytes): 10.191.10.147:32921 (Tomcat-Cluster)
local_addr=10.191.10.147:32921
group_name=Tomcat-Cluster
version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
view: MergeView::[10.191.10.147:32921|1] [10.191.10.147:32921, 10.191.10.148:37308], subgroups=[[10.191.10.147:32921|0] [10.191.10.147:32921], [10.191.10.148:37308|0] [10.191.10.148:37308]]
group_addr=239.0.1.113:45577
stats:
UNICAST={num_bytes_sent=0, num_xmit_requests_received=0, num_acks_sent=4, num_msgs_sent=6, num_acks_received=6, num_msgs_received=4, num_bytes_received=0}
NAKACK={xmit_rsps_received=0, xmit_rsps_sent=0, missing_msgs_received=0, xmit_reqs_sent=0, sent_msgs=[114 - 239] (126), received_msgs=10.191.10.148:37308: received_msgs: [], delivered_msgs: [null - null]
10.191.10.147:32921: received_msgs: [], delivered_msgs: [115 - 239] (size=124)
, xmit_reqs_received=0}
UDP={num_bytes_sent=62081, num_msgs_sent=771, num_msgs_received=1715, num_bytes_received=0}
channel={received_bytes=0, sent_msgs=0, received_msgs=0, sent_bytes=0}
props:
<UDP mcast_port="45577"
mcast_recv_buf_size="80000"
mcast_send_buf_size="150000"
mcast_addr="239.0.1.113"
loopback="false"
ip_mcast="true"
ucast_recv_buf_size="80000"
ip_ttl="8"
ucast_send_buf_size="150000" />
<PING num_initial_members="3"
up_thread="false"
timeout="2000"
down_thread="false" />
<MERGE2 max_interval="20000"
min_interval="10000" />
<FD_SOCK />
<VERIFY_SUSPECT
up_thread="false"
timeout="1500"
down_thread="false" />
<NAKACK max_xmit_size="8192"
up_thread="false"
retransmit_timeout="600,1200,2400,4800"
down_thread="false"
gc_lag="50" />
<UNICAST min_threshold="10"
window_size="100"
timeout="600,1200,2400"
down_thread="false" />
<STABLE up_thread="false"
desired_avg_gossip="20000"
down_thread="false" />
<FRAG up_thread="false"
frag_size="8192"
down_thread="false" />
<GMS shun="true"
print_local_addr="true"
join_timeout="5000"
join_retry_timeout="2000" />
<STATE_TRANSFER
up_thread="true"
down_thread="true" />
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081794#4081794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081794
18 years, 7 months
[JBoss Seam] - EntityManager is null when Stateless Session Bean invoked fr
by jfrankman
Is it possible to inject the EntityManager into a stateless session bean if the bean is invoked from a MDB?
I have a message driven been that calls a stateless session bean. In the session bean I inject entity manager. But when the session bean is invoked from the MDB the entity manager is always null. The app is deployed as an EAR and everything deployes successfully.
MDB:
@MessageDriven(activationConfig =
| {
| @ActivationConfigProperty(propertyName="destinationType",
| propertyValue="javax.jms.Queue"),
| @ActivationConfigProperty(propertyName="destination",
| propertyValue="queue/KeyCheckImageQueue2")
| })
|
| public class KeyCheckImagesMessageHandler implements MessageListener{
|
| public void onMessage (Message msg) {
Stateless session bean:
@Stateless
| @Name("xyzServices")
| public class KeyServicesImpl implements KeyServices
| {
|
| @PersistenceContext
| private EntityManager em;
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081787#4081787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081787
18 years, 7 months
[JBoss Seam] - Injected bean: java assist
by miloslav.vlach
Hi all,
I would like to know something:
I create a pojo named CompanySearchParams. This is not entity. When I use this pojo in search action I got the javassist coded object. I would like to obtain object CompanySearchParams - not javassist.
Know somebody solution ?
When is the POJO marked as @Entity all works good....
Thanks Mila
| <h:form>
| <fieldset> <legend>Vyhledávání spole?ností</legend>
| <table class="search_table full">
| <tr>
| <th>Název:</th>
| <th>M?sto:</th>
| </tr>
| <tr>
| <td>
| <h:inputText value="#{companySearchParams.name}" style="width:95%;" />
| </td>
| <td>
| <h:inputText value="#{companySearchParams.city}" style="width:95%;" />
| </td>
| </tr>
| <tr>
| <td colspan="4">
| <div style="text-align: right;">
| <h:commandButton value="Hledat" action="#{companyAction.find}"/>
| </div>
| </td>
| </tr>
| </table>
| </fieldset>
| </h:form>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081779#4081779
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081779
18 years, 7 months
[Installation, Configuration & DEPLOYMENT] - jboss starts but won't load
by gryffin
I was editing the configuration of my JBoss test installation yesterday and it no longer boots. I backed out the four changes ( adding an SSL connector/mbean and changing the hostname to the actual computer name )).
That didn't solve the problem. I'm getting a ton of persistence related errors and when I try to access the web-console all I get is a white window. It connects, but fails to serve content.
Here's the first errors in the server log, all total there are dozens of related errors.
2007-09-06 10:08:55,640 DEBUG [org.jboss.system.ServiceController] starting service jboss.ejb:service=EJBTimerService,persistencePolicy=database
2007-09-06 10:08:55,640 DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Starting jboss.ejb:service=EJBTimerService,persistencePolicy=database
2007-09-06 10:08:55,671 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: registering pool with interval 900000 old interval: 9223372036854775807
2007-09-06 10:08:55,671 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: about to notify thread: old next: 1189098985671, new next: 1189098985671
2007-09-06 10:08:55,687 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2007-09-06 10:08:55,687 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2007-09-06 10:08:55,687 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2007-09-06 10:08:55,687 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.lang.ClassCastException: oracle.jdbc.OracleDriver)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:164)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:565)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:250)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:491)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:301)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.tableExists(SQLUtil.java:995)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:112)
at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:95)
...
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: oracle.jdbc.OracleDriver
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:239)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:156)
... 122 more
2007-09-06 10:08:55,718 ERROR [org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin] Cannot create timer table
org.jboss.deployment.DeploymentException: Error while checking if table aleady exists TIMERS; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.lang.ClassCastException: oracle.jdbc.OracleDriver); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.lang.ClassCastException: oracle.jdbc.OracleDriver)))
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.tableExists(SQLUtil.java:1040)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:112)
at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:95)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081777#4081777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081777
18 years, 7 months