Bug 968489
Summary: | Not informative exception with recursive stack-overflow JSF custom taglib JBoss AS 7 | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Online | Reporter: | Ihor <sp.titan> | ||||
Component: | Containers | Assignee: | Dan Mace <dmace> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | libra bugs <libra-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 2.x | CC: | jhonce | ||||
Target Milestone: | --- | Keywords: | SupportQuestion | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-09-03 20:59:39 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: | |||||||
Attachments: |
|
Description
Ihor
2013-05-29 19:08:58 UTC
JSF 2.1.7-jbossorg-2 Ihor, Unfortunately, I was unable to reproduce the issue with the information provided. Could you please provide a more complete example which could be pushed to a new jbossas-7 OpenShift application (including a complete example pom.xml, web.xml, any supplementary/custom class source, and some sort of XHTML page using the custom tag)? Thanks. now I have another issue and my application not start https://bugzilla.redhat.com/show_bug.cgi?id=968849 Also please forgive me for I used not informative comments for commits. "Could you please provide a more complete example" Please look: this code gave exception(also after this I recreate "rs" application, before I use small gears, now I created application with medium gears) rs-emetemunoy.rhcloud.com commit 196a3ba54463e5173b8aa41a0d7ece7fc35db993 Author: 452 <sp.titan> 2013-05-26 18:01:40 Committer: 452 <sp.titan> 2013-05-26 18:01:40 Parent: 20e5bb5a7fe139d434211162d81bdb6e7d2c7c3b (jrebel) Child: ce8763225945dceaf7442541fe9db8e6e4793ffe (os) Branches: test, origin/master added Like buttons =============================================================== worked because I use .java @FacesComponent commit 6c1bf64ad980169186d5afcd0290759062ac9c5e Author: 452 <sp.titan> 2013-05-29 15:04:55 Committer: 452 <sp.titan> 2013-05-29 15:04:55 Parent: 9e0a6930146736802eefec4e76d519c611e48e95 (f) Child: 5b3728bdb70e814cf8fd7581c4c5c0a631c71091 (xcz) Branches: test, origin/master component Ihor, The OpenShift team doesn't have access to the source code/Git repository of your application. If you're willing to share it in this case, could you archive those commits (or the entire repository) as attachments to this issue so I can reproduce the issue in our development environments? Thanks, Dan Created attachment 754801 [details]
ops
please remove me
The provided sample code fails to deploy on a new jbossas-7 application: 2013/09/03 16:49:37,069 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ROOT.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"ROOT.war#db.dbPU\"jboss.naming.context.java.jboss.datasources.ShopDSMissing[jboss.persistenceunit.\"ROOT.war#db.dbPU\"jboss.naming.context.java.jboss.datasources.ShopDS]"]} 2013/09/03 16:49:37,378 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment ROOT.war in 311ms 2013/09/03 16:49:37,380 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.jboss.datasources.ShopDS (missing) dependents: [service jboss.persistenceunit."ROOT.war#db.dbPU"] Going to close this one out. If there's a working example which can be used to deploy to a stock jbossas-7 application which reproduces the original issue, please provide it and re-open the bug. |