[Beginner's Corner] - The warning message stomp out.
by Darryl Baker
Darryl Baker [http://community.jboss.org/people/dpbaker57] created the discussion
"The warning message stomp out."
To view the discussion, visit: http://community.jboss.org/message/583432#583432
--------------------------------------------------------------
I'm new to being a web admin. As a system admin I didn't like spurious messages in my logs and did what was needed to get rid of them.
I've joined a company as a Unix/Web admin. They have beed using JBoss for several years. I fined during the JBoss startup several warning messages on ever installation they have. I know they are not causing functional problems but my version of OCD requires me to try to fix them.
Most of the deployed environments are 4.0.5 but we are in the process of moving the latest implementation of our software to 6.0. So I would like to set the configuration instruction for new environments such that these messages never occur. I have already fixed a simple log4j file issue and a Jakarta plugin issue. Now I'd like to fix some other message the first is this series:
[ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:43,566 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
16:14:43,676 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:43,770 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp3718574988013474295jbossws-context-exp.war/
16:14:43,879 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:44,035 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
16:14:44,113 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:45,145 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
16:14:45,363 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
Which I think should be fixable by defining a security role in server/myserver/deploy/jbossweb-tomcat55.sar/conf/web.xml but I don't understand how to do that well enough. I'm also not sure how to debug my attempts.
The next error message is:
[STDERR] The developer file [null] does not exist and will not be used.
Obviously we are not using a developer file but what is it? What are the possible values? Where should it be set? Since we are not using it how do I set it to a value that does not break the applications yet has the eqivalent effect as now but without an error message.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583432#583432]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[EJB3] - Cancelling an @Asynchronous method with Future.cancel
by david_b
david_b [http://community.jboss.org/people/david_b] created the discussion
"Cancelling an @Asynchronous method with Future.cancel"
To view the discussion, visit: http://community.jboss.org/message/583431#583431
--------------------------------------------------------------
I am writing an enterprise Java application that uses aynchronous EJB 3.1 methods to execute a number of tasks in parallel. The app is currently running on JBoss AS 6.0.0 Final.
To support cancelling a long running task I have been attempting to use the Future interface. Unfortunately calling future.cancel(true)appears to have no effect on the session context of the bean executing the task, despite the fact that cancel is returning true.
I have a simple interface:
public interface AsyncInterface
{
Future run() throws Exception;
}
With a bean implementation as follows:
@Stateless(a)Remote(AsyncInterface.class)public class AsyncBean{ @Resource SessionContext myContext; @Asynchronous public Future(result); }}
The asynchronous method is called from another Stateless EJB like so:
InitialContext ctx = new InitialContext();AsyncInterface async = (AsyncInterface)ctx.lookup("AsyncBean/remote");Future future = async.run();if( future.cancel(true) ){ System.out.println("future.cancel() returned true");}else{ System.out.println("future.cancel() returned false");}
The output from the AsyncBean is an endless stream of "Working"; it never detects the cancellation.
I haven't found much sample code using Futures to cancel an @Asynchronous EJB call. Is using the session context the correct way of checking for cancellation? Is there a better method for cancelling the asynchronous call?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583431#583431]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[jBPM] - Console Server
by Amin Mohammed-Coleman
Amin Mohammed-Coleman [http://community.jboss.org/people/aminmc] created the discussion
"Console Server"
To view the discussion, visit: http://community.jboss.org/message/583395#583395
--------------------------------------------------------------
Hi
I would like to use the gwt-console-server in order to monitor and inspect workflow processes. I understand there are RESTful urls to inspect process instances and get images (i'm not sure if this image indicates what the active nodes in the process are). I have been trying to follow the discussion which shows how to integrate the console with standalone tomcat however I have come across some problems. I have the following project structure for my workflow application:
src/main/resources/bpmn/...
src/main/resources/META-INF/orm.xml
src/main/resources/META-INF/persistence.xml
I copied over the necessary jars into the lib directory of my tomcat installation and updated my context.xml in the conf directory of my tomcat to be
In the catalina.bat I have added the following:
-Djbpm.console.directory={location of the bpmn files}
I presume I don't need guvnor running...
When I execute the following:
curl ... " http://localhost:8080/gwt-console-server/rs../instance/ http://localhost:8080/gwt-console-server/rs../instance/{1} (sorry I can't remember the full url) I get the following exception:
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
</pre></p><p><b>root cause</b> <pre>javax.persistence.PersistenceException: No Persistence provider for EntityManager named org.dr
ools.persistence.jpa
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:56)
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:1
Am i following the right steps? Any help would be appreciated.
Thanks
Amin
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583395#583395]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months