[Clustering/JBoss] - Re: Farm Deployment with UDP not working
by RedChili
For completeness, this is the trace on the sending machine when I use TCP instead of UDP:
2007-03-27 11:14:14,095 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Partition DefaultPartition received msg
| 2007-03-27 11:14:14,096 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] pre methodName: FarmMemberService.farmDeployments
| 2007-03-27 11:14:14,096 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] handlerName: FarmMemberService methodName: farmDeployments
| 2007-03-27 11:14:14,096 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Handle: FarmMemberService.farmDeployments
| 2007-03-27 11:14:14,096 DEBUG [org.jboss.ha.framework.server.FarmMemberService] farmDeployments request, parentDUMap.size=1
| 2007-03-27 11:14:14,097 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] rpc call return value: {farm/kusssdemo.ear=Mon Mar 26 17:14:03 CEST 2007}
| 2007-03-27 11:14:14,123 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Partition DefaultPartition received msg
| 2007-03-27 11:14:14,129 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] pre methodName: org.jboss.ha.framework.server.ClusterFileTransferService.remotePullOpenFile
| 2007-03-27 11:14:14,129 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] handlerName: org.jboss.ha.framework.server.ClusterFileTransferService methodName: remotePullOpenFile
| 2007-03-27 11:14:14,129 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Handle: org.jboss.ha.framework.server.ClusterFileTransferService.remotePullOpenFile
| 2007-03-27 11:14:14,139 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] rpc call return value: org.jboss.ha.framework.server.ClusterFileTransfer$FileContentChunk@2ef8e535
|
The file is requested, openend and consequentally transferred and successfully deployed on the other machine and the clustered application works fine. Is it possible that 'I'm hitting a bug with the UDP configuration here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031961#4031961
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031961
19Â years
[Installation, Configuration & Deployment] - Help required for SPECjAppserver2004 setup on Jboss
by sudheer_pisces
I have been trying to setup SPECjAppserver2004 on Jboss, I have used jboss version 4.05-GA and the jboss-specj kit version 1.3.7 for the setup.
The emulator, SUT and the database server are on different machines.
On the emulator machine, Jboss server fails to start, it says that the jboss-service.xml file is missing. I have found that some files are not created by ant in the $JBOSS_EMULATOR_HOME/server/$JBOSS_EMULATOR_SERVER_NAME directory.
The error message that I get is as follows :
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /usr/local/jboss-4.0.5.GA
JAVA: /usr/java/jdk1.6.0/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: /usr/local/jboss-4.0.5.GA/bin/run.jar:/usr/java/jdk1.6.0/lib/tools.jar
=========================================================================
15:06:32,865 INFO [Server] Starting JBoss (MX MicroKernel)...
15:06:32,867 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
15:06:32,870 INFO [Server] Home Dir: /usr/local/jboss-4.0.5.GA
15:06:32,871 INFO [Server] Home URL: file:/usr/local/jboss-4.0.5.GA/
15:06:32,873 INFO [Server] Patch URL: null
15:06:32,873 INFO [Server] Server Name: emulator
15:06:32,873 INFO [Server] Server Home Dir: /usr/local/jboss-4.0.5.GA/server/emulator
15:06:32,874 INFO [Server] Server Home URL: file:/usr/local/jboss-4.0.5.GA/server/emulator/
15:06:32,874 INFO [Server] Server Log Dir: /usr/local/jboss-4.0.5.GA/server/emulator/log
15:06:32,875 INFO [Server] Server Temp Dir: /usr/local/jboss-4.0.5.GA/server/emulator/tmp
15:06:32,876 INFO [Server] Root Deployment Filename: jboss-service.xml
15:06:33,487 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
15:06:33,487 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc.
15:06:33,487 INFO [ServerInfo] OS-System: Linux 2.4.20-8smp,i386
15:06:33,916 INFO [Server] Core system initialized
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: url file:/usr/local/jboss-4.0.5.GA/server/emulator/conf/jboss-service.xml could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:781)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:619)
15:06:33,951 INFO [Server] Runtime shutdown hook called, forceHalt: true
15:06:33,952 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
15:06:33,964 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
The jboss-MySQL-run.properties file on the machine is as follows:
#--------------
#SPECJ home
#--------------
JAS_HOME=/usr/local/SPECjAppServer2004-1.05
#--------------
#Driver configuration
#--------------
TXRATE=50
OUTDIR=/usr/local/SPECjAppServer2004-1.05/output
DUMPDIR=/tmp/specj
TRIGGERTIME=50
RAMPUPTIME=600
STDYSTATETIME=1800
RAMPDOWNTIME=300
#--------------
#SUT configuration
#--------------
JBOSS_HOME=/usr/local/jboss-4.0.5.GA
JBOSS_URL=http://10.107.26.6:8080
APPLICATION_HOST=10.107.26.6
APPLICATION_PORT=8080
server-name=specj2004
#--------------
#Emulator configuration
#--------------
JBOSS_EMULATOR_HOME=/usr/local/jboss-4.0.5.GA
JBOSS_EMULATOR_HOST=10.107.26.23
JBOSS_EMULATOR_PORT=8080
JBOSS_EMULATOR_SERVER_NAME=emulator
#--------------
#specj2004 database
#--------------
JDBC_URL=jdbc:mysql://10.107.26.43/specj2004
JDBC_DRIVER=com.mysql.jdbc.Driver
JDBC_USER=specj2004
JDBC_PASSWORD=specj2004
JDBC_DATASOURCE_NAME=SpecjDS
JDBC_DATASOURCE_NAME_RC=SpecjDS_RC
JDBC_DATASOURCE_NAME_RR=SpecjDS_RC
JDBC_DATASOURCE_NAME_RC.MIN=0
JDBC_DATASOURCE_NAME_RC.MAX=500
JDBC_DATASOURCE_NAME_RR.MIN=0
JDBC_DATASOURCE_NAME_RR.MAX=500
#--------------
#jms database
#--------------
JMS_JDBC_URL=jdbc:mysql://10.107.26.43/jbossjms
JMS_JDBC_DRIVER=com.mysql.jdbc.Driver
JMS_JDBC_USER=jbossjms
JMS_JDBC_PASSWORD=jbossjms
JMS_JDBC_DATASOURCE_NAME=SpecjJMSDS
#--------------
#Datasources configuration
#--------------
JDBC_DATASOURCE_MAPPING=mySQL
#DRIVER_JAVA_PARAMETERS=
server-database=mySQL
--
Regards,
sudheer_pisces
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031960#4031960
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031960
19Â years
[Messaging, JMS & JBossMQ] - When/where to create TopicConnection objects in a stateless
by frank_montoya
Our configuration:
- We installed JBoss jboss-4.0.5.GA
- we use stateless SBs, MDBs, and JMX services
- JMS producers are one of our stateless SB and our JMX services
- JMS consumers are our MDBs and our JMX services.
The context:
In most of the methods of one of our session beans, we need to publish JMS messages. Considering that TopicConnection creation is expensive, I first added a TopicConnection member to the sessionBean. I created and started the TopicConnection during the @PostConstruct method, and closed it in the @PreDestroy method.
The problem:
- Session beans are pooled components, so if 100 of them are in the pool, they all have an established connection on port 8093. That?s already not good. (100 is the default ?MaximumSize? for ?Standard Stateless SessionBean? in standardjboss.xml)
- Furthermore, it seems to have an impact on the pooling of the session bean, because I get more than 200 instances of the session bean, and it just keep on growing with normal load of our application. Of course the number of established connections on port 8093 grows as well.
My solutions (work around)
- (1) I create and start a TopicConnection instance every time I need to send a message in the SB. This way I have few established connections on port 8093. A (good) side effect is that there are less instances of the session bean in JBoss (about 40, and stable with normal load of our application).
- (2) I change the setting in standardjboss.xml in order to have 10 for the ?MaximumSize? of ?Standard Stateless SessionBean. I added also strictMaximumSize setting with true value. The number of the stateless SB and the number of the established connection on port 8093 is then limited.
My questions:
I spent a lot of time testing and looking at the JBoss forum. I still have the following questions:
- (1) Is it a bad idea to create a TopicConnection member instance per SessionBean instance?
- (2) Is there a better way to do it? Limiting the stateless SB pool size does not seems a good idea. Creating/starting a connection for every publish message neither.
Any help is welcome, thanks.
Frank
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031959#4031959
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031959
19Â years
[Messaging, JMS & JBossMQ] - Re: import org.jboss.mq.server.jmx.Queue
by milind.uc
"milind.uc" wrote : yes ,, hay thanks for ur reply as I get confidence from your reply because before reading your reply I did the things which you mentioned but the thing is that only the getQueueDepth is working which is nothing but the tolal number fo the messages in the queue..Other attributes like the getSchedulemessagecount(),getReceiversCount() are giving the values zero ..Still writing this reply I used all thses things only on the receivers side.. I did in the foloowing way while sending the messages and still not on the receivers side...
|
|
| | MBeanServerConnection mbean_server = null;
| | ObjectName dm = null;
| | try{
| |
| |
| | mbean_server =(MBeanServerConnection) ctx.lookup("jmx/rmi/RMIAdaptor");
| | dm = new ObjectName("jboss.mq:service=DestinationManager");
| |
| | String domain = "jboss.mq.destination";
| | String service = "service=Queue";
| | String name = "name=queue/C";
| |
| | String stringObjectName = domain + ":" + service + "," + name;
| |
| |
| |
| |
| | ObjectName queueObjectName = ObjectName.getInstance(stringObjectName);
| |
| | org.jboss.mq.server.jmx.QueueMBean queueMBean =
| | (org.jboss.mq.server.jmx.QueueMBean) MBeanServerInvocationHandler.newProxyInstance(
| | mbean_server,
| | queueObjectName,
| | org.jboss.mq.server.jmx.QueueMBean.class,
| | false
| | );
| | System.out.println("queue depth is :" + queueMBean.getQueueDepth());
| | System.out.println("getScheduledMessageCount count is :" + queueMBean.getScheduledMessageCount());
| | System.out.println("History Limit :"+queueMBean.getMessageCounterHistoryDayLimit());
| | System.out.println("MAximmum depth :"+ queueMBean.getMaxDepth());
| | System.out.println("Receiver Count is :" +queueMBean.getReceiversCount());
| | System.out.println("Redelivery Limit:"+queueMBean.getRedeliveryLimit());
| | System.out.println("Name is :"+queueMBean.getName());
| | System.out.println("queue name is :"+queueMBean.getQueueName());
| |
| |
| |
|
| Again if I did the org.jboss.mq.server MessageCounter meas []= queueMBean.getMessageCounter(); then I got the exception as===
| java.lang.reflect.UndeclaredThrowableException
| at $Proxy1.getMessageCounter(Unknown Source)
| at Statstic.Sender_Count.main(Sender_Count.java:220)
| Caused by: java.io.NotSerializableException: org.jboss.mq.server.MessageCounter
| at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
| at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
| .....
|
| Beside the total count of the messages in the queue I also needed how many messages are scheduled(Recived by reciver ) ,pending.If u have idea then please suggest and guide me.
|
| Thanks for all your help it is pleasurable :)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031958#4031958
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031958
19Â years
[Messaging, JMS & JBossMQ] - Re: import org.jboss.mq.server.jmx.Queue
by milind.uc
yes ,, hay thanks for ur reply as I get confident from your reply because before reading your reply I did the things which you mentioned but the thing is that only the getQueueDepth is working which is nothing but the tolal number fo the messages in the queue..Other attributes like the getSchedulemessagecount(),getReceiversCount() are giving the values zero ..Still writing this reply I used all thses things only on the receivers side.. I did in the foloowing way while sending the messages and still not on the receivers side...
| MBeanServerConnection mbean_server = null;
| ObjectName dm = null;
| try{
|
|
| mbean_server =(MBeanServerConnection) ctx.lookup("jmx/rmi/RMIAdaptor");
| dm = new ObjectName("jboss.mq:service=DestinationManager");
|
| String domain = "jboss.mq.destination";
| String service = "service=Queue";
| String name = "name=queue/C";
|
| String stringObjectName = domain + ":" + service + "," + name;
|
|
|
|
| ObjectName queueObjectName = ObjectName.getInstance(stringObjectName);
|
| org.jboss.mq.server.jmx.QueueMBean queueMBean =
| (org.jboss.mq.server.jmx.QueueMBean) MBeanServerInvocationHandler.newProxyInstance(
| mbean_server,
| queueObjectName,
| org.jboss.mq.server.jmx.QueueMBean.class,
| false
| );
| System.out.println("queue depth is :" + queueMBean.getQueueDepth());
| System.out.println("getScheduledMessageCount count is :" + queueMBean.getScheduledMessageCount());
| System.out.println("History Limit :"+queueMBean.getMessageCounterHistoryDayLimit());
| System.out.println("MAximmum depth :"+ queueMBean.getMaxDepth());
| System.out.println("Receiver Count is :" +queueMBean.getReceiversCount());
| System.out.println("Redelivery Limit:"+queueMBean.getRedeliveryLimit());
| System.out.println("Name is :"+queueMBean.getName());
| System.out.println("queue name is :"+queueMBean.getQueueName());
|
|
|
Again if I did the org.jboss.mq.server MessageCounter meas []= queueMBean.getMessageCounter(); then I got the exception as===
java.lang.reflect.UndeclaredThrowableException
at $Proxy1.getMessageCounter(Unknown Source)
at Statstic.Sender_Count.main(Sender_Count.java:220)
Caused by: java.io.NotSerializableException: org.jboss.mq.server.MessageCounter
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
.....
Beside the total count of the messages in the queue I also needed how many messages are scheduled(Recived by reciver ) ,pending.If u have idea then please suggest and guide me.
Thanks for all your help it is pleasurabel :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031954#4031954
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031954
19Â years