Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899221 (JBEWS-177)

Summary:	EWS - jsvc support
Product:	[JBoss] JBoss Enterprise Web Server 1	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	unspecified	Assignee:	Permaine Cheung <pcheung>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	EWS 1.0.1, EWS 1.0.0.GA	CC:	mturk, pcheung, rebecca.jboss
Target Milestone:	---
Target Release:	EWS 1.0.2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEWS-177
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	all
Last Closed:	2011-03-14 10:59:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	899283

Description Aleksandar Kostadinov 2010-02-10 15:15:18 UTC

Date of First Response: 2010-02-10 10:25:43
project_key: JBEWS

I would like to ask at what level is jsvc supported in EWS. Currently we are shipping source code. To what extend is this supported. Why don't we compile the utility if we are going to support it? Or should that be removed from the distribution or just marked unsupported? 

In my opinion leaving in source will be harmful for both customers and us. Not all machines have a dev environment setup so it it will be extra burden for clients and QE to run and test. Setting up the build process to compile that should be much more straightforward. Or removing that will also be fine in my opinion if jsvc is not giving some great advantage I fail to see.

Thanks

Comment 1 Rajesh Rajasekaran 2010-02-10 15:25:43 UTC

Aleks, i opened JBPAPP-3609 for including a compiled binary. We might not have time to do it for 1.0.1. Moving to 1.0.2

Comment 2 Aleksandar Kostadinov 2010-02-10 15:37:45 UTC

Ah, I tried to find that one but somehow my JIRA search was not successful so filed a new one.

I'm not sure how would it be best to track this one though because it also has documentation implications. If we include a compiled in version, then the docs should state that. On the other hand, if one needs to compile, instructions are not clear because there are development packages needed to be installed and for example solaris' tar doesn't take xvfz argument (z being a problem). One needs to gunzip and then tar xvf.
Or should that be only incuded in the release notes.

In any case though we will need to handle the situation in this release somehow so probably we can keep my JIRA issue for this release and yours for the next?

Comment 3 Aleksandar Kostadinov 2010-02-10 15:38:01 UTC

Link: Added: This issue related JBPAPP-3609

Comment 4 Rajesh Rajasekaran 2010-02-10 15:50:33 UTC

Ok. I didn't think about the docs issue. Reopening for 1.0.1
I am not sure how the docs are maintained. The upstream docs for most part contain instructions for the unix(linux) platforms.
For cases where the instructions differ for solaris or windows we need to include in our online documentation.

Comment 5 Permaine Cheung 2010-02-11 14:50:53 UTC

Assigning to Laura as this is a docs issue for the current release.

Comment 6 Mladen Turk 2010-02-11 15:13:37 UTC

This is target for 1.0.2

Comment 7 Laura Bailey 2010-02-12 01:32:53 UTC

Aleksandar, can you provide me with more details about the compilation process, or link me to upstream documentation with more details? Otherwise there is little to report in the release notes other than that jsvc ships uncompiled. Thanks!

Comment 8 Aleksandar Kostadinov 2010-02-12 06:16:31 UTC

There is INSTALL.txt in share/tomcat[56]/bin/jsvc.tar.gz
But it talks nothing about what tools you need have installed before that works.
I can only say that you need some subset of the tools needed to build EWS.

Comment 9 Laura Bailey 2010-02-14 23:06:45 UTC

Mladen, can you give me any further information?

Comment 10 Mladen Turk 2010-02-15 08:08:13 UTC

I have enabled jakarta-commons-daemon native binary (jsvc) build for non-windows platforms.
We can include it in 1.0.1 or postpone for 1.0.2
I suppose we would need some sort of wrapper scripts for tomcat5 and tomcat6
Since this requires much more work then actual compiling, if we choose to ship the
jsvc binary with 1.0.1 we should note that we will provide wrapper scripts with 1.0.2

Regarding tools needed for building jsvc on Solaris there is only two requirements
SunStudio 12 and Java1.4+ SDK (JRE won't be enough).
For Linux one will also need Java SDK and gcc toolchain.
Windows already has jakarta-commons-daemon binaries as part of tomcat distribution
and those are named tomcat5.exe, tomcat5w.exe, tomcat6.exe and tomcat6w.exe

Comment 12 Mladen Turk 2010-03-01 17:51:59 UTC

Re enabled in 1.0.2-dev

Comment 13 Anne-Louise Tangring 2010-10-28 19:30:36 UTC

Accepted for 1.0.2

Comment 14 Mladen Turk 2010-11-17 11:57:17 UTC

We would need to upgrade to commons-daemon 1.0.4
It contains full support for running Tomcat and JBOSS AS

Comment 15 Mladen Turk 2010-11-17 12:00:57 UTC

Link: Added: This issue is a dependency of JBPAPP-4709

Comment 16 Mladen Turk 2010-11-17 12:13:51 UTC

BTW, we could directly reuse official binaries (I made them BTW)
http://www.apache.org/dist/commons/daemon/binaries/1.0.4/

Comment 17 Mladen Turk 2011-01-10 11:57:37 UTC

I suggest we use latest stable version:
http://www.apache.org/dist/commons/daemon/binaries/1.0.5/

This would mean to update the rpm (probably inside RHEL-5-EP-5 branch)
Also this component would be build as one-off for both Tomcat5 and Tomcat6
resolving duplicates on Solaris and WIndows, as well on RHEL,

Comment 18 Permaine Cheung 2011-01-10 13:52:22 UTC

Link: Added: This issue related JBPAPP-5465

Comment 19 Rajesh Rajasekaran 2011-02-21 21:15:06 UTC

Permaine, based on Mladen's last comments I am assigning this to you. It is important to include this JIRA for the 1.0.2 release.

Comment 20 Permaine Cheung 2011-02-22 13:40:03 UTC

daemon already upgraded to 1.0.5 in JBPAPP-5465.

Comment 21 Permaine Cheung 2011-03-01 15:19:15 UTC

Assigning back to Mladen to see if he needs any additional work to get this in EWS 1.0.2.

Mladen, please mark this as resolved if you're already done. Thanks!

Comment 22 Aleksandar Kostadinov 2011-03-14 10:59:25 UTC

jsvc is now found in the EWS bundles. Closing this issue although we see some problems as reported by JBPAPP-6079

Comment 23 Aleksandar Kostadinov 2011-05-03 19:58:26 UTC

Link: Added: This issue is related to JBPAPP-6079