Greg:
I read a bug about something similar on bugs.eclipse.org. It seems the user there was using the webtools "generic server" adapter for JBoss, which is not what we use here. We use a custom server adapter.
I suspect strongly you're using the same thing.
The only thing I can think of to help you is that there is probably, somewhere in your plugins folder, a jboss-related xml file which the generic server uses to configure ports and such.
The folder should be something like: eclipse\plugins\org.eclipse.jst.server.generic.jboss_1.5.1.v200609140551\servers\jboss.serverdef
But, we suggest you use JBoss IDE instead ;)
If I'm wrong and you're not using the generic jboss server, feel free to respond. (You can tell by watching which category you create your server in. JBoss vs JBoss Inc. JBoss Inc. is the one we create / support. JBoss is provided by webtools.)
Take luck.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008855#4008855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008855
anonymous wrote :
| What is the recommendation to start/manage background worker threads in JBoss 4.0.x?
|
There is nothing to prevent you from developing a custom MBean that uses threads or a thread pool to preform background tasks. Simple wrap your Runnable/Thread stuff in an MBean and that's that. Also, JMX is nice for configuration/management as well. This would be my suggestion.
You could develop a custom JCA adapter that's sole purpose is to give EJB and Servlets access to the WorkManagement API but this is a bit heavy when a simple MBean would really suffice.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008854#4008854
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008854
Best of luck ;-)
As far as the
anonymous wrote :
| Can anybody tell me in what kind of security and transaction context the work thread will run?
|
The answer is that it will be unspecified being that the WorkManager API is meant to be consumed solely from a ResourceAdapter which would have it's own transaction/security context. In other words, it is unknown and there are no guarantees because this is a non standard use of the API.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008852#4008852
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008852
Thank You Weston.
Then let me ask the more generic question:
What is the recommendation to start/manage background worker threads in JBoss 4.0.x?
Using JMS for a long running process seems to be discouraged (like 5 minutes of background work)
I can implement a Runnable/Thread class and manage it myself but per J2EE protocol this is not recommended. Threads are supposed to be managed by the app server.
Thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008846#4008846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008846