April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-7210) JBossContextConfig needs to be isolated from the war class loader

by Bruno HALEBLIAN (JIRA)

[ https://issues.jboss.org/browse/JBAS-7210?page=com.atlassian.jira.plugin.... ] Bruno HALEBLIAN commented on JBAS-7210: --------------------------------------- These 2 referenced patches failed to apply "as is" on JB 5.1.0_GA sources. Line numbers and former $Id tags didn't match because the diffs comply with JB 6.X code source. So I had to adapt the diffs (change line numbers and former $Id tag comment) to have the patch successfully apply on JB 5.1.0_GA sources. That's what I call backport. I just posted this comment as a HowTo for those who, like me, wanted to hotfix the issue on old running JB5.1 systems with no time for a full JB7 migration. I fully agree with Brad Maxwell : Upgrading to JB7 is the recommended option, although driving the change from JB5 to JB7 on production systems varies from simple to head-aching (depending on what's deployed)... > JBossContextConfig needs to be isolated from the war class loader > ----------------------------------------------------------------- > > Key: JBAS-7210 > URL: https://issues.jboss.org/browse/JBAS-7210 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ClassLoading, Web (Tomcat) service > Affects Versions: JBossAS-5.1.0.GA > Reporter: Scott Stark > Assignee: Scott Stark > Fix For: 6.0.0.M2 > > Attachments: jbas-7210.war.zip > > > The parsing of the context.xml by the JBossContextConfig class is using the tccl which causes problems when the war app has tried to load its own xml parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener

by Sudip Bhowmik (JIRA)

[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ] Sudip Bhowmik commented on AS7-6819: ------------------------------------ Got same kind of error in jboss-eap-6.1: [jboss-eap-6.1] 15:01:07,911 ERROR [org.jboss.as.server] (HttpManagementService-threads - 7) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"jboss-as-helloworld-mdb.war\".component.MessageDrivenBean.CREATE is missing [jboss.ra.\"DiameterRAInDeploy-1.0\"]"]} May be I am missing something very basic. Please help. Thank you. > MBD @ResourceAdapter deployment issue with JCA inbound listener > --------------------------------------------------------------- > > Key: AS7-6819 > URL: https://issues.jboss.org/browse/AS7-6819 > Project: Application Server 7 > Issue Type: Release > Components: EJB, JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows with Jboss 7.1.3 EAP version. > Reporter: Sudip Bhowmik > Labels: jboss > Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml > > > The source set is attached here with. > ================================================= > 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t > ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame > terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener

by Sudip Bhowmik (JIRA)

[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ] Sudip Bhowmik updated AS7-6819: ------------------------------- Issue Type: Release (was: Clarification) > MBD @ResourceAdapter deployment issue with JCA inbound listener > --------------------------------------------------------------- > > Key: AS7-6819 > URL: https://issues.jboss.org/browse/AS7-6819 > Project: Application Server 7 > Issue Type: Release > Components: EJB, JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows with Jboss 7.1.3 EAP version. > Reporter: Sudip Bhowmik > Labels: jboss > Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml > > > The source set is attached here with. > ================================================= > 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t > ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame > terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6590) JSR-349 Bean Validation 1.1 API support and integration

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-6590?page=com.atlassian.jira.plugin.s... ] Stefano Maestri commented on AS7-6590: -------------------------------------- Any update on the plan for this issue? Thanks in advance. > JSR-349 Bean Validation 1.1 API support and integration > ------------------------------------------------------- > > Key: AS7-6590 > URL: https://issues.jboss.org/browse/AS7-6590 > Project: Application Server 7 > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Emmanuel Bernard > Fix For: 8.0.0.Alpha1 > > > Integrate Bean Validation 1.1 and Hibernate Validator 5 to support the BV 1.1 requirement of Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6823) Warning if no JDBC drivers can be found in domain mode

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6823?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6823: ----------------------------- Labels: Console_1.5.3 (was: ) > Warning if no JDBC drivers can be found in domain mode > ------------------------------------------------------ > > Key: AS7-6823 > URL: https://issues.jboss.org/browse/AS7-6823 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: Console_1.5.3 > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6823) Warning if no JDBC drivers can be found in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6823?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6823: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901322 > Warning if no JDBC drivers can be found in domain mode > ------------------------------------------------------ > > Key: AS7-6823 > URL: https://issues.jboss.org/browse/AS7-6823 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6823) Warning if no JDBC drivers can be found in domain mode

by Heiko Braun (JIRA)

Heiko Braun created AS7-6823: -------------------------------- Summary: Warning if no JDBC drivers can be found in domain mode Key: AS7-6823 URL: https://issues.jboss.org/browse/AS7-6823 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 8.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6759) Console should react properly to loss of connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6759?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6759: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=910718 > Console should react properly to loss of connection > --------------------------------------------------- > > Key: AS7-6759 > URL: https://issues.jboss.org/browse/AS7-6759 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > > Codesplit error handling leads to freeze -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-66) It is impossible to switch off URL caching if https protocol is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-66?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-66: ----------------------------------------------- Marek Winkler <mwinkler(a)redhat.com> made a comment on [bug 913252|https://bugzilla.redhat.com/show_bug.cgi?id=913252] Verified on 5.3.1.BRMS-P02. > It is impossible to switch off URL caching if https protocol is used > -------------------------------------------------------------------- > > Key: DROOLS-66 > URL: https://issues.jboss.org/browse/DROOLS-66 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: BRMS 5.3.1 > Reporter: Alessandro Lazarotti > Assignee: Mark Proctor > Fix For: 6.0.0.Alpha1 > > > It is impossible to switch off URL caching if https protocol is used > When used https to load resources from HTTP, a conditional mistake try to cache the content even though CACHE_DIR is null: > // class org.drools.io.impl.UrlResource > public InputStream getInputStream() throws IOException { > (...) > if (lastMod > 0 && lastMod > lastRead) { > if (CACHE_DIR != null && url.getProtocol().equals("http") || url.getProtocol().equals("https")) { > //lets grab a copy and cache it in case we need it in future... > cacheStream(); > } > } > (...) > } > IF only "https" was evaluated as true - ((false && false) || true) - so the exit will be true, which should be not the expected behaviour > That code should be: > if (CACHE_DIR != null && (url.getProtocol().equals("http") || url.getProtocol().equals("https"))) { > //lets grab a copy and cache it in case we need it in future... > cacheStream(); > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-66) It is impossible to switch off URL caching if https protocol is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-66?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-66: ----------------------------------------------- Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 913252|https://bugzilla.redhat.com/show_bug.cgi?id=913252] from ON_QA to VERIFIED > It is impossible to switch off URL caching if https protocol is used > -------------------------------------------------------------------- > > Key: DROOLS-66 > URL: https://issues.jboss.org/browse/DROOLS-66 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: BRMS 5.3.1 > Reporter: Alessandro Lazarotti > Assignee: Mark Proctor > Fix For: 6.0.0.Alpha1 > > > It is impossible to switch off URL caching if https protocol is used > When used https to load resources from HTTP, a conditional mistake try to cache the content even though CACHE_DIR is null: > // class org.drools.io.impl.UrlResource > public InputStream getInputStream() throws IOException { > (...) > if (lastMod > 0 && lastMod > lastRead) { > if (CACHE_DIR != null && url.getProtocol().equals("http") || url.getProtocol().equals("https")) { > //lets grab a copy and cache it in case we need it in future... > cacheStream(); > } > } > (...) > } > IF only "https" was evaluated as true - ((false && false) || true) - so the exit will be true, which should be not the expected behaviour > That code should be: > if (CACHE_DIR != null && (url.getProtocol().equals("http") || url.getProtocol().equals("https"))) { > //lets grab a copy and cache it in case we need it in future... > cacheStream(); > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013