June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-116) Update versions of rmi spec and jaxrs api spec in the BOMs

by Paul Gier (JIRA)

Paul Gier created JBEE-116: ------------------------------ Summary: Update versions of rmi spec and jaxrs api spec in the BOMs Key: JBEE-116 URL: https://issues.jboss.org/browse/JBEE-116 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: general Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 3.0.1.Final Update the versions of the rmi spec jar and the jaxrs spec jar listed in the EE BOM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (JBEE-115) Add XML schema and clean up license info for servlet 3.0 spec api jar

by Thomas Diesler (JIRA)

Thomas Diesler created JBEE-115: ----------------------------------- Summary: Add XML schema and clean up license info for servlet 3.0 spec api jar Key: JBEE-115 URL: https://issues.jboss.org/browse/JBEE-115 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: jboss-servlet-api Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 5 Spec APIs - Maint The servlet 2.5 spec api is missing XML schema information. Also, the license information should be reviewed and corrected if there are any problems. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] (JBRULES-3561) Add support for ad-hoc queries

by Jaroslav Pullmann (JIRA)

Jaroslav Pullmann created JBRULES-3561: ------------------------------------------ Summary: Add support for ad-hoc queries Key: JBRULES-3561 URL: https://issues.jboss.org/browse/JBRULES-3561 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (expert), drools-core (expert) Reporter: Jaroslav Pullmann Assignee: Mark Proctor Priority: Optional Please consider extending the WM interface by a method that allows for one-shot queries. It accepts a concrete query pattern (LHS expression) instead of the name of a predefined query. Sample signature: QueryResults WorkingMemory#executeQuery(String queryPattern) throws IllegalArgumentException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (AS7-4210) Remove dependency on framework implementation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4210: ----------------------------------- Summary: Remove dependency on framework implementation Key: AS7-4210 URL: https://issues.jboss.org/browse/AS7-4210 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Currently we include org.osgi.util.tracker org.osgi.util.xml with jbosgi-framework-core. Every component that wants to use those (public) packages needs to define a e dependency on the framework impl. These packages should be externalized to a public API module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (AS7-4772) Maintain iteration order for entity bean finders

by Mattias Nilsson (JIRA)

Mattias Nilsson created AS7-4772: ------------------------------------ Summary: Maintain iteration order for entity bean finders Key: AS7-4772 URL: https://issues.jboss.org/browse/AS7-4772 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.1.Final Reporter: Mattias Nilsson Assignee: jaikiran pai In previous JBoss AS versions (at least in JBoss AS 4.x) if a finder method in an EJB 2.x entity bean returned a collection or enumeration of primary keys in a specific order, the client would receive a collection or enumeration of entities with the same iteration order. In JBoss AS 7, the entity bean home interceptor uses a HashSet when producing the collection of entities. This means iteration order is lost and clients receive the entities in random order. As a convenience and as a backward compatibility for users migrating from previous JBoss versions, could you consider replacing java.util.HashSet with java.util.LinkedHashSet in org.jboss.as.ejb3.component.entity.interceptors.EntityBeanHomeFinderInterceptorFactory? I would be happy to provide a test case and a pull request with this change. Regards, Mattias -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
8
0 / 0

[JBoss JIRA] (AS7-4971) Upgrade JBoss Logging for OSGi

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created AS7-4971: --------------------------------------- Summary: Upgrade JBoss Logging for OSGi Key: AS7-4971 URL: https://issues.jboss.org/browse/AS7-4971 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Affects Versions: 7.1.2.Final (EAP) Reporter: Juergen Zimmermann Assignee: Thomas Diesler jbosgi-repository-parent-1.2.0.Final.pom and jbosgi-vfs-parent-1.1.0.Final.pom are using old versions of JBoss Logging: * version.jboss.logging: 3.1.0.GA -> 3.1.1.GA * version.jboss.logging.processor: 1.0.0.Final -> 1.0.2.Final * version.jboss.logmanager: 1.2.2.GA -> 1.3.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1752) Starting multiple standalone servers from the same install is not clean

by Brian Stansberry (JIRA)

Starting multiple standalone servers from the same install is not clean ----------------------------------------------------------------------- Key: AS7-1752 URL: https://issues.jboss.org/browse/AS7-1752 Project: Application Server 7 Issue Type: Task Components: Server Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.1.0.CR1 It should be easy to copy the standalone dir to another dir (say, "serverB" in the same level in the FS tree) and launch a second server using ./standalone.sh -Djboss.server.base.dir=serverB It somewhat works, but things that aren't as smooth as they should be: a) The resolution of jboss.server.base.dir isn't very smart. For example, to do the common thing and launch the script from within the bin dir you have to either use an absolute path to instance1/2 or do something kludgey like: ./standalone.sh -Djboss.server.base.dir=../serverB If the path is relative and resolving it doesn't result in a file that exists, an attempt should be made to resolve against jboss.home.dir. 2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] (AS7-4888) Configuration org.jboss.as.test.integration.osgi.xservice.bundle.ConfiguredService deleted

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4888: ----------------------------------- Summary: Configuration org.jboss.as.test.integration.osgi.xservice.bundle.ConfiguredService deleted Key: AS7-4888 URL: https://issues.jboss.org/browse/AS7-4888 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Reporter: Thomas Diesler Assignee: Thomas Diesler {code} 09:38:24,811 INFO [org.jboss.osgi.framework] (pool-3-thread-1) JBOSGI011002: Bundle started: example-configadmin:0.0.0 09:38:25,140 ERROR [org.jboss.as.configadmin] (pool-1-thread-1) JBAS016201: Error in configuration listener: org.jboss.as.osgi.configadmin.DomainModelPersistenceManager@34f9cff1: java.lang.RuntimeException: java.lang.IllegalStateException: Configuration org.jboss.as.test.integration.osgi.xservice.bundle.ConfiguredService deleted at org.jboss.as.osgi.configadmin.DomainModelPersistenceManager.configurationModified(DomainModelPersistenceManager.java:159) at org.jboss.as.configadmin.service.ConfigAdminServiceImpl$ConfigurationModifiedService.run(ConfigAdminServiceImpl.java:256) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] Caused by: java.lang.IllegalStateException: Configuration org.jboss.as.test.integration.osgi.xservice.bundle.ConfiguredService deleted at org.apache.felix.cm.impl.ConfigurationAdapter.checkDeleted(ConfigurationAdapter.java:173) at org.apache.felix.cm.impl.ConfigurationAdapter.update(ConfigurationAdapter.java:109) at org.jboss.as.osgi.configadmin.DomainModelPersistenceManager.configurationModified(DomainModelPersistenceManager.java:156) ... 4 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
7
0 / 0

[JBoss JIRA] (AS7-5022) Server sometimes crashes during reload operation

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-5022?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-5022: -------------------------------- Summary: Server sometimes crashes during reload operation (was: CLONE - Server sometimes crashes during reload operation) > Server sometimes crashes during reload operation > ------------------------------------------------ > > Key: AS7-5022 > URL: https://issues.jboss.org/browse/AS7-5022 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jan Martiska > Assignee: Thomas Diesler > Priority: Critical > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > After some number of server reloads, next reload fails.. the number seems random, for me it is between 6 and 150. > this error message pops up during boot: > {noformat} > 15:21:05,036 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 53) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered > {noformat} > This shell script can be used for reproduction: > {noformat} > #!/bin/sh > $JBOSS_HOME/bin/standalone.sh > /dev/null & > sleep 10 > for i in `seq 1 150`; do > echo $i > $JBOSS_HOME/bin/jboss-cli.sh -c --command=:reload > sleep 4 > tail --lines=50 $JBOSS_HOME/standalone/log/server.log | grep ERROR > done > {noformat} > Testing environment> RHEL 5 or 6. This happens both when reloading using jboss-cli.sh and jboss-as-controller-client. It seems it has never happened to me when EAP was running in IPv6 mode (java.net.preferIPv4Stack=false), only IPv4. Affects all standalone profiles. It randomly breaks my admin console testsuite, which uses server reloads quite a lot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-1556) Initial support for OSGi webapps in JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-1556?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1556: -------------------------------- Summary: Initial support for OSGi webapps in JBossWeb (was: Initial support OSGi webapps in JBossWeb) Git Pull Request: https://github.com/jbossas/jboss-as/pull/2564 (was: https://github.com/jbossas/jboss-as/pull/2564) Forum Reference: http://community.jboss.org/message/17257#17257 (was: http://community.jboss.org/message/17257#17257) > Initial support for OSGi webapps in JBossWeb > -------------------------------------------- > > Key: AS7-1556 > URL: https://issues.jboss.org/browse/AS7-1556 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Priority: Critical > Fix For: 7.2.0.Alpha1 > > Attachments: webapp-1.0.pdf > > > OSGi webapps are currently deployed onto jboss-osgi-webapp, which contains an embedded PAX-Web WAR extender that in turn delegates to the PAX-Web provided WebContainer based on Jetty. > In the future, OSGi webapps should be handled by JBossWeb and be deployed onto the JBoss embedded Tomcat instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

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 June 2012