[jBPM] - Re: everything blocked after trying to edit from Guvnor
by Renzo Tomaselli
Renzo Tomaselli [http://community.jboss.org/people/Tomarenz] created the discussion
"Re: everything blocked after trying to edit from Guvnor"
To view the discussion, visit: http://community.jboss.org/message/616311#616311
--------------------------------------------------------------
I cannot see such a button ("about" says Version 5.2.0 final). Anyway from the lib dir I see designer-1.0.0.052-jboss.war (reinstalled jBpm yesterday).
Server log, many errors:
2011-07-19 15:03:46,151 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/drools-guvnor].[PackageDeploymentServlet]] (http-localhost%2F127.0.0.1-8080-5) Servlet.service() for servlet PackageDeploymentServlet threw exception
javax.jcr.PathNotFoundException: drools:repository/drools:package_area
at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2437)
at org.drools.repository.RulesRepository.getAreaNode(RulesRepository.java:209)
Many of:
ERROR 19-07 16:28:10,473 (LoggingHelper.java:error:69) Blocked request without GWT permutation header (XSRF attack?)
java.lang.SecurityException: Blocked request without GWT permutation header (XSRF attack?) at com.google.gwt.user.server.rpc.RemoteServiceServlet.checkPermutationStrongName(RemoteServiceServlet.java:272)
A couple of:
ERROR 19-07 17:25:33,804 (UserInfo.java:<init>:51) Unable to init UserInfo
javax.jcr.RepositoryException: failed to resolve path relative to node /drools:repository/user_info
at org.apache.jackrabbit.core.NodeImpl.resolveRelativePath(NodeImpl.java:249)
and the final killer:
2011-07-19 17:43:11,910 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http-localhost%2F127.0.0.1-8080-2) An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
at java.util.LinkedHashMap.createEntry(LinkedHashMap.java:424)
By "stuck" I meant never returning.
I don't know jboss enough to be selective in killing its processes (Win7 64 bits), so rebooting was my last chance.
Renzo
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616311#616311]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
[jBPM] - jBPM 5 database testing
by Marco Rietveld
Marco Rietveld [http://community.jboss.org/people/marco.rietveld] modified the document:
"jBPM 5 database testing"
To view the document, visit: http://community.jboss.org/docs/DOC-17071
--------------------------------------------------------------
*Note: the actual implementation of this has not yet been merged into the trunk of jBPM!*
In order to allow testing to be done on other databases (instead of H2), the following has been done:
- Overview of modifications
- Explanation
- How to test on other databases
h3. Overview of modifications
The jbpm pom.xml (artifact jbpm) now contains:
** Properties to be used to connect to the database of choice
** A database profile that can be used in order to inject a dependency for the jdbc driver jar for the database
** An example profile, which has been commented out, which shows how do test without using a settings file
2. A org.jbpm.persistence.util.PersistenceUtil class has been added to the jbpm-persistence-jpa module.
3. The jbpm-persistence-jpa module now also has a test-jar goal: the test-jar produced contains the PersistenceUtil class mentioned above.
4. In the modules in which persistence is used during testing, the following modifications have been made:
* A datasource.properties file has been added to the src/test/resources directory.
* The pom.xml of the module has been modified so that filtering has been turned on for the src/test/resources directory.
* The persistence.xml file in src/test/resources/META-INF has been modified so that the hibernate.connection.* properties use variables.
How all of these modifications fit together is explained in the following section.
h3. Explanation
We essentially use maven to inject the values we want into the persistence configuration.
Unfortunately, because XA datasource configuration is not uniform across different database vendors, there is also a utility class (org.jbpm.persistence.util.PersistenceUtil) which contains database specific XA datasource configuration and which we use to initiate and configure the XA datasource when testing.
An explanation follows the diagram below:
http://community.jboss.org/servlet/JiveServlet/showImage/102-17071-3-1676... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-17071-3-...
h5. A. Pom.xml and maven settings:
Properties
The jbpm project root pom (jbpm artifact) contains a number of maven.* properties: a number of these settings are empty, and those that aren't are set to the h2 defaults.
However, we can create a local settings.xml file and run the following:
mvn clean test -ssettings-db.xml -Pdatabase
(The -Pdatabase is explained below)
By filling a local settings.xml file with the jdbc values that we want for, for example, our local PostgreSQL database, we can then use those values later on when running our tests.
Otherwise, we can also directly modify the pom.xml itself and fill the values in there.
Using a profile to inject a dependency
The -Pdatabase option in the mvn command above tells maven to use the profile that has an id of "database".
In the project root pom, we have also defined a "database" profile that uses a dependency. By setting the maven.jdbc.driver.jar property (in either the pom.xml or the settings.xml file that you use) to the path of the appropriate jdbc driver class jar, we can then ensure that the database specific driver classes are available to our tests.
[Depending on demand, we could also add properties to the pom.xml so that the groupId, artifactId, and version of the driver class jar (instead of a system path) are defined and used]
h5. B. Filtering and the datasource.properties and hibernate.xml files:
In the pom.xml of the module in which the testing is done (for example, jbpm-persistence-jpa or jbpm-bam), the following has also been added to the <build> section of the module pom:
<build>
...
<testResources>
<testResource>
<directory>src/test/resources</directory>
<filtering>true</filtering>
</testResource>
</testResources>
...
</build>
When maven runs the process-test-resources goal, it +filters+ all files in and under the src/main/resources directory. Any properties that have been defined in the (effective) pom.xml being processed by maven, will be replaced with the values that have been assigned to them.
In this case, the following two files in src/main/resources that are filtered for us:
* datasource.properties
* META-INF/hibernate.xml
In the PersistenceUtil class, we read in the datasource.properties file. The test-compile and process-test-resources goals ensure that the filtered version of this file -- where all maven variables have been replaced with their assigned values -- is placed in the same class path as the rest of the test classes and jars (target/, namely).
hibernate.xml is used by Hibernate when we instantiate an EntityManager.
h5. C. Using the PersistenceUtil in unit tests:
Lastly, when we write any unit tests that use persistence, instead of configuring the datasource and entityManager ourselves, we use the static methods made available to us from the PersistenceUtil class.
In our test class, we can use something like the following code:
import static org.jbpm.persistence.util.PersistenceUtil.*;
import javax.persistence.EntityManagerFactory;
import javax.persistence.Persistence;
...
import org.junit.After;
import org.junit.Before;
import bitronix.tm.TransactionManagerServices;
import bitronix.tm.resource.jdbc.PoolingDataSource;
public class MyPersistenceTest {
private PoolingDataSource ds1;
private EntityManagerFactory emf;
@Before
public void setUp() throws Exception {
ds1 = setupPoolingDataSource();
ds1.init();
emf = Persistence.createEntityManagerFactory( PERSISTENCE_UNIT_NAME );
}
@After
public void tearDown() throws Exception {
emf.close();
ds1.close();
}
setupPoolingDataSource() is a static method from the PersistenceUtil Class.
Todo:
- datasource configuration logic in PU class
- what the setupPoolingDataSource method does
[Still under progress.. ]
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-17071]
Create a new document in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 8 months
[JBoss Tools] - activate a Modalpanel with commandbutton
by yasser zairi
yasser zairi [http://community.jboss.org/people/yasser_z] created the discussion
"activate a Modalpanel with commandbutton"
To view the discussion, visit: http://community.jboss.org/message/616468#616468
--------------------------------------------------------------
Hi,
i want to activate a modalPanel from a Commandbutton but it seem that is sth wrong .
_______________________________________________________________________________________
here is the code of the ModalPanel with the commandbutton ::
<a4j:commandbutton value="Modifier" ajaxSingle="true" id="editlink"
oncomplete="#{rich:component('editPanel')}.show()" action="#{valeursMBean.viwDetail}" />
<rich:modalPanel id="editPanel" autosized="true" width="450">
<f:facet name="header">
<h:outputText value="Modifier la valeur mobiliere actuelle :" />
</f:facet>
<f:facet name="controls">
<h:panelGroup>
<h:graphicImage value="../style/close.jpeg" id="hidelink"
styleClass="hidelink" />
<rich:componentControl for="editPanel" attachTo="hidelink"
operation="hide" event="onclick" />
</h:panelGroup>
</f:facet>
<h:form>
<rich:messages style="color:red;"></rich:messages>
<h:panelGrid columns="1">
<a4j:outputPanel ajaxRendered="true">
<h:panelGrid columns="2">
<h:outputLabel value="CodeIsin" for="codeIsin" />
<h:inputText id="codeIsin"
value="#{valeursMBean.currentItem.codeIsin}" />
<h:outputLabel value="Categorie" for="categorie" />
<h:inputText id="categorie"
value="#{valeursMBean.currentItem.categorie}" />
<h:outputLabel value="Denomination" for="denomination" />
<h:inputText id="denomination"
value="#{valeursMBean.currentItem.denomination}" />
<h:outputLabel value="Date Echeance" for="dateEcheance" />
<h:inputText id="dateEcheance"
value="#{valeursMBean.currentItem.dateEcheance}" />
<h:outputLabel value="Etat" for="etat" />
<h:inputText id="etat" value="#{valeursMBean.currentItem.etat}"/>
</h:panelGrid>
<rich:message showSummary="true" showDetail="false" for="etat" />
</a4j:outputPanel>
<a4j:commandButton value="Enregistrer"
action="#{valeursMBean.update}"
reRender="codeIsin, categorie, etat, denomination, dateEcheance"
oncomplete="if (#{facesContext.maximumSeverity==null}) #{rich:component('editPanel')}.hide();" />
</h:panelGrid>
</h:form>
</rich:modalPanel>
_______________________________________________________________________________________________
and here is my Bean ::
package cdvm.surv.web;
import java.io.Serializable;
import java.util.Iterator;
import java.util.List;
import javax.annotation.PostConstruct;
import org.richfaces.component.html.HtmlScrollableDataTable;
import org.richfaces.model.ScrollableTableDataModel.SimpleRowKey;
import org.richfaces.model.selection.Selection;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.Scope;
import org.springframework.stereotype.Component;
import cdvm.surv.model.ValeurRef;
import cdvm.surv.service.ValeurRefService;
@Component("valeursMBean")
@Scope("session")
public class ValeursMBean implements Serializable {
@Autowired
private transient ValeurRefService valeurefService;
private transient HtmlScrollableDataTable valeurTable;
private List<ValeurRef> valeurefList;
private ValeurRef currentItem;
@PostConstruct
public void init(){
valeurefList = valeurefService.find();
}
public String update(){
valeurefService.save(currentItem);
init();
return null;
}
public void viewDetail(){
List<ValeurRef> valueList=(List<ValeurRef>) valeurTable.getValue();
Selection sl = valeurTable.getSelection();
Iterator<Object> keys= sl.getKeys();
if(keys.hasNext()){
//SimpleRowKey ky = (SimpleRowKey)keys.next();
currentItem=valueList.get((Integer)keys.next());
System.out.println(currentItem.getCodeIsin());
}
}
// Getter and Setter
public ValeurRef getCurrentItem() {
return currentItem;
}
public void setCurrentItem(ValeurRef currentItem) {
this.currentItem = currentItem;
}
public HtmlScrollableDataTable getValeurTable() {
return valeurTable;
}
public void setValeurTable(HtmlScrollableDataTable valeurTable) {
this.valeurTable = valeurTable;
}
public List<ValeurRef> getValeurefList() {
return valeurefList;
}
public void setValeurefList(List<ValeurRef> valeurefList) {
this.valeurefList = valeurefList;
}
}
________________________________________________________________________________
the error that i get is ::
javax.el.PropertyNotFoundException: /GestionRef/Grid.jsp @86,56 value="#{valeursMBean.currentItem.codeIsin}": Target Unreachable, 'currentItem' returned null
com.sun.facelets.el.TagValueExpression.getType(TagValueExpression.java:62)
com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:81)
javax.faces.component.UIInput.getConvertedValue(UIInput.java:936)
javax.faces.component.UIInput.validate(UIInput.java:861)
javax.faces.component.UIInput.executeValidate(UIInput.java:1071)
javax.faces.component.UIInput.processValidators(UIInput.java:663)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1040)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1040)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1040)
javax.faces.component.UIForm.processValidators(UIForm.java:229)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1040)
javax.faces.component.UIInput.processValidators(UIInput.java:661)
javax.faces.component.UIForm.processValidators(UIForm.java:229)
org.ajax4jsf.component.AjaxViewRoot$3.invokeContextCallback(AjaxViewRoot.java:447)
org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:240)
org.ajax4jsf.component.AjaxViewRoot.processValidators(AjaxViewRoot.java:463)
com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:100)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
i'll be thankful for any suggestions
thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616468#616468]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
[jBPM] - jBPM 5 database testing
by Marco Rietveld
Marco Rietveld [http://community.jboss.org/people/marco.rietveld] modified the document:
"jBPM 5 database testing"
To view the document, visit: http://community.jboss.org/docs/DOC-17071
--------------------------------------------------------------
*Note: the actual implementation of this has not yet been merged into the trunk of jBPM!*
In order to allow testing to be done on other databases (instead of H2), the following has been done:
- Overview of modifications
- Explanation
- How to test on other databases
h3. Overview of modifications
The jbpm pom.xml (artifact jbpm) now contains:
** Properties to be used to connect to the database of choice
** A database profile that can be used in order to inject a dependency for the jdbc driver jar for the database
** An example profile, which has been commented out, which shows how do test without using a settings file
2. A org.jbpm.persistence.util.PersistenceUtil class has been added to the jbpm-persistence-jpa module.
3. The jbpm-persistence-jpa module now also has a test-jar goal: the test-jar produced contains the PersistenceUtil class mentioned above.
4. In the modules in which persistence is used during testing, the following modifications have been made:
* A datasource.properties file has been added to the src/test/resources directory.
* The pom.xml of the module has been modified so that filtering has been turned on for the src/test/resources directory.
* The persistence.xml file in src/test/resources/META-INF has been modified so that the hibernate.connection.* properties use variables.
How all of these modifications fit together is explained in the following section.
h3. Explanation
We essentially use maven to inject the values we want into the persistence configuration.
Unfortunately, because XA datasource configuration is not uniform across different database vendors, there is also a utility class (org.jbpm.persistence.util.PersistenceUtil) which contains database specific XA datasource configuration and which we use to initiate and configure the XA datasource when testing.
An explanation follows the diagram below:
http://community.jboss.org/servlet/JiveServlet/showImage/16760/jBPM_Persi... http://community.jboss.org/servlet/JiveServlet/downloadImage/16760/702-38...
h5. A. Pom.xml and maven settings:
Properties
The jbpm project root pom (jbpm artifact) contains a number of maven.* properties: a number of these settings are empty, and those that aren't are set to the h2 defaults.
However, we can create a local settings.xml file and run the following:
mvn clean test -ssettings-db.xml -Pdatabase
(The -Pdatabase is explained below)
By filling a local settings.xml file with the jdbc values that we want for, for example, our local PostgreSQL database, we can then use those values later on when running our tests.
Otherwise, we can also directly modify the pom.xml itself and fill the values in there.
Using a profile to inject a dependency
The -Pdatabase option in the mvn command above tells maven to use the profile that has an id of "database".
In the project root pom, we have also defined a "database" profile that uses a dependency. By setting the maven.jdbc.driver.jar property (in either the pom.xml or the settings.xml file that you use) to the path of the appropriate jdbc driver class jar, we can then ensure that the database specific driver classes are available to our tests.
[Depending on demand, we could also add properties to the pom.xml so that the groupId, artifactId, and version of the driver class jar (instead of a system path) are defined and used]
h5. B. Filtering and the datasource.properties and hibernate.xml files:
In the pom.xml of the module in which the testing is done (for example, jbpm-persistence-jpa or jbpm-bam), the following has also been added to the <build> section of the module pom:
<build>
...
<testResources>
<testResource>
<directory>src/test/resources</directory>
<filtering>true</filtering>
</testResource>
</testResources>
...
</build>
When maven runs the process-test-resources goal, it +filters+ all files in and under the src/main/resources directory. Any properties that have been defined in the (effective) pom.xml being processed by maven, will be replaced with the values that have been assigned to them.
In this case, the following two files in src/main/resources that are filtered for us:
* datasource.properties
* META-INF/hibernate.xml
In the PersistenceUtil class, we read in the datasource.properties file. The test-compile and process-test-resources goals ensure that the filtered version of this file -- where all maven variables have been replaced with their assigned values -- is placed in the same class path as the rest of the test classes and jars (target/, namely).
hibernate.xml is used by Hibernate when we instantiate an EntityManager.
h5. C. Using the PersistenceUtil in unit tests:
Lastly, when we write any unit tests that use persistence, instead of configuring the datasource and entityManager ourselves, we use the static methods made available to us from the PersistenceUtil class.
[to be continued..]
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-17071]
Create a new document in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 8 months
[jBPM] - Finding a task id during task assignment
by Ayusman Dikshit
Ayusman Dikshit [http://community.jboss.org/people/ayusman_dikshit] created the discussion
"Finding a task id during task assignment"
To view the discussion, visit: http://community.jboss.org/message/616439#616439
--------------------------------------------------------------
All,
is it possible to find the task id that got created when a task is assigned to an user?
in my case, the task gets assigned to an user which is found using a task assignment handler.
However I also need the task id to be stored in an external table, so that another application can invoke the
completion of the specifc task just by doing a
taskservice.completeTask("mySavedTaskId");
Since the task ID that was created as a part of the TASK activity in my JPDL is going to assign tha task automatically, is it possible to have some kind of event-handler/code to achieve this?
I have tried event-handler... but does not seem to work...
<task name="assignTask" assignee="testUser1" g="200,153,92,52">
<on event="start">
<event-listener class="test.TestDemo3">
<field name="msg"><string value="start on activity wait"/></field>
</event-listener>
</on>
<transition name="to java1" to="to_perform_math_op" g="-18,-23"/>
</task>
Please help!!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616439#616439]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
[JBoss Cache] - Re: Invalid character ':' in value part of property
by Mike Duffy
Mike Duffy [http://community.jboss.org/people/mduffy] created the discussion
"Re: Invalid character ':' in value part of property"
To view the discussion, visit: http://community.jboss.org/message/616406#616406
--------------------------------------------------------------
With a breand new version of JBoss 6.0, with no code deployed I see the following error about every hour after starting my server:
05:07:59,517 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] Servlet.service() for servlet HtmlAdapt
or threw exception: javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
at javax.management.ObjectName.construct(ObjectName.java:602) [:1.6.0_26]
at javax.management.ObjectName.<init>(ObjectName.java:1403) [:1.6.0_26]
at org.jboss.jmx.adaptor.control.Server.getMBeanData(Server.java:97) [:]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$1.run(HtmlAdaptorServlet.java:357) [:]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$1.run(HtmlAdaptorServlet.java:354) [:]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.getMBeanData(HtmlAdaptorServlet.java:353) [:]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.inspectMBean(HtmlAdaptorServlet.java:224) [:]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) [:]
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:81) [:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616406#616406]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
