Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1156397 - File System Deployments are not enabled in standalone/clustered.xml by default
File System Deployments are not enabled in standalone/clustered.xml by default
Status: CLOSED CURRENTRELEASE
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server (Show other bugs)
6.4.0
Unspecified Unspecified
unspecified Severity high
: ER8
: 6.4.0
Assigned To: Galder Zamarreño
Martin Gencur
:
Depends On:
Blocks: jdg64-GA-Blockers
  Show dependency tree / graph
 
Reported: 2014-10-24 07:35 EDT by Vitalii Chepeliuk
Modified: 2015-02-22 18:59 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
Previously in Red Hat JBoss Data Grid, the server did not contain the deployment scanner which is responsible for handling deployments. As a result, it was not possible to deploy custom user filters, converters and marshallers for enhanced remote listeners by copying jar files with these pieces into the <filename>standalone/deployments<filename> folder in the server. This issue is now resolved in JBoss Data Grid 6.4 and the server now contains the deployment scanner and works as expected.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker ISPN-4884 Critical Resolved Deployment scanner should be enabled to allow filter/converter jar deployment 2016-01-22 02:48 EST

  None (edit)
Description Vitalii Chepeliuk 2014-10-24 07:35:36 EDT 
Description of problem:
When we want to copy JARS and deploy it on JDG server in standalone/clustered.xml is no deployment-scanner element defined. It should be added when server is built

Version-Release number of selected component (if applicable): 6.4.0.ER2

Steps to Reproduce:
1. cp filter-converter.jar jboss-datagrid-6.4.0-server/standalone/deployments/
2. look at console output of server 
3. check if there is no output from deployment scanner

Actual results: not output from deployment scanner, because it is not enabled


Expected results: we should see following output in console log
JBAS015012: Started FileSystemDeploymentService for directory /home/weblogic/jboss-datagrid-6.4.0-server/standalone/deployments
JBAS015876: Starting deployment of "filter-converter.jar" (runtime-name: "filter-converter.jar")
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.