August 2009 - jboss-user - Jboss List Archives

[JBoss Messaging Users] - Re: Remote JMS Provider | Connecting EJB3 to a remote Topic

by artima

Hi Andy, Thanks for your response. I did look at HornetQ as mentioned in your response. The example in HornetQ is no different than the one for JBM2.0, except that it uses a different Java package for the same class. Even with JBM2.0, I had tried out the approach of direct netty connection specified in the MDB, but doesnt work either. [Unless there is bug in BETA 4.0 that prevents us doing that]. Any further help will be greatly appreciated. Thank, amit. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251650#4251650 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251650

16 years, 8 months

1
0
0 / 0

[jBPM Users] - Re: How to control process transition in JBPM 4.0?

by jbarrez

This is quite easy to implement if you use the transitions as a 'button' for going to every screen; ie. on the second screen your process is halted until the button is clicked, which will signal the process. I don't see anything out of the ordinary in this use case, or am I missing something? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251648#4251648 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251648

16 years, 8 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: jboss website as default site

by hand-solo

i don't want to restart the jboss server, is it possible to deploy considering the index.jsp lies in the web-deployer ROOT.war directory? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251645#4251645 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251645

16 years, 8 months

1
0
0 / 0

[JBoss Tools Users] - Re: Generating DDL from annotated POJOs

by JPAV

No, automatic build is turned on. Not to mention, I've tried manually building several times also with no change. Wrt the missing entity class, I show the Inner class in the screencast with the @Entity annotation, and I believe that is the class that can't be found for some reason. This is a bit of a new error for me. Not sure what I did right before the capture to get this. I was getting a ClassNotFoundException for the SqlServerDriver. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251640#4251640 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251640

16 years, 8 months

1
0
0 / 0

[JBoss Tools Users] - Re: Generating DDL from annotated POJOs

by max.andersen＠jboss.com

The screencast you sent to me in private email have the same error again and again on creating the console configuraiton: Some class/package is missing and that is 99% because the project is not actually built. It also seems like there is no Entity class on the classpath. Have you disabled automatic build ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251638#4251638 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251638

16 years, 8 months

1
0
0 / 0

[JBoss AOP Users] - Re: Deploy AOP to jboss 5.1

by kabir.khan＠jboss.com

If you want to intercept onMessage() only, you're probably better off creating a custom AOP domain for message driven beans (see deploy/ejb3-interceptors-aop.xml for examples of how to do this) and to use the @AspectDomain annotation on your message driven beans where you want this behaviour. This will avoid the need for weaving your classes. There should be some examples on how to do this in the ejb 3 documentation or user forum. Regarding your question, it "should work" for onMessage(), but I am not sure how ejb3 interacts with woven classes, and since EJB3 uses AOP to configure itself, there might be some problem with aspects on EJB 3 business methods. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251636#4251636 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251636

16 years, 8 months

1
0
0 / 0

[JBoss AOP Users] - Re: Deploy AOP to jboss 5.1

by kgreenejpmc

Ok, after quite a bit of trial and error I finally got the aop to work. However, I have a question. If I put my @JobFlow annotation on the onMessage method, the aop does not work. However, If I put the @JobFlow annotation on the processMessage method (which onMessage calls), the aop works. Does jboss suppress or ignore custom annotations on onMessage? If so, is there a way to enable them to work on onMessage? | @MessageDriven(activationConfig = { | @ActivationConfigProperty(propertyName="maxMessages", propertyValue="1"), | @ActivationConfigProperty(propertyName="maxSession", propertyValue="3"), | @ActivationConfigProperty(propertyName="dLQMaxResent", propertyValue="1"), | @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), | @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/TestConsumer1") | }) | @Clustered | public class TestConsumer1 implements MessageListener { | | | | | private static Logger log = Logger.getLogger(TestConsumer1.class); | | @Resource | private MessageDrivenContext context; | | | | //put @JobFlow here does not work. The aop does not get called | public void onMessage(Message msg) { | log.info("Got message."); | | | try | { | processMessage(msg); | TextMessage txtMsg = (TextMessage)msg; | String stagingPath = txtMsg.getText(); | | log.info("FlowId: " + MessageProperties.getFlowId(msg)); | log.info("JobId: " + MessageProperties.getJobId(msg)); | log.info("PrevStageId: " + MessageProperties.getPrevStageId(msg)); | | } | catch (Exception e) | { | context.setRollbackOnly(); | | } | | | log.info("DONE!"); | } | | | //putting @JobFlow here works and the aop is called | @JobFlow | public void processMessage(Message msg) | { | log.info("Running processMessage"); | } | | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251632#4251632 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251632

16 years, 8 months

1
0
0 / 0

[JBoss Messaging Users] - Deploying an MDB on a server started using the -b option.

by k.k.ramachandran

Hi, I've got a simple EJB 3 style MDB. When I deploy it on a server started without the -b option i.e ./run.sh. It works fine. When I deploy it to a server started with the -b option ./run.sh -b <ip addr> I get the following errors : | 14:12:48,538 DEBUG [NamingContext] Failed to connect to localhost:1099 | javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:331) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1696) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) | at java.lang.Thread.run(Thread.java:613) | Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301) | ... 17 more | Caused by: java.net.ConnectException: Connection refused | at java.net.PlainSocketImpl.socketConnect(Native Method) | at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) | at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) | at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) | at java.net.Socket.connect(Socket.java:520) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:297) | ... 17 more | 14:12:53,540 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@74b6e6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)2a032a destination=queue/DeliverMPOExternalMessageQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=bssub pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]] | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1725) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) | at java.lang.Thread.run(Thread.java:613) | Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:331) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1696) | ... 16 more | Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301) | ... 17 more | Caused by: java.net.ConnectException: Connection refused | at java.net.PlainSocketImpl.socketConnect(Native Method) | at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) | at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) | at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) | at java.net.Socket.connect(Socket.java:520) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:297) | ... 17 more | | | The bean is obviously looking to connect over localhost and failing. How do i get around this View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251627#4251627 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251627

16 years, 8 months

1
0
0 / 0

[EJB 3.0 Users] - MDBs and -b option.

by k.k.ramachandran

Hi, I'm having trouble deploying an mdb. It's a relatively simply EJB 3, MDB configured via annotations. Here is the config: | @MessageDriven(activationConfig = { | @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), | @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), | @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/DeliverMPOExternalMessageQueue"), | // @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/RemoteJMSProvider"), | @ActivationConfigProperty(propertyName = "user", propertyValue = "user"), | @ActivationConfigProperty(propertyName = "password", propertyValue = "password") | }) | This works fine when i simply start a server using ./run.sh. However when i bind the server to my ip address: ./run.sh -b 10.0.0.191 . I get the following errors: | 14:12:48,538 DEBUG [NamingContext] Failed to connect to localhost:1099 | javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:331) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1696) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) | at java.lang.Thread.run(Thread.java:613) | Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301) | ... 17 more | Caused by: java.net.ConnectException: Connection refused | at java.net.PlainSocketImpl.socketConnect(Native Method) | at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) | at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) | at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) | at java.net.Socket.connect(Socket.java:520) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:297) | ... 17 more | 14:12:53,540 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@74b6e6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)2a032a destination=queue/DeliverMPOExternalMessageQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=bssub pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]] | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1725) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) | at java.lang.Thread.run(Thread.java:613) | Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:331) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1696) | ... 16 more | Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused] | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301) | ... 17 more | Caused by: java.net.ConnectException: Connection refused | at java.net.PlainSocketImpl.socketConnect(Native Method) | at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) | at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) | at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) | at java.net.Socket.connect(Socket.java:520) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97) | at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82) | at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:297) | ... 17 more | Any hints? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251625#4251625 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251625

16 years, 8 months

1
0
0 / 0

[jBPM Users] - Re: How to control process transition in JBPM 4.0?

by jbpmjboss11

Thanks for the response. To explain my problem in more detail ... What I am planning to do is ... 1. I have a web application say 3-4 screens. I have created JBPM flow as one page backend code as one process state. 2. I don't want to tie up my UI with JBPM. When user clicks on first page, backend java component will be called through JBPM. 3. Like, first screen "submit" button will initiate the process, and calls the class mentioned in first java task with proper input and receive response. 4. Now I send this output to the user screen (my first state/task is complete). 5. Here I want transition from first state/task to second state/task to be on hold till user moves to second screen. Do you think this is possible? So far I have not seen anything in JBPM API which can hold process from transitioning once state/task is over. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251624#4251624 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251624

16 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user August 2009