February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3278) rollout plan tab-completion

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3278: -------------------------------------- Summary: rollout plan tab-completion Key: AS7-3278 URL: https://issues.jboss.org/browse/AS7-3278 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final Tab-completion isn't yet supported for rollout plans. -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-3425) Allow setting of security properties via -S option on the command line

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-3425: ---------------------------------- Summary: Allow setting of security properties via -S option on the command line Key: AS7-3425 URL: https://issues.jboss.org/browse/AS7-3425 Project: Application Server 7 Issue Type: Feature Request Components: Security, Server Affects Versions: 7.1.0.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 7.1.0.Final It should be possible for users to set Security Properties via command line option -S http://docs.oracle.com/javase/6/docs/api/java/security/Security.html#setP... Previously it was part of Security subsystem configuration, but Jason thinks it is better to place it as a cmd line option. -- 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM

by Galder Zamarreno (JIRA)

EJB timer service should use a thread pool to avoid OOM ------------------------------------------------------- Key: EJBTHREE-1330 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1330 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor The default EJB timer service used by the EJB3 layer is based on org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates to the standard org.jboss.ejb.txtimer.EJBTimerService. For EJB3 beans using the EJB timer service the thread local pool should not be used. Since the current EJB timer service creates a new thread for each timer being created, the thread local pool will create a matching instance of the bean for that thread. Thus the number of active instances in total can effectively grow unchecked and thus an OOM will occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
8
0 / 0

[JBoss JIRA] (AS7-3583) CLI: data-source add command argument jndi-name not mandatory

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3583: ------------------------------------- Summary: CLI: data-source add command argument jndi-name not mandatory Key: AS7-3583 URL: https://issues.jboss.org/browse/AS7-3583 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Alexey Loubyansky The data-source add command argument "jndi-name" is not mandatory. The CLI allows exection of data-source add command without specifying jndi name. Enabling such data-source fails. [standalone@localhost:9999 /] data-source add --name=TestDS2 --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 [standalone@localhost:9999 /] data-source enable --name=TestDS2 JBAS010436: Failed to create DataSource instance for [{ "operation" => "enable", "address" => [ ("subsystem" => "datasources"), ("data-source" => "TestDS2") ], "persistent" => undefined }] reason: IJ010068: Missing required attribute jndi-name in org.jboss.as.connector.subsystems.datasources.ModifiableDataSource -- 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3355) Problems when writing rhs in Rule API

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3355: -------------------------------------- Summary: Problems when writing rhs in Rule API Key: JBRULES-3355 URL: https://issues.jboss.org/browse/JBRULES-3355 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: There are several problems when writing rhs of a rule in Rule API: - if you omit rhs() you 'nullend' on the end of the rule which results in compile error - if you put comment in rhs() like rhs("//consequences") you get '//consequencesend' which result in compile error as well I think there should be line delimiter behind rhs and that if rhs is omitted it should result in empty string rather than "null". KnowledgeDescr descr = DescrFactory.newPackage().name("org.sample") .newRule().name("results in consequencesend") .rhs("//consequences") .end() .newRule().name("results in nullend") .lhs() .pattern("String").end() .end() .end() .getDescr(); -- 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

13 years, 10 months

4
20
0 / 0

[JBoss JIRA] (AS7-3580) NameNotFoundException in async web service method.

by Jeremy Whiting (JIRA)

[ https://issues.jboss.org/browse/AS7-3580?page=com.atlassian.jira.plugin.s... ] Jeremy Whiting deleted AS7-3580: -------------------------------- > NameNotFoundException in async web service method. > -------------------------------------------------- > > Key: AS7-3580 > URL: https://issues.jboss.org/browse/AS7-3580 > Project: Application Server 7 > Issue Type: Bug > Environment: Any java system. > Reporter: Jeremy Whiting > Assignee: Alessio Soldano > Priority: Critical > > When an asynchronous Web Service method annotated with @OneWay is invoked by an MDB in the same VM a Na -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3580) NameNotFoundException in async web service method.

by Jeremy Whiting (JIRA)

Jeremy Whiting created AS7-3580: ----------------------------------- Summary: NameNotFoundException in async web service method. Key: AS7-3580 URL: https://issues.jboss.org/browse/AS7-3580 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1b Environment: Any java system. Reporter: Jeremy Whiting Assignee: Alessio Soldano Priority: Critical When an asynchronous Web Service method annotated with @OneWay is invoked by an MDB in the same VM a Na -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3579) Upgrade to JBossWS 4.0.1.GA and Apache CXF 2.4.6

by Alessio Soldano (JIRA)

Alessio Soldano created AS7-3579: ------------------------------------ Summary: Upgrade to JBossWS 4.0.1.GA and Apache CXF 2.4.6 Key: AS7-3579 URL: https://issues.jboss.org/browse/AS7-3579 Project: Application Server 7 Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.1.0.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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3379) ResourceAdapterActivatorService never gets stopped

by Andy Taylor (JIRA)

Andy Taylor created AS7-3379: -------------------------------- Summary: ResourceAdapterActivatorService never gets stopped Key: AS7-3379 URL: https://issues.jboss.org/browse/AS7-3379 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.CR1b Reporter: Andy Taylor Assignee: Andy Taylor Priority: Critical Fix For: 7.1.0.Final This is because the stop method is over ridden but doesn't do anything meaning that resource adapters aren't closed properly leaving resources running. -- 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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (AS7-3228) Add support for Apache Sling on OSGi subsystem

by Thomas Diesler (Created) (JIRA)

Add support for Apache Sling on OSGi subsystem ---------------------------------------------- Key: AS7-3228 URL: https://issues.jboss.org/browse/AS7-3228 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

13 years, 10 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012