[Installation, Configuration & DEPLOYMENT] - Steps to install Jboss tools in eclipse sdk
by praveenas
Hi all,
I found a manual to install the jboss IDE plug in to the eclipse. http://www.devx.com/opensource/Article/20242/0/page/1
But when I have followed this, I am not getting the updations properly. For identifying the bug while clustering jboss, I want to add the Jboss IDE plug in to the eclipse which already have tomcat running. When I am trying to do this, following the above doc, while I want to run jboss in debug mode, tomcat is starting immediately.
I came to know that Jboss IDE is replaced with jboss tools. But let me know the steps to configure it exactly and properly in eclipse sdk, which have tomcat configured already in it.
Or please let me know the actual configuration manual of JBossIDE-1.6.0.GA-Bundle-linux-gtk.
I want to run jboss in debug mode. Also, Let me know the command for this. Or any particular steps to be followed if we are running with out eclipse?
Pls let me know the doc to be refered for solving the above queries. Sorry for the drafting . Thanks for ur patience in reading the mail.
Thanks ,
Praveena.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154922#4154922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154922
16 years
[Clustering/JBoss] - jgroup duplicate member issue
by ikbenben
hey everyone,
we've set up a jboss 4.0.5 cluster involving two servers and i'm seeing some strange behavior. basically, the cluster view is adding duplicate members as shown below.
the cluster configuration is using the default configuration where we are passing in the appropriate clustering variables: jboss.partition.name and jboss.partition.udpGroup
anybody have any ideas?
-------------------------------------------------------
| GMS: address is sagesavprdapp02vm:33636 (additional data: 17 bytes)
| -------------------------------------------------------
| 2008-06-01 17:27:08,358 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.atg20071.prd] New cluster view for partition atg20071.prd (id: 1936, delta: 1) : [172.16.36.37:1299, 172.16.36.36:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299]
| 2008-06-01 17:27:08,359 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.atg20071.prd] I am (172.16.36.37:1299) received membershipChanged event:
| 2008-06-01 17:27:08,359 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.atg20071.prd] Dead members: 0 ([])
| 2008-06-01 17:27:08,359 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.atg20071.prd] New Members : 0 ([])
| 2008-06-01 17:27:08,359 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.atg20071.prd] All Members : 73 ([172.16.36.37:1299, 172.16.36.36:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299, 172.16.36.37:1299])
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154912#4154912
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154912
16 years, 1 month
[Messaging, JMS & JBossMQ] - MDB does not consume messages
by jonathanztaub
I'm using JBoss 4.2.2 on a Windows XP.
I was able to configure JMS settings and am now able to send JMS messages to a queue and I can see the messages stored in my MySQL database. The problem is that the MDB does not seem to consume any messages.
Here are snippets from the ejb-jar.xml (EJB 3) deployment descriptor (I make minimal usage of annotations):
<?xml version="1.0"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
<enterprise-beans>
<message-driven>
<ejb-name>ServiceProcessorBean</ejb-name>
<ejb-class>com.mobilexl.server.ejb.ServiceProcessorBean</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>messageSelector</activation-config-property-name>
<activation-config-property-value>MessageFormat = 'Version 3.4'</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>acknowledgeMode</activation-config-property-name>
<activation-config-property-value>Auto-acknowledge</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>queue/ServiceRequest</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
</ejb-jar>
I know that the application server examines this because if I omit the destintation property, I'm getting errors.
The jboss.xml looks like:
<?xml version="1.0"?>
<jboss xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
version="3.0">
<enterprise-beans>
<message-driven>
<ejb-name>ServiceProcessorBean</ejb-name>
<destination-jndi-name>queue/ServiceRequest</destination-jndi-name>
</message-driven>
</enterprise-beans>
The jboss-destinations-service.xml looks like:
<!-- Destination without a configured SecurityManager or without a
a SecurityConf will default to role guest with read=true, write=true, create=false.
-->
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
queue/ServiceRequest
(if I remove the queue defintions from here, upon startup, JBoss issues a warn level log statement saying that the queue cannot be found and it creates one).
Using the JMS console, I'm able to see the queue and my message driven bean. The code for the message driven bean is:
...
...
public class ServiceProcessorBean implements MessageListener
{
private static final Logger logger = Logger.getLogger(ServiceProcessorBean.class);
public ServiceProcessorBean()
{
logger.info("------- in MDB's constructor -------");
System.out.println("------- in MDB's constructor ------ sysout");
}
public void onMessage(Message message)
{
logger.fatal("----------- onMessage ------------");
try
{
TextMessage textMessage = (TextMessage)message;
logger.info("In MDB: " + textMessage.getText());
}
catch(JMSException e)
{
logger.error("Failed to process request.", e);
}
}
}
I put logging on the onMessage and in the constructor just to see if an object is being instantiated and whether the MDB consumes messages. NON of these is happening.
In the JMX console, under jboss.j2ee, I see:
ear=mobile-xl-server-1.0-SNAPSHOT.ear,jar=ejb-1.0-SNAPSHOT.jar,name=ServiceProcessorBean,service=EJB3
I was able to get over the configuration part and it seems like messages are stored correctly (I omitted all session bean related code that sends the messages for brevity). However, I cannot figure out why the message driven bean is not activated/instantiated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154906#4154906
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154906
16 years, 1 month
[JBoss Messaging] - JBoss Messaging 2.0.0 alpha released
by timfox
JBoss messaging 2.0.0 alpha is released!
The goal of JBM 2.0 is simple and uncompromising- to bring unrivalled levels of performance to reliable messaging, and to be the fastest, best featured and most scalable open source messaging system. Period.
JBM 2.0 alpha is a technology preview of our next generation messaging system and demonstrates that we are well on the way to achieving that goal, with class-beating performance results.
We don't like to make unfalsifiable claims about our performance in our marketing literature. We prefer science to religion. So, in this release, we back up our assertions with a set of simple performance measurements comparing JBM 2.0 alpha with a selection of other open source messaging systems, including the market leader Apache ActiveMQ, and also Apache QPid and MRG Messaging 1.0 C++ version (pre GA)
Performance results are here http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/...
The tests are all reproducable by you, using only the tools shipped in the distribution. I think you'll agree that the facts speak for themselves.
Remember that JBM 2.0 is only an alpha release but we demonstrate results that outstrip competing production, or near production releases.
The success of JBM 2.0 comes down to a few factors:
1) An elegant simple architecture - 100% POJO based, allowing embeddable messaging in any product. The JMS API is provided as a thin optional facade on the client side.
2) An ultra high performance intelligent journal which can automatically flip into using pure Java NIO, or Linux asynchronous IO (via a thin native layer) depending on whether AIO is available on the system. This gives us astonishing persist rates even on commodity hardware. (See performance results). The journal is written in 95% Java, deliberately keeping the native layer to a minimum, making it far simpler to manage and port to other operating systems in the future.
3) A high performance new transport based on Apache MINA.
And not forgetting that none of this would be possible without our team. We have a small, but highly experienced, highly motivated team who have worked their butts off all hours of the day and night for as long as I can remember.
Many thanks to the "dream team", in no particular order, Andy Taylor, Clebert Suconic and Jeff Mesnil. Also thanks to Trustin Lee for working closely with us to build our new transport.
The release is available here: http://www.jboss.org/jbossmessaging/downloads/
Enjoy...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154898#4154898
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154898
16 years, 1 month