March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6449) jboss-cli deploy --force fails for OSGi bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6449?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-6449 at 3/18/13 10:46 AM: --------------------------------------------------------------- Cannot reproduce {code} [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar 'org.apache.felix.eventadmin.jar' already exists in the deployment repository (use --force to replace the existing content in the repository). [standalone@localhost:9999 /] deploy --force ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar [standalone@localhost:9999 /] {code} was (Author: thomas.diesler): Cannot reproduce {code} [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar 'org.apache.felix.eventadmin.jar' already exists in the deployment repository (use --force to replace the existing content in the repository). [standalone@localhost:9999 /] deploy --force ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar {code} > jboss-cli deploy --force fails for OSGi bundles > ----------------------------------------------- > > Key: AS7-6449 > URL: https://issues.jboss.org/browse/AS7-6449 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, OSGi > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Thomas Diesler > > If you try to deploy already-deployed .jar from cli, it says "already exists in the deployment repository (use --force to replace the existing content in the repository)". However, using --force errors with "service already registered" if it is an OSGi bundle. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6449) jboss-cli deploy --force fails for OSGi bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6449?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved AS7-6449. --------------------------------- Fix Version/s: (was: 8.0.0.Alpha1) Resolution: Cannot Reproduce Bug Cannot reproduce {code} [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar [standalone@localhost:9999 /] deploy ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar 'org.apache.felix.eventadmin.jar' already exists in the deployment repository (use --force to replace the existing content in the repository). [standalone@localhost:9999 /] deploy --force ~/git/jbosgi/distribution/installer/target/deploy-artifacts/lib/org.apache.felix.eventadmin.jar {code} > jboss-cli deploy --force fails for OSGi bundles > ----------------------------------------------- > > Key: AS7-6449 > URL: https://issues.jboss.org/browse/AS7-6449 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, OSGi > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Thomas Diesler > > If you try to deploy already-deployed .jar from cli, it says "already exists in the deployment repository (use --force to replace the existing content in the repository)". However, using --force errors with "service already registered" if it is an OSGi bundle. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1010) Addition of the 4470 FATAL error for the DB2 ExceptionSorter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1010?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1010: ----------------------------------- Assignee: Jesper Pedersen (was: Johnathon Lee) Fix Version/s: 1.0.16.Final 1.1.0.Beta5 Affects Version/s: (was: 1.0.16.Final) I need a patch for this > Addition of the 4470 FATAL error for the DB2 ExceptionSorter > ------------------------------------------------------------ > > Key: JBJCA-1010 > URL: https://issues.jboss.org/browse/JBJCA-1010 > Project: IronJacamar > Issue Type: Feature Request > Components: JDBC > Reporter: Johnathon Lee > Assignee: Jesper Pedersen > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > > DB2 has a FATAL SQL error code of 4470 that needs to be handled by the DB2ExceptionSorter -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1010) Addition of the 4470 FATAL error for the DB2 ExceptionSorter

by Johnathon Lee (JIRA)

Johnathon Lee created JBJCA-1010: ------------------------------------ Summary: Addition of the 4470 FATAL error for the DB2 ExceptionSorter Key: JBJCA-1010 URL: https://issues.jboss.org/browse/JBJCA-1010 Project: IronJacamar Issue Type: Feature Request Components: JDBC Affects Versions: 1.0.16.Final Reporter: Johnathon Lee Assignee: Johnathon Lee DB2 has a FATAL SQL error code of 4470 that needs to be handled by the DB2ExceptionSorter -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-92) Add support for Equinox ExtendedLogService

by Philippe Marschall (JIRA)

Philippe Marschall created JBLOGGING-92: ------------------------------------------- Summary: Add support for Equinox ExtendedLogService Key: JBLOGGING-92 URL: https://issues.jboss.org/browse/JBLOGGING-92 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-logging-spi Reporter: Philippe Marschall Assignee: David Lloyd We are running some JBoss libraries that use jboss-logging inside Eclipse RCP. We'd like to centralise all our logging. Unfortunately OSGi LogService does not support named loggers, for now they're only available through the Equinox ExtendedLogService. I'll attach a pull request. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5959) Get rid of CNFs and NCDFs from clustering TS runs

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5959?page=com.atlassian.jira.plugin.s... ] Radoslav Husar resolved AS7-5959. --------------------------------- Resolution: Done Completely done as part of AS7-4460. [rhusar@x220 as]$ grep NoClassDefFoundError -R testsuite/integration/clust/ | wc -l 0 > Get rid of CNFs and NCDFs from clustering TS runs > ------------------------------------------------- > > Key: AS7-5959 > URL: https://issues.jboss.org/browse/AS7-5959 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > [0m[0m12:53:07,775 INFO [org.jboss.weld.ClassLoading] (MSC service thread 1-3) WELD-000119 Not generating any bean definitions from org.jboss.as.test.clustering.ClusterHttpClientUtil because of underlying class loading error > [0m[0m12:53:07,776 INFO [org.jboss.weld.ClassLoading] (MSC service thread 1-3) catching: org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.jboss.as.test.clustering.ClusterHttpClientUtil > at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:167) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.bootstrap.BeanDeployer.loadWeldClass(BeanDeployer.java:116) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:79) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:135) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31] > Caused by: java.lang.NoClassDefFoundError: org/apache/http/client/methods/HttpUriRequest > at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.6.0_31] > at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [rt.jar:1.6.0_31] > at java.lang.Class.getDeclaredFields(Class.java:1743) [rt.jar:1.6.0_31] > at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:105) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:102) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAndWrap(SecureReflectionAccess.java:63) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.util.reflection.SecureReflections.getDeclaredFields(SecureReflections.java:102) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.java:155) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:121) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:59) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:50) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) > at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) > at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) > at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) > at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:163) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] > ... 12 more > Caused by: java.lang.ClassNotFoundException: org.apache.http.client.methods.HttpUriRequest from [Module "deployment.stateful.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] > ... 30 more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1009) delistResource never called

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1009?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1009: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=922793 > delistResource never called > --------------------------- > > Key: JBJCA-1009 > URL: https://issues.jboss.org/browse/JBJCA-1009 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1006) isSameRmOverride doesn't take effect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1006?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1006: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=922174, https://bugzilla.redhat.com/show_bug.cgi?id=922793 (was: https://bugzilla.redhat.com/show_bug.cgi?id=922174) > isSameRmOverride doesn't take effect > ------------------------------------ > > Key: JBJCA-1006 > URL: https://issues.jboss.org/browse/JBJCA-1006 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1005) SemaphoreArrayListManagedConnectionPool should FIFO

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1005?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1005: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=922793 > SemaphoreArrayListManagedConnectionPool should FIFO > --------------------------------------------------- > > Key: JBJCA-1005 > URL: https://issues.jboss.org/browse/JBJCA-1005 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > > Currently behaving in FILO manner -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1004) Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1004?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBJCA-1004: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=922793 > Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1004 > URL: https://issues.jboss.org/browse/JBJCA-1004 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > Attachments: JBJCA-1004-tests.patch, JBJCA-1004.patch > > > An issue cloned from JBPAPP6-1323 for the upstream. > DataSource configured with security-domain using org.picketbox.datasource.security.CallerIdentityLoginModule is able to create correct connection > when one of ds.getConection(username, password) is set to null. > Null parameter is substituted using value of corresponding field from the security-domain. > The datasource is defined using <allow-multiple-users/>. > See test org.jboss.as.test.integration.jca.security.DsWithCallerIdentityLoginModuleTestCase at https://github.com/pskopek/jboss-as/tree/JBPAPP-9583. -- 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, 2 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 March 2013