[JBoss Tools] - JBoss Developer Studio 4 is now available for free
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the blog post:
"JBoss Developer Studio 4 is now available for free"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/03/22/jboss-develope...
--------------------------------------------------------------
JBoss Developer Studio 4 is now avaliable for free (registration required) from http://devstudio.jboss.com/download/ http://devstudio.jboss.com/download/
If you are an existing Red Hat Support Portal user/customer then you already should have access to JBoss Developer Studio via the Downloads section, but if you are a new user the only thing you need to do is to signup and you will be granted access to the free download of JBoss Developer Studio.
The direct link to the download no matter if you are existing or new user of Red Hat Support Portal is: https://www.redhat.com/wapps/eval/index.html?evaluation_id=1015 https://www.redhat.com/wapps/eval/index.html?evaluation_id=1015
h2. What is JBoss Developer Studio 4 ?
JBoss Developer Studio 4 comes as a full easy to install Eclipse installation that bundles Eclipse WTP, TestNG, Spring IDE and the latest updated release of the http://community.jboss.org/docs/DOC-13300 supported plugins from http://community.jboss.org/community/tools/blog/2011/02/21/jboss-tools-32... JBoss Tools 3.2.
This latest release highlights are that it is now based on Eclipse 3.6 (Helios), updates the JSF 2 tooling, adds remote deployment for JBoss server adapters, easier setup of existing runtimes, provides tech preview of improved CDI functionallity and it includes updates for the SOA-P related features such as Guvnor, Drools, jBPM 3, Teiid Designer and Modeshape plugins.
h2. Free vs For Pay ?
The free version of JBoss Developer Studio is the standalone version which can be used with both community and productized versions of JBoss Application Server and related frameworks such as Hibernate, Seam, Drools, jbpm, etc. The difference between this distribution and JBoss Tools boils down to ease-of-installation and future updates.
The product called JBoss Developer Studio Portfolio Edition is also available from http://devstudio.jboss.com/download/ http://devstudio.jboss.com/download/ for 99$ and in addition to the standalone version of JBoss Developer Studio it gives access to a bundle with JBoss Enterprise Application Platform 5 and additional downloads for development purposes of JBoss and Red Hat runtime distributions - including but not limited to JBoss Enterprise SOA Platform and Red Hat Enterprise Linux. You can read more about this offering at http://www.jboss.com/products/devstudio/ http://www.jboss.com/products/devstudio/
Thus if you already have access to the runtimes you would like to target for development the free version of JBoss Developer Studio is for you, but if you want access to the full range of JBoss and Red Hat runtime products (+ updates) for developement then the Portfolio Edition is what you are looking for.
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/03/22/jboss-develope...]
15 years
[JBoss Messaging] - MDB stop processing messages from Queue(JBossMessaging)
by KVMKrishna Reddy
KVMKrishna Reddy [http://community.jboss.org/people/dasmurali] created the discussion
"MDB stop processing messages from Queue(JBossMessaging)"
To view the discussion, visit: http://community.jboss.org/message/594656#594656
--------------------------------------------------------------
Hi,
We had a java client connecting to Queue(hosted in remote server), publishing messages to the Queue. And the remote server will have a MDB(whose MaxPoll size is 100) which will listens to this queue and process the messages. Average load will be around 100K messages per day.
After migrating to JBoss 5.1 (with JBoss Messaging), MDB in my remote server stopped processing messages after some time (guessing it is happening at peak load time).
Please find below configurations of my application.
Both servers are running in JBoss 5.1.GA
JBoss Messaging: 1.4.3.GA
JBoss Remoting: 2.5.1
Not changed any configurations of JBoss Messaging comes with JBoss 5.1 Application server in remote server.
No exceptions in Remote Server instance. Got few errors at client application server. Find the below exception stack trace for the same below.
<code>
2011-03-21 13:28:42,965 ERROR [MY_MDB] (WorkManager(2)-40) exception processing message
org.jboss.jms.exception.MessagingNetworkFailureException
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:263)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:191)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_2129980416.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_2129980416.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
at com.adp.ebs.dasmonitor.ejb.AbstractMailHandler.sendMessage(AbstractMailHandler.java:105)
at com.adp.ebs.dasmonitor.ejb.payrollprocessed.PayrollProcessedHandler.handle(PayrollProcessedHandler.java:199)
at com.adp.ebs.dasmonitor.ejb.GenericMDB.onMessage(GenericMDB.java:143)
at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.invocation.Invocation.performCall(Invocation.java:386)
at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:513)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:156)
at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:115)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.RunAsSecurityInterceptor.process(RunAsSecurityInterceptor.java:133)
at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:103)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:415)
at org.jboss.ejb.Container.invoke(Container.java:1029)
at sun.reflect.GeneratedMethodAccessor357.invoke(Unknown Source)
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:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor.delivery(MessageEndpointInterceptor.java:249)
at org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor.invoke(MessageEndpointInterceptor.java:128)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy229.onMessage(Unknown Source)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160)
at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_2129980416.invoke(SessionAspect_z_handleRun_2129980416.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:234)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://<<IP_ADDRESS>>:4657/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&connectionWait=10&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&stopLeaseOnFailure=true&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&validatorPingPeriod=10000&validatorPingTimeout=5000]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:776)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:426)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:467)
at org.jboss.remoting.Client.setupClientLease(Client.java:1715)
at org.jboss.remoting.Client.connect(Client.java:1615)
at org.jboss.remoting.Client.connect(Client.java:515)
at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:354)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:350)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:158)
... 63 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:366)
at java.net.Socket.connect(Socket.java:519)
at com.wily.introscope.agent.probe.net.ManagedSocket.connect(ManagedSocket.java:263)
at org.jboss.remoting.transport.socket.SocketClientInvoker.connect(SocketClientInvoker.java:289)
at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:206)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:433)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:1089)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:762)
</code>
Thanks and Regards
Murali Reddy
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/594656#594656]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Tools] - My issues (or missunderstandings) with Jboss Tools
by Tim Evers
Tim Evers [http://community.jboss.org/people/Kragoth] created the discussion
"My issues (or missunderstandings) with Jboss Tools"
To view the discussion, visit: http://community.jboss.org/message/592592#592592
--------------------------------------------------------------
Hey everybody.
Let me preface this by saying that my complaints may be completely unfounded and if anyone can help me solve my problems I will be most greatful.
So, let me describe the application I'm working on.
We have 2 tier design with Hibernate and Spring being the basis of our service layer and Seam/JSF being the basis of our web layer. Obviously there are other technologies/libs involved but...that's they are the foundations.
BUT!!!! (And this seems to be where jboss tools and to a certain extent eclipse itself falls to the ground and becomes a very annoying tool) I am not a 1 man team. Not only am I not alone, Eclipse is NOT the only IDE being used. Infact the structure of the app was designed in InteliJ (IDEA).
So. let me explain our structure.
root
-> code
-> workspace //The eclipse workspace for my project is here outside my codebase
Inside the code folder
code
-> gekko-build //Yeah I had to use linked resources to make this work cause ecipse is stupid about only compiling inside the project space
-> gekko-services //All our .java files from ../gekko/gekko-services (see description below) compile there .class files to here
-> gekko-web //Same as above except all the .class files from the compiled ../gekko/gekko-web/*.java files
-> gekko
-> gekko-services //All our Hibernate and Spring stuff are here. Entities, Spring Components and Services
-> gekko-web
-> config
-> seam/WEB-INF/classes
-> spring/WEB-INF/classes
-> web/WEB-INF //Contains things like web.xml and other files that will deploy into the war WEB-INF directory
->tags
-> prod-src
-> java //This is where all our Seam beans are.
-> resources //.properties files for messages etc
-> web //All our .xhtml files are here
So, that's a fairly accurate view of our folder structure.
So, let's try getting jBoss tools to play nice with this project... Older versions of the jboss tools worked OK. They had issues but auto complete in EL expressions and other features that really were quite helpful worked. There was a lot of stuff that didn't but I could live with it. As new versions came out it would take me longer and longer to get them working with our structure up till now. Now I can't get it working at all.
So, I do the Add Seam Support
Seam support - checked
Seam Runtime - created a new runtime to the directory I have in a sibling project...once again WHY!!! can't I put in a project relative path *SIGH* (I want to share these settings to others in my team...why make them hardcoded directories?)
Deployment - WAR (I really don't want you to care about how I deploy, I just want you to allow me to have the features of EL expression auto complete etc)
View Folder - Well, I tried blank and /gekko/gekko-web/web but no idea if it is doing anything for me
Model - blank....We dont use extended persistence context Spring is our transaction manager.
Action/Form/Conv - gekko/gekko-web/prod-src/java - But....the Seam beans are not detected *sigh*
package - gekko.web
Test - left unchecked
So, click apply and nope not working.
Now, I've played around a bit with this and I notice that the Seam buildier is not appearing in my list of builders. *sigh*
So, I go check out the project Facets. Seam is not checked...if I try check it it tells me I have constraints not met. OK
But....all the required constraints now try to enforce a structure on my app. WTH? It should NOT matter how my uncompiled app is structured.
So, not to be out done I add the seam builder to my .project file manually. BOOM! All my Seam Beans now appear in the Seam Component view and auto complete in my EL expressions now shows my Seam beans. OK, making progress.
But, I don't get any of the features that I was hoping to get. Thinks like finding all usages of a method in my xhtml.
Anyway, I've had my rant. I'm frustrated. Why is it so easy for developers using InteliJ to just tell the facet here is the web.xml, here is the faces-config.xml and it just works for them. WHY does eclipse / jboss tools/ whatever other plugin jboss tools relies go bananas if I don't have my project set out like it wants it.
Has anyone had success in getting all the features of jboss tools to work on a project where the layout is not 'standard'.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/592592#592592]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years