Bug 1442140 - c3p0 centos update breaks spacewalk-postrgresql operation
Summary: c3p0 centos update breaks spacewalk-postrgresql operation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
: 1443398 (view as bug list)
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2017-04-13 15:58 UTC by Leonid Kanter
Modified: 2019-07-04 12:30 UTC (History)
11 users (show)

Fixed In Version: spacewalk-java-2.7.53-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-27 07:02:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Leonid Kanter 2017-04-13 15:58:18 UTC
Description of problem:

Path to c3p0.jar was changed in latest c3p0 rpm update, as a result tomcat application is unable to start. And it could be impossible to install new spacewalk instrance.

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

spacewalk-postgresql-2.6.1-1.el7.noarch

How reproducible:

always

Steps to Reproduce:
1. On running instance of spacewalk, run yum update c3p0

Actual results:

web interface will be broken. in tomcat log you will see:

java.io.IOException: Failed to access resource /WEB-INF/lib/c3p0.jar

Expected results:

Spacewalk web should continue to operate properly

Additional info:

/var/lib/tomcat/webapps/rhn/WEB-INF/lib/c3p0.jar points to /usr/share/java/c3p0.jar. While the new path is /usr/share/java/c3p0/c3p0.jar

Comment 1 Leonid Kanter 2017-04-13 16:16:44 UTC
Additional info: spacewalk is incompatible with c3p0-0.9.2.1-5.el7.noarch.rpm from centos updates. I had to roll it back to c3p0-0.9.1.2-2.jpp5.noarch

Comment 2 Raimund Hook 2017-04-20 14:32:26 UTC
Thanks Leonid, I had the same problem after an update to 2.6.

Rolling back c3p0 did the trick...

Comment 3 Ronny Bremer 2017-04-23 09:33:33 UTC
I have been affected by the same issue. Rolling back c3p0 also worked for me.

Comment 4 sjansen 2017-05-02 15:47:42 UTC
Same issue on my installation. Had do downgrade c3p0 to get Spacewalk working again.

Comment 6 sheepdestroyer 2017-08-24 09:19:25 UTC
Can confirm the bug on Centos 7.3

Comment 7 Dave Brennan 2017-09-04 10:13:19 UTC
Confirm Spacewalk crashed after c3p0 update

Workaround:

yum downgrade c3p0
yum versionlock c3p0

Comment 8 Michael Mráka 2017-09-27 07:02:39 UTC
Already fixed in spacewalk master, most likely by
commit da7ff4efedf2f243aefd34921a405eff72eedc52
    no more special jar handling is needed

Comment 9 Eric Herget 2017-09-28 18:12:08 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.

Comment 10 Michael Mráka 2019-07-04 12:30:01 UTC
*** Bug 1443398 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.