Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 7.1.1:


Last Update:

28 Sep 2015

Package Maintainer(s):

Software Author(s):

  • JBoss Developers


jboss admin java jdk


  • 1
  • 2
  • 3

7.1.1 | Updated: 28 Sep 2015



Downloads of v 7.1.1:



Software Author(s):

  • JBoss Developers

JBoss 7.1.1

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install JBoss, run the following command from the command line or from PowerShell:


To upgrade JBoss, run the following command from the command line or from PowerShell:


To uninstall JBoss, run the following command from the command line or from PowerShell:


Deployment Method:


This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade jboss-as -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade jboss-as -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install jboss-as
    name: jboss-as
    version: '7.1.1'
    state: present

See docs at

chocolatey_package 'jboss-as' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '7.1.1'

See docs at

cChocoPackageInstaller jboss-as
    Name     = "jboss-as"
    Version  = "7.1.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'jboss-as':
  ensure   => '7.1.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator gep13 on 06 Jan 2016.


JBoss is a Application Server. It is possible to run Web application ARchive (WAR) files using JBoss. JBoss 7.1.1 requires a JDK 7 in order to run.

Overriding installation parameters example:

Install JBoss to c:\jboss and set the default admin account to "bob" with a password of "mypass":

choco install jboss -params '"/Start:false /InstallationPath:"c:\jboss" /Username:bob /Password:mypass"'

function hash([string] $value){    
    $md5 = new-object -TypeName System.Security.Cryptography.MD5CryptoServiceProvider
    $utf8 = new-object -TypeName System.Text.UTF8Encoding
    $hash = [System.BitConverter]::ToString($md5.ComputeHash($utf8.GetBytes($value))).ToLower().Replace('-', '')
    echo $hash

$ErrorActionPreference = 'Stop'
$packageName = 'jboss'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = ''

$arguments = @{}

$packageParameters = $env:chocolateyPackageParameters

$installationPath = "c:\opt\jboss"
$jbossAdmin = "admin"
$jbossPass = "password"
$startService = "true"

$arguments = @{};
$packageParameters = $env:chocolateyPackageParameters;

if($packageParameters) {
	Write-Host "PackageParameters: $packageParameters"
	$match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.\$]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
	#""" fixes issues with notepad++
	$option_name = 'option'
    $value_name = 'value'

	if ($packageParameters -match $match_pattern ){
	  $results = $packageParameters | Select-String $match_pattern -AllMatches
	  $results.matches | % {
	  Throw "Package Parameters were found but were invalid (REGEX Failure)"

	if($arguments.ContainsKey("InstallationPath")) {
	  $installationPath = $arguments["InstallationPath"];
	  Write-Host "Value variable installationPath changed to $installationPath"
	} else {
	  Write-Host "Default InstallationPath will be used"

	if($arguments.ContainsKey("Username")) {
	  $jbossAdmin = $arguments["Username"];
	  Write-Host "Admin username changed to $jbossAdmin"
	} else {
	  Write-Host "Default admin username will be used"

	if($arguments.ContainsKey("Password")) {
	  $jbossPass = $arguments["Password"];
	  Write-Host "Admin password changed to $jbossPass"
	} else {
	  Write-Host "Default admin password will be used. PLEASE CHANGE THIS!!!"
	if($arguments.ContainsKey("Start")) {
	  $startService = $arguments["Start"];
	  Write-Host "Start service? $startService"
	} else {
	  Write-Host "Service will be automatically started"
} else {
	Write-Host "Package parameters will not be overwritten"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $installationPath
  url           = $url
  checksum      = '175c92545454f4e7270821f4b8326c4e'
  checksumType  = 'md5'  

Install-ChocolateyZipPackage @packageArgs

Write-Debug "Copy to $installationPath\ from $installationPath\jboss-as-7.1.1.Final"
cp -Recurse -Force $installationPath\jboss-as-7.1.1.Final\* $installationPath\jboss-as-7.1.1.Final\..\

Write-Debug "Remove $installationPath\jboss-as-7.1.1.Final"
rm -Force -Recurse $installationPath\jboss-as-7.1.1.Final

Install-ChocolateyEnvironmentVariable -variableName "JBOSS_HOME" -variableValue "$installationPath" -variableType 'Machine'
Install-ChocolateyPath "$installationPath\bin" "Machine"

Write-Verbose "Adding management user to JBoss"
$hashPass = hash ($jbossAdmin + ":ManagementRealm:" + $jbossPass)
$jbossUser = "$jbossAdmin=$hashPass" 
Write-Debug "Admin user hash: $jbossUser ==>  $installationPath\standalone\configuration\"

Add-Content $installationPath\standalone\configuration\ "`r`n$jbossUser" -Encoding utf8

Write-Verbose "Checking for JBOSS service..."
$jbossSvc = Get-Service jboss*
if($jbossSvc -eq $null){
	Write-Host "Installing JBoss Service"
	Write-Debug "Service unzipLocation $installationPath"
	$servicePackageArgs = @{
		packageName   = "$packageName-Service"
		unzipLocation = $installationPath
		url           = ""
		url64bit      = ""
		checksum    = 'acc45d49f1838183726bf616f0069cfc'
		checksumType= 'md5'
		checksum64    = '63477e8e166c9ec695ab2922ca0a31b0'
		checksumType64= 'md5'
	Install-ChocolateyZipPackage @servicePackageArgs
    cp $toolsDir\service.bat $installationPath\bin\service.bat -force
    &$installationPath\bin\service.bat install

    Set-Service jboss -StartupType Automatic
	if($startService -eq "true"){
		Write-Host "Starting Service"
		Start-Service jboss
	} else {
		Write-Host "Start service set to $startService"
Write-Host "JBoss service installed"
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'jboss'

Write-Debug "Checking for JBOSS service..."
$jbossSvc = Get-Service jboss*
if($jbossSvc -ne $null){
	Stop-Service jboss
	&sc.exe delete jboss

Uninstall-ChocolateyZipPackage $packageName ""

Install-ChocolateyEnvironmentVariable "JBOSS_HOME" $null "Machine"

$path = Get-EnvironmentVariable "PATH" "Machine"
Write-Host "Current path: $path"

$installationPath = Get-EnvironmentVariable "JBOSS_HOME" "Machine"	
$newPath = $path.Replace("$installationPath\bin;", $null)
Write-Host "New Path: $newPath"

Install-ChocolateyEnvironmentVariable "PATH" $newPath "Machine"

@echo off
REM JBoss, the OpenSource webOS
REM Distributable under LGPL license.
REM See terms of license at
REM -------------------------------------------------------------------------
REM JBoss Service Script for Windows
REM -------------------------------------------------------------------------
REM ITL Corrections
REM	Changed service name, display & description
REM Changed run.bat t0 standalone.bat
REM Changed shutdown -S to jboss-cli.bat --connect command=:shutdown

@if not "%ECHO%" == "" echo %ECHO%
@if "%OS%" == "Windows_NT" setlocal

REM during the build with ant filter.
set SVCDISP=JBoss Application Server 7.1.1
set SVCDESC=JBoss Application Server 7.1.1 GA/Platform: Windows x64

REM Suppress killing service on logoff event

set JAVAOPTS=-Xmx1024M –Xms512M –XX:MaxPermSize=512M -Xrs
REM Figure out the running mode

if /I "%1" == "install"   goto cmdInstall
if /I "%1" == "uninstall" goto cmdUninstall
if /I "%1" == "start"     goto cmdStart
if /I "%1" == "stop"      goto cmdStop
if /I "%1" == "restart"   goto cmdRestart
if /I "%1" == "signal"    goto cmdSignal
echo Usage: service install^|uninstall^|start^|stop^|restart^|signal
goto cmdEnd

REM jbosssvc retun values
REM ERR_RET_USAGE           1
REM ERR_RET_MODE            6

if errorlevel 1 echo Invalid command line parameters
if errorlevel 2 echo Failed installing %SVCDISP%
if errorlevel 4 echo Failed removing %SVCDISP%
if errorlevel 6 echo Unknown service mode for %SVCDISP%
goto cmdEnd

mkdir %JBOSS_HOME%\standalone\log
echo Service Installed > %JBOSS_HOME%\standalone\log\service.log
jbosssvc.exe -imwdc %SVCNAME% "%DIRNAME%" "%SVCDISP%" "%SVCDESC%" service.bat
if not errorlevel 0 goto errExplain
echo Service %SVCDISP% installed
goto cmdEnd

jbosssvc.exe -u %SVCNAME%
if not errorlevel 0 goto errExplain
echo Service %SVCDISP% removed
goto cmdEnd

REM Executed on service start
del %JBOSS_HOME%\standalone\log\.r.lock 2>&1 | findstr /C:"being used" > nul
if not errorlevel 1 (
  echo Could not continue. Locking file already in use.
  goto cmdEnd
echo Y > %JBOSS_HOME%\standalone\log\.r.lock
jbosssvc.exe -p 1 "Starting %SVCDISP%" >> %JBOSS_HOME%\standalone\log\service.log
call standalone.bat --server-config=standalone.xml < %JBOSS_HOME%\standalone\log\.r.lock >> %JBOSS_HOME%\standalone\log\service.log 2>&1
jbosssvc.exe -p 1 "Shutdown %SVCDISP% service" >> %JBOSS_HOME%\standalone\log\service.log
del %JBOSS_HOME%\standalone\log\.r.lock
goto cmdEnd

REM Executed on service stop

echo Y > %JBOSS_HOME%\standalone\log\.s.lock
jbosssvc.exe -p 1 "Shutting down %SVCDISP%" >> %JBOSS_HOME%\standalone\log\service.log

call jboss-cli.bat --connect command=:shutdown < %JBOSS_HOME%\standalone\log\.s.lock >> %JBOSS_HOME%\standalone\log\service.log 2>&1
jbosssvc.exe -p 1 "Shutdown %SVCDISP% service" >> %JBOSS_HOME%\standalone\log\service.log

del %JBOSS_HOME%\standalone\log\.s.lock
goto cmdEnd

REM Executed manually from command line
REM Note: We can only stop and start

echo Y > %JBOSS_HOME%\standalone\log\.s.lock
jbosssvc.exe -p 1 "Shutting down %SVCDISP%" >> %JBOSS_HOME%\standalone\log\service.log

call jboss-cli.bat --connect command=:shutdown < %JBOSS_HOME%\standalone\log\.s.lock >> %JBOSS_HOME%\standalone\log\service.log 2>&1
del %JBOSS_HOME%\standalone\log\.s.lock
REM Delete lock file

del %JBOSS_HOME%\standalone\log\.r.lock > nul 2>&1
REM Wait one second if lock file exist
jbosssvc.exe -s 1
if exist "%JBOSS_HOME%\standalone\log\.r.lock" goto waitRun

echo Y > %JBOSS_HOME%\standalone\log\.r.lock
jbosssvc.exe -p 1 "Restarting %SVCDISP%" >> %JBOSS_HOME%\standalone\log\service.log

call standalone.bat --server-config=standalone.xml < %JBOSS_HOME%\standalone\log\.r.lock >> %JBOSS_HOME%\standalone\log\service.log 2>&1
jbosssvc.exe -p 1 "Shutdown %SVCDISP% service" >> %JBOSS_HOME%\standalone\log\service.log

del %JBOSS_HOME%\standalone\log\.r.lock
goto cmdEnd

REM Send signal to the service.
REM Requires jbosssch.dll to be loaded in JVM
@if not ""%2"" == """" goto execSignal
echo Missing signal parameter.
echo Usage: service signal [0...9]
goto cmdEnd
jbosssvc.exe -k%2 %SVCNAME%
goto cmdEnd


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status

Discussion for the JBoss Package

Ground Rules:

  • This discussion is only about JBoss and the JBoss package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or JBoss, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus