[jBPM] - drools-guvnor: build package failures
by Renzo Tomaselli
Renzo Tomaselli [http://community.jboss.org/people/Tomarenz] created the discussion
"drools-guvnor: build package failures"
To view the discussion, visit: http://community.jboss.org/message/619912#619912
--------------------------------------------------------------
Hi, I imported several process definition examples from Eclipse into Guvnor: Looping, HumanTask, BPMN2-ExclusiveSplit, BPMN2-gatewayTest, besides having already my own test example.
First of all, this was a two step sequence since after a couple of imports, processes were listed but their opening showed an empty panel till I got a jboss outOfMemory error. Then the usual jboss stop/restart.
Then I run build package for the defaultPackage and I got several errors for all processes.
The common one is "unable to parse xml : Exception class java.lang.IllegalArgumentException : No interfaces found".
Another one is "unable to parse xml : Exception class org.drools.RuntimeDroolsException : invalid package name".
Indeed the package property was com.sample, so I turned it into defaultPackage. This raised other errors, such as "Parser returned a null Package", and "[ERR 102] Line 12:13 mismatched input 'true' in rule "RuleFlow-Split-com.sample.looping-4-5-DROOLS_DEFAULT"".
Basically I'm totally lost with the designer.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/619912#619912]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
[jBPM] - JUnit test support for jBPM5
by Maciej Swiderski
Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] modified the document:
"JUnit test support for jBPM5"
To view the document, visit: http://community.jboss.org/docs/DOC-17345
--------------------------------------------------------------
There are number of issues that people are facing while working with jBPM and to get help the most useful elements are:
* process definition (BPMN2 file)
* test case that illustrates mentioned issue
As process definition is concerned that is rather straight forward (since we already working with it when encountering the problem),
but with test case it can be bit more complex to give directly to others the driver we use for our case.
So, after struggling for some time with exactly the same issue, I decided to start with small but yet powerful support for test cases for jBPM.
There is already a test case class that we could extend and that already brings some useful elements but that is not all we need...
I tried to build up a small library that is dedicated to test cases based on JUnit and that aligns with latest releases of JUnit, meaning it is
based on annotations. So to move directly what I am referring to, lets take a look at very simple test case:
@RunWith(JbpmJUnitRunner.class)
@KnowledgeBase(source={"script.bpmn2"})
@KnowledgeSession()
public class JbpmJUnitTestCase {
protected org.drools.KnowledgeBase knowledgeBase;
protected StatefulKnowledgeSession session;
@Test
public void testScriptTask() {
ProcessInstance instance = session.startProcess("ScriptTask");
assertProcessInstanceComplete(instance);
}
}
What you can see here is the most basic test case that allows to execute and assert process instance completion. I think the code is self explanatory so
I jump directly to the annotations that were introduced with this library:
+*@RunWith*+ - this one is standard JUnit annotation that instructs what runner should be used to execute tests
+*@KnowledgeBase*+ - annotation that defines what artifacts should be loaded into knowledge base
Annotation attributes:
* source - list of resources to be loaded (currently only BPMN2 resources are supported)
* sharedKey - name of the key that will be used to cache knowledge based between test cases, so if you have set of resources that are used across various
test cases and you want to avoid building knowledge base for each of the test cases sharedKey attribute should be set to load knowledge base only one time
+*@KnowledgeSession*+ - annotation that defines how stateful sessions should be created and maintained
Annotation attributes:
* disposePerTest - defines if session should be disposed after each test within test case, default set to true
* logger - defines what working memory logger should be configured for the session, available options NONE (default), CONSOLE, JPA
* handlers - set of work item handlers that will be registered for each session (WorkItemHandler annotation)
* persistence - defines persistence for the session (Persistence annotation)
+*@Persistence*+ annotation attributes:
* persistenceUnit - name of the persistence unit that should be used while configuring JPA entity manager factory
* reloadSession - defines if session should be reloaded (with the same id) between test invocation within test case, default false
+*@WorkItemHandler*+ annotation attributes:
* taskName - name of the task the handler is registered for
* handles - class of the handler
+*@HumanTaskSupport*+ - annotation that instructs runner that test case requires Human Task interactions so it will initialize Task Server accessible via MINA transport
it will be started on test case scope, meaning that all tests will have access to the same instance of the server within test case.
Annotation attributes:
* users - list of user ids that should be added to the task server on startup
* groups - list of groups that should be added to the task server on startup
* persistanceUnit - name of the persistence unit that should be used while building entity manager factory
* host - interface on which task server should be started, defaults to localhost
* port - port on which task server should be started, defaults to 9123
In addition to annotation there are two property files required when configuring session persistence or human task server:
* datasource.properties - defines parameters of connection pool
* jndi.properties - defines JNDI provider for bitronix
NOTE: Connection pool will be created for entire test phase once datasource.properties file was discovered.
Obviously following files are required as well, since they are required by jbpm and task server artifacts:
* META-INF/persistence.xml that defines both (jbpm and human task persistence units)
* META-INF/JBPMorm.xml
* META-INF/Taskorm.xml
Main concept is around injecting dependencies into your test case class. As dependencies I mean following items:
* Knowledge base
* Stateful session
* Task client
Methods from JUnit life cycle are still available, such as these annotated with @Before, @After, @BeforeClass, @AfterClass. Instance methods (@Before @After) will
have access to session and knowledge base, for instance if some facts should be inserted before running the test.
There is one more item that is worth to mention, an assert class dedicated to jbpm - JbpmAssert, which defines (at the moment):
* assertProcessInstanceComplete
* assertProcessInstanceActive
* assertProcessInstanceAborted
* assertProcessInstancePending
* assertProcessInstanceSuspended
and most likely more to come...
*And now, its time to show some examples of it*
Simple test case with session persistence:
@RunWith(JbpmJUnitRunner.class)
@KnowledgeBase(source={"script.bpmn2"})
@KnowledgeSession(persistence=@Persistence(persistenceUnit="org.jbpm.persistence.jpa"))
public class JbpmJUnitTestCase {
protected org.drools.KnowledgeBase knowledgeBase;
protected StatefulKnowledgeSession session;
@Test
public void testScriptTask() {
ProcessInstance instance = session.startProcess("ScriptTask");
assertProcessInstanceComplete(instance);
}
}
If session reload is desired between tests test case should be defined as follows:
@RunWith(JbpmJUnitRunner.class)
@KnowledgeBase(source={"script.bpmn2"})
@KnowledgeSession(persistence=@Persistence(persistenceUnit="org.jbpm.persistence.jpa", reloadSession=true))
public class JbpmJUnitTestCase {
protected org.drools.KnowledgeBase knowledgeBase;
protected StatefulKnowledgeSession session;
@Test
public void testScriptTask() {
ProcessInstance instance = session.startProcess("ScriptTask");
assertProcessInstanceComplete(instance);
}
@Test
public void testScriptTask2() {
ProcessInstance instance = session.startProcess("ScriptTask");
assertProcessInstanceComplete(instance);
}
}
Both tests will use same session.
Last but not least, human interaction test case:
@RunWith(JbpmJUnitRunner.class)
@KnowledgeBase(source={"script.bpmn2","usertask.bpmn2"}, sharedKey="common")
@KnowledgeSession(handlers={@WorkItemHandler(taskName="Human Task", handler=WSHumanTaskHandler.class)}, logger=Logger.CONSOLE)
@HumanTaskSupport(persistenceUnit="org.jbpm.task", users={"john", "Administrator"})
public class JbpmJUnitRunnerTest {
protected org.drools.KnowledgeBase knowledgeBase;
protected StatefulKnowledgeSession session;
protected TaskClient taskClient;
@Test
public void testHumanTask() throws Exception {
ProcessInstance instance = session.startProcess("UserTask");
Thread.sleep(1000);
BlockingTaskSummaryResponseHandler taskSummaryHandler = new BlockingTaskSummaryResponseHandler();
taskClient.getTasksAssignedAsPotentialOwner("john", "en-UK", taskSummaryHandler);
assertEquals(1, taskSummaryHandler.getResults().size());
TaskSummary task1 = taskSummaryHandler.getResults().get(0);
BlockingTaskOperationResponseHandler taskOperationHandler = new BlockingTaskOperationResponseHandler();
taskClient.claim(task1.getId(), "john", taskOperationHandler);
taskOperationHandler = new BlockingTaskOperationResponseHandler();
taskClient.start(task1.getId(), "john", taskOperationHandler);
taskOperationHandler.waitTillDone(1000);
taskOperationHandler = new BlockingTaskOperationResponseHandler();
taskClient.complete(task1.getId(), "john", null, taskOperationHandler);
taskOperationHandler.waitTillDone(1000);
Thread.sleep(1000);
assertProcessInstanceComplete(instance);
}
}
In the example we can notice several configurations elements:
* knowledge base is configured to be shared between test cases under 'common' shared key
* knowledge session will have registered handler for 'Human Task' work items
* knowledge session will have a console logger configured
* human task server will be configured with 'org.jbpm.task' persistence unit and will add two users once it's started (john, Administrator)
Ok, so that is it! I hope you can provide some feedback about it and hopefully we can get a valuable discussion around it and what's even more important
maybe we start using it on daily basis so everybody could benefit from it.
Attached draft version of the library.
Looking forward to your comments
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-17345]
Create a new document in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years
[JBoss Tools] - JBoss Tools Shift Happens in M4
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools Shift Happens in M4"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...
--------------------------------------------------------------
Shift Happens in the last planned milestone of JBoss Tools 3.3. Read on for more...
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.3 M4 (Shift Happens)
[ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.
This time around we are adding in a central hub for users called JBoss Central, support for OpenShift, some OSGi magic, Runtime downloads and more...
h2. Installation
As always, get and install http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you get majority of the dependencies letting you save bandwidth:
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The updatesite URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
h3. JBoss Central
First time you install JBoss Tools M4 you will be greeted with what we've named JBoss Central. JBoss Central is a hub for getting easy access to Project Wizards, Examples, jboss.org news and additional Eclipse plugin installation.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png
It will show up on every startup by default which if you don't want it can be disabled in preferences. The editor will also show up when there are new updates to JBoss Tools plugins installed.
If you want to open central later you can find it under *Help > JBoss Central*.
h3. OpenShift Express
OpenShift Express by Red Hat provides free, auto-scaling platform-as-a-service for Java, Ruby, PHP, Perl and Python applications. Until now to use it you've had to use command line tools like git and rhc-* commands; with JBoss Tools support for OpenShift you can do all of the hard work in the comfort of Eclipse.
To get started use the OpenShift Express Application Wizard available from *File > New > OpenShift*.
http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png
If you are a new user the wizard will walk you through the needed steps to setup an account, create domain and create applications.
If you are an existing user with existing applications it will allow you to log in, choose an application and import the project into Eclipse and in case of it being a JBoss 7 type application we will even setup a server for you in Eclipse server view that allows you to easily publish directly to OpenShift.
This publish is just a Git commit & push which you can also do from command line or manually via eGit in Eclipse - but with the server adapter integration you get a simple and easy way of doing it without having to deal with git manually.
h2. Materialize Library
Eclipse likes to encapsulate jar library access in Classpath Container's and sometimes these classpath containers are great to begin with but for various reasons you might want to decouple your Eclipse projects from the plugin providing the classpath container or maybe you've used one of the great Project Examples or quickstarts we provide via JBoss Central but you don't want to use Maven to manage your libraries/build then this feature also comes handy.
We've added an experimental feature named "Materialize Library" which is available in the context menu of classpath containers in Eclipse.
http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-... http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-...
Once you click that JBoss Tools will present you with a dialog asking where to put the libraries and once you press Ok your project will no longer be dependent on the classpath container, but instead have a copy of the jars and all configured as it was inside Java Build path still; allowing you to more easy build and migrate your project to another setup if need be.
h3. Richfaces 4
We've implemented support in the visual page editor for the new and updated JSF components in Richfaces 4.
http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png
h3. CDI & Seam Solder
The CDI tooling this time around continues to add more quick fixes, improved navigation and adds an "Open Named CDI Bean" dialog for easy lookup of named CDI beans.
http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png
It also adds support for the new package naming in Seam 3.1.Beta4 for the Solder and Config modules, while still maintaing support for previous Seam 3 releases.
h3. Forge in Color
Forge console now has better editing, is now using color rendering and is made easily available with the new Ctrl+4 (or Cmd+4 on OSX) shortcut.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4279-17274/fo... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4279-1727...
h2. JBoss OSGi
The JBoss adapter now supports dragging Eclipse PDE (OSGi) projects to the server and it will use the default PDE export to create and bundle the archive.
h2. Runtime downloads
JBoss Tools now provide easy access to download runtimes such as JBoss AS and Seam (more to be added in the future).
This feature are directly available from JBoss Tools Runtime Detection preference page.
http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png
or via use of Project Examples that requires a runtime.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png
The downloaded runtimes will be installed in a directory of your choosing and will be configured to be ready for use within Eclipse/JBoss Tools.
h3. And more...
There are additional screenshot and features to browse over at http://docs.jboss.org/tools/whatsnew/ What's New & Noteworthy
This is our last planned milestone, beta is next thus its time to make your voice heard and speak up if there are features that aren't giving you what you need.
Leave a comment to let us know!
And as always,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...]
13 years
[JBoss Tools] - JBoss Tools Shift Happens in M4
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools Shift Happens in M4"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...
--------------------------------------------------------------
Shift Happens in the last planned milestone of JBoss Tools 3.3. Read on for more...
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.3 M4 (Shift Happens)
[ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.
This time around we are adding in a central hub for users called JBoss Central, support for OpenShift, some OSGi magic, Runtime downloads and more...
h2. Installation
As always, get and install http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you get majority of the dependencies letting you save bandwidth:
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The updatesite URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
h3. JBoss Central
First time you install JBoss Tools M4 you will be greeted with what we've named JBoss Central. JBoss Central is a hub for getting easy access to Project Wizards, Examples, jboss.org news and additional Eclipse plugin installation.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png
It will show up on every startup by default which if you don't want it can be disabled in preferences. The editor will also show up when there are new updates to JBoss Tools plugins installed.
If you want to open central later you can find it under *Help > JBoss Central*.
h3. OpenShift Express
OpenShift Express by Red Hat provides free, auto-scaling platform-as-a-service for Java, Ruby, PHP, Perl and Python applications. Until now to use it you've had to use command line tools like git and rhc-* commands; with JBoss Tools support for OpenShift you can do all of the hard work in the comfort of Eclipse.
To get started use the OpenShift Express Application Wizard available from *File > New > OpenShift*.
http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png
If you are a new user the wizard will walk you through the needed steps to setup an account, create domain and create applications.
If you are an existing user with existing applications it will allow you to log in, choose an application and import the project into Eclipse and in case of it being a JBoss 7 type application we will even setup a server for you in Eclipse server view that allows you to easily publish directly to OpenShift.
This publish is just a Git commit & push which you can also do from command line or manually via eGit in Eclipse - but with the server adapter integration you get a simple and easy way of doing it without having to deal with git manually.
h2. Materialize Library
Eclipse likes to encapsulate jar library access in Classpath Container's and sometimes these classpath containers are great to begin with but for various reasons you might want to decouple your Eclipse projects from the plugin providing the classpath container or maybe you've used one of the great Project Examples or quickstarts we provide via JBoss Central but you don't want to use Maven to manage your libraries/build then this feature also comes handy.
We've added an experimental feature named "Materialize Library" which is available in the context menu of classpath containers in Eclipse.
http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-... http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-...
Once you click that JBoss Tools will present you with a dialog asking where to put the libraries and once you press Ok your project will no longer be dependent on the classpath container, but instead have a copy of the jars and all configured as it was inside Java Build path still; allowing you to more easy build and migrate your project to another setup if need be.
h3. Richfaces 4
We've implemented support in the visual page editor for the new and updated JSF components in Richfaces 4.
http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png
h3. CDI & Seam Solder
The CDI tooling this time around continues to add more quick fixes, improved navigation and adds an "Open Named CDI Bean" dialog for easy lookup of named CDI beans.
http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png
It also adds support for the new package naming in Seam 3.1.Beta4 for the Solder and Config modules, while still maintaing support for previous Seam 3 releases.
h3. Forge in Color
Forge console now has better editing, is now using color rendering and is made easily available with the new Ctrl+4 (or Cmd+4 on OSX) shortcut.
http://docs.jboss.org/tools/whatsnew/forge/images/3.3.0.M4/forge_colors.png http://docs.jboss.org/tools/whatsnew/forge/images/3.3.0.M4/forge_colors.png
h2. JBoss OSGi
The JBoss adapter now supports dragging Eclipse PDE (OSGi) projects to the server and it will use the default PDE export to create and bundle the archive.
h2. Runtime downloads
JBoss Tools now provide easy access to download runtimes such as JBoss AS and Seam (more to be added in the future).
This feature are directly available from JBoss Tools Runtime Detection preference page.
http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png
or via use of Project Examples that requires a runtime.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png
The downloaded runtimes will be installed in a directory of your choosing and will be configured to be ready for use within Eclipse/JBoss Tools.
h3. And more...
There are additional screenshot and features to browse over at http://docs.jboss.org/tools/whatsnew/ What's New & Noteworthy
This is our last planned milestone, beta is next thus its time to make your voice heard and speak up if there are features that aren't giving you what you need.
Leave a comment to let us know!
And as always,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...]
13 years
[Beginner's Corner] - Application specific (per-deplyoment) logging AS6 final and correct reference to Logger
by Pasquale Imbemba
Pasquale Imbemba [http://community.jboss.org/people/pi4630] created the discussion
"Application specific (per-deplyoment) logging AS6 final and correct reference to Logger"
To view the discussion, visit: http://community.jboss.org/message/635682#635682
--------------------------------------------------------------
Hi,
I've applied the changes to my logmanager-jboss-beans.xml as described https://issues.jboss.org/browse/JBAS-9407 here. When I startup my JBoss AS, I get the following error:
ERROR [ProfileServiceBootstrap] (Thread-2) Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "Logging:REGISTRATION:Mercurius:Anonymous-0" is missing the following dependencies:
Dependency "JBossLogManagerContextSelectorService" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'JBossLogManagerContextSelectorService' **")
DEPLOYMENTS IN ERROR:
Deployment "JBossLogManagerContextSelectorService" is in error due to the following reason(s): ** NOT FOUND Depends on 'JBossLogManagerContextSelectorService' **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
The application specific jboss-logging.xml is inside META-INF folde of my application, which is deployed as JAR. The file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!-- My application jboss-logging.xml -->
<logging xmlns="urn:jboss:logging:6.0" context="Mercurius">
<!-- ~ This element, in conjunction with the "context" attribute above,
tells the ~ logging system that I want my own separate logging environment. -->
<define-context name="Mercurius" />
<!-- Just an example handler. -->
<file-handler file-name="/home/pb26683/Pippo.log" name="FILE"
autoflush="true" append="true">
<formatter>
<pattern-formatter pattern="%d %-5p [%c] (%t) %s%E%n" />
</formatter>
<properties>
<property name="encoding">UTF-8</property>
</properties>
</file-handler>
<!-- Configure the root logger with my handler from above -->
<root-logger>
<level name="INFO" />
<handlers>
<handler-ref name="FILE" />
</handlers>
</root-logger>
</logging>
Why is "JBossLogManagerContextSelectorService" the state "missing"?
A more general question: from my SLSB, I refer to the org.jboss.logging.Logger this way:
org.jboss.logging.Logger;
Should it be referenced by annotation instead?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/635682#635682]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
[JBoss Tools] - JBoss Tools Shift Happens in M4
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools Shift Happens in M4"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...
--------------------------------------------------------------
Shift Happens in the last planned milestone of JBoss Tools 3.3. Read on for more...
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.3 M4 (Shift Happens)
[ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.
This time around we are adding in a central hub for users called JBoss Central, support for OpenShift, some OSGi magic, Runtime downloads and more...
h2. Installation
As always, get and install http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you majority of the dependencies letting you save bandwidth:
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The updatesite URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
h3. JBoss Central
First time you install JBoss Tools M4 you will be greeted with what we've named JBoss Central. JBoss Central is a hub for getting easy access to Project Wizards, Examples, jboss.org news and additional Eclipse plugin installation.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraleditor.png
It will show up on every startup by default which if you don't want it can be disabled in preferences. The editor will also show up when there are new updates to JBoss Tools plugins installed.
If you want to open central later you can find it under *Help > JBoss Central*.
h3. OpenShift Express
OpenShift Express by Red Hat provides free, auto-scaling platform-as-a-service for Java, Ruby, PHP, Perl and Python applications. Until now to use it you've had to use command line tools like git and rhc-* commands; with JBoss Tools support for OpenShift you can do all of the hard work in the comfort of Eclipse.
To get started use the OpenShift Express Application Wizard available from *File > New > OpenShift*.
http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png http://docs.jboss.org/tools/whatsnew/openshift/images/applications.png
If you are a new user the wizard will walk you through the needed steps to setup an account, create domain and create applications.
If an existing user with existing applications it will allow you to log in, choose an application and import the project into Eclipse and in case of it being a JBoss 7 type application we will even setup a server for you in Eclipse server view that allows you to easily publish directly to OpenShift.
This publish is behind a scenes just a Git commit & push which you can also do from command line or manually via eGit in Eclipse - but with the server adapter integration you get a simple and easy way of doing it without having to deal with git manually.
h2. Materialize Library
Eclipse likes to encapsulate jar library access in Classpath Container's and sometimes these classpath containers are great to begin with but for various reasons you might want to decouple your Eclipse projects from the plugin providing the classpath container or maybe you've used one of the great Project Examples or quickstarts we provide via JBoss Central but you don't want to use Maven to manage your libraries/build then this feature also comes handy.
We've added an experimental feature named "Materialize Library" which is available in the context menu of classpath containers in Eclipse.
http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-... http://docs.jboss.org/tools/whatsnew/core/images/materialize-lib-context-...
Once you click that JBoss Tools will present you with a dialog asking where to put the libraries and once you press Ok your project will no longer be dependent on the classpath container, but instead have a copy of the jars and all configured as it was inside Java Build path still; allowing you to more easy build and migrate your project to another setup if need be.
h3. Richfaces 4
We've implemented support in the visual page editor for the new and update JSF components in Richfaces 4.
http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.M4/8950.png
h3. CDI & Seam Solder
The CDI tooling this time around continues to add more quick fixes, improved navigation and adds a "Open Named CDI Bean" dialog for easy lookup of named CDI beans.
http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png http://docs.jboss.org/tools/whatsnew/cdi/images/3.3.0.M4/openNamed.png
It also adds support for the new package naming in Seam 3.1.Beta4 for the Solder and Config modules, while still maintaing support for previous Seam 3 releases.
h3. Forge in Color
Forge console now has better editing, is now using color rendering and is made easily available with the new Ctrl+4 (or Cmd+4 on OSX) shortcut.
http://docs.jboss.org/tools/whatsnew/forge/images/3.3.0.M4/forge_colors.png http://docs.jboss.org/tools/whatsnew/forge/images/3.3.0.M4/forge_colors.png
h2. JBoss OSGi
The JBoss adapter now supports dragging Eclipse PDE (OSGi) projects to the server and it will use the default PDE export to create and bundle the archive.
h2. Runtime downloads
JBoss Tools now provide easy access to download runtimes such as JBoss AS and Seam (more to be added in the future).
This feature are directly available from JBoss Tools Runtime Detection preference page.
http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png http://docs.jboss.org/tools/whatsnew/as/images/runtimedownload1.png
or via use of Project Examples that requries a runtime.
http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png http://docs.jboss.org/tools/whatsnew/images/jbosscentraldownloadas.png
The downloaded runtimes will be installed in a directory of your choosing and will be configured to be ready for use within Eclipse/JBoss Tools.
h3. And more...
There are additional screenshot and features to browse over at http://docs.jboss.org/tools/whatsnew/ What's New & Noteworthy
This is our last planned milestone, beta is next thus its time to make your voice heard and speak up if there are features that aren't giving you what you need.
Leave a comment to let us know!
And as always,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/11/09/jboss-tools-sh...]
13 years
[JBoss Cache] - NullPointer in PojoCache
by Grzegorz Jamka
Grzegorz Jamka [http://community.jboss.org/people/scottgj] created the discussion
"NullPointer in PojoCache"
To view the discussion, visit: http://community.jboss.org/message/635673#635673
--------------------------------------------------------------
Hi,
Versions:
JBossCache - 3.1.0.GA
PojoCache - 3.0.0.GA
During my endurance tests I get such exceptions
1)
org.jboss.cache.pojo.PojoCacheException: detach failed /parlayRa/TEST_NODES/18-12883
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:134)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:221)
at org.mobicents.slee.resource.parlay.util.replication.CacheBase.removeObject(CacheBase.java:74)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove_aroundBody0(TestRemovePojoCache.java:14)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove_aroundBody1$advice(TestRemovePojoCache.java:96)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove(TestRemovePojoCache.java:1)
at pl.ivmx.pojocache.PeriodicCacheLoader.run(PeriodicCacheLoader.java:72)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at org.jboss.cache.pojo.impl.InternalHelper.cleanUp(InternalHelper.java:261)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.removeObject(PojoCacheDelegate.java:264)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:126)
... 12 more
2)
org.jboss.cache.pojo.PojoCacheException: detach failed /parlayRa/TEST_NODES/2-67790
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:134)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:221)
at org.mobicents.slee.resource.parlay.util.replication.CacheBase.removeObject(CacheBase.java:74)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove_aroundBody0(TestRemovePojoCache.java:14)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove_aroundBody1$advice(TestRemovePojoCache.java:96)
at pl.ivmx.pojocache.cache.TestRemovePojoCache.remove(TestRemovePojoCache.java:1)
at pl.ivmx.pojocache.PeriodicCacheLoader.run(PeriodicCacheLoader.java:72)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at org.jboss.cache.pojo.impl.InternalHelper.isMultipleReferenced(InternalHelper.java:180)
at org.jboss.cache.pojo.impl.ObjectGraphHandler.isMultipleReferenced(ObjectGraphHandler.java:79)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.removeObject(PojoCacheDelegate.java:253)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:126)
... 12 more
Does enybody know why?
How to reporoduce error:
To start a test you have to:
1) Copy pojo cache configuration on two nodes (I have cluster comprised from two nodes in LAN)
1a) My JVM config (on both nodes):
JAVA_OPTS="-Xms1200m -Xmx1200m -XX:NewSize=150m -XX:MaxNewSize=150m -XX:MaxPermSize=128m -XX:SurvivorRatio=15 -XX:+UseTLAB -XX:TLABSize=64k -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:MaxTenuringThreshold=32 -XX:CMSInitiatingOccupancyFraction=66"
1b)
2) Deploy web app on one of node
3) Go to web app web page
http://firstnode_ip:8080/pojocache-load-test/index http://firstnode_ip:8080/pojocache-load-test/index
4) Choose section
h4. Test with all remove operations running constantly.
and enter values:
Number of members per second: 500
Object live time in ms: 180000
and Run test.
Error should be shown after memory allocated on heap reachs its upper limit (from top totally allocated memory shows about 1.6GB)
Best regards,
Grzegorz Jamka
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/635673#635673]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
