January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-733) ShrinkWrap 1.0.0.CR2

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-733: ------------------------------------- Summary: ShrinkWrap 1.0.0.CR2 Key: JBJCA-733 URL: https://issues.jboss.org/browse/JBJCA-733 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha5 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-734) ShrinkWrap Descriptors 1.2.0.Alpha2

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-734: ------------------------------------- Summary: ShrinkWrap Descriptors 1.2.0.Alpha2 Key: JBJCA-734 URL: https://issues.jboss.org/browse/JBJCA-734 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha5 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-732) Arquillian 1.0.0.CR7

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-732: ------------------------------------- Summary: Arquillian 1.0.0.CR7 Key: JBJCA-732 URL: https://issues.jboss.org/browse/JBJCA-732 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha5 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-714) JBossTS 4.16.0.Beta1

by Jesper Pedersen (Created) (JIRA)

JBossTS 4.16.0.Beta1 -------------------- Key: JBJCA-714 URL: https://issues.jboss.org/browse/JBJCA-714 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha5 -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3354) HornetQ backup server won't start when live server is killed

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/AS7-3354?page=com.atlassian.jira.plugin.s... ] Miroslav Novak deleted AS7-3354: -------------------------------- > HornetQ backup server won't start when live server is killed > ------------------------------------------------------------ > > Key: AS7-3354 > URL: https://issues.jboss.org/browse/AS7-3354 > Project: Application Server 7 > Issue Type: Bug > Reporter: Miroslav Novak > Assignee: Clebert Suconic > > Test scenario: > 1. Start two AS7/EAP6 servers in (hornetq) cluster with HornetQ in colocated topology - server A contains backup for server B and server B contains backup for server A > 2. Kill AS7/EAP6 server A using "kill -9 ..." > I see following to happen after step 2.: > a) HornetQ backup server on server B won't start/come live. > b) Server B is not able to update its cluster view. > a) and b) -> c) JMS clients on server A are not able to failover to bakcup > I've attached reproducer with configuration - reproducer.zip. (logging is set to DEBUG level for "org.hornetq") > How to use the reproducer (there are necessary two machines): > 1. Download and unzip attached reproducer.zip > 2. prepare servers A and B using - "sh prepare.sh" > 3. start server A - "sh start-server1.sh serverA_hostname" - on server serverA_hostname > 4. start server B - "sh start-server2.sh serverB_hostname" - on server serverB_hostname > 5. Kill server A using "kill -9 ..." > I've attached JMS client to reproducer (it's using HornetQ core api to create connection factory a queue "testQueue"): > 1. Start producer - "sh start-producer.sh server_hostname" > 2. Start consumer - "sh start-consumer.sh server_hostname" > This could be configuration issue. For this reason I set major priority. Please re-check standalone-ha-A.xml and standalone-ha-B.xml. I could not find a bug in it. > Thank you, > Mirek -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3354) HornetQ backup server won't start when live server is killed

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3354: ----------------------------------- Summary: HornetQ backup server won't start when live server is killed Key: AS7-3354 URL: https://issues.jboss.org/browse/AS7-3354 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final Test scenario: 1. Start two AS7/EAP6 servers in (hornetq) cluster with HornetQ in colocated topology - server A contains backup for server B and server B contains backup for server A 2. Kill AS7/EAP6 server A using "kill -9 ..." I see following to happen after step 2.: a) HornetQ backup server on server B won't start/come live. b) Server B is not able to update its cluster view. a) and b) -> c) JMS clients on server A are not able to failover to bakcup I've attached reproducer with configuration - reproducer.zip. (logging is set to DEBUG level for "org.hornetq") How to use the reproducer (there are necessary two machines): 1. Download and unzip attached reproducer.zip 2. prepare servers A and B using - "sh prepare.sh" 3. start server A - "sh start-server1.sh serverA_hostname" - on server serverA_hostname 4. start server B - "sh start-server2.sh serverB_hostname" - on server serverB_hostname 5. Kill server A using "kill -9 ..." I've attached JMS client to reproducer (it's using HornetQ core api to create connection factory a queue "testQueue"): 1. Start producer - "sh start-producer.sh server_hostname" 2. Start consumer - "sh start-consumer.sh server_hostname" This could be configuration issue. For this reason I set major priority. Please re-check standalone-ha-A.xml and standalone-ha-B.xml. I could not find a bug in it. Thank you, Mirek -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] (AS7-3350) Combo boxes stop working after hitting cancel

by David Bosschaert (JIRA)

David Bosschaert created AS7-3350: ------------------------------------- Summary: Combo boxes stop working after hitting cancel Key: AS7-3350 URL: https://issues.jboss.org/browse/AS7-3350 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Heiko Braun This is a general issue with the combo-boxes and their interaction with the editing framework. When you edit a subsystem that uses combo boxes (e.g. EJB 3) and then hit cancel instead of save, the combo box becomes unresponsive when trying to edit the subsystem again. The main problem is with combo boxes that have 2 possible values, although if there are 3 values the problem applies to the 2 values involved (the old and the new). I have also seen the same behaviour with combo boxes in various places. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] (AS7-3324) Extend WS EndpointPublisher to allow providing properties/metadata

by Alessio Soldano (JIRA)

Alessio Soldano created AS7-3324: ------------------------------------ Summary: Extend WS EndpointPublisher to allow providing properties/metadata Key: AS7-3324 URL: https://issues.jboss.org/browse/AS7-3324 Project: Application Server 7 Issue Type: Enhancement Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.1.0.Final The EndpointPublisher spi currently allows for providing @WebService/@WebServiceProvider annotated endpoint class and deploy endpoint(s) to the running JBoss AS container with an api pretty much equivalent to the JAXWS Endpoint.publish(..) api. What is missing is the ability of doing something like: {code} List<Source> metadata = new ArrayList<Source>(); StreamSource source = WSDLUtil.getStream(_config.getWsdl()); metadata.add(source); Map<String, Object> properties = new HashMap<String, Object>(); properties.put(Endpoint.WSDL_SERVICE, portName.getServiceQName()); properties.put(Endpoint.WSDL_PORT, portName.getPortQName()); properties.put(WSDL_LOCATION, WSDLUtil.getURL(_config.getWsdl()).toExternalForm()); ... _endpoint = Endpoint.create(wsProvider); // instance of @WebServiceProvider annotated class, with no attributes in the annotation _endpoint.setMetadata(metadata); _endpoint.setProperties(properties); _endpoint.publish(publishUrl); {code} IOW, we need support for setting properties and metadata and passing them down to the stack (Apache CXF already reads them generated DDBeans/descriptor). This is required for a proper SwitchYard integration into AS7. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] (AS7-3353) ActivationSpec.setResourceAdapter called by EJB3

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-3353: ------------------------------------ Summary: ActivationSpec.setResourceAdapter called by EJB3 Key: AS7-3353 URL: https://issues.jboss.org/browse/AS7-3353 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Jesper Pedersen Assignee: jaikiran pai Priority: Critical Fix For: 7.1.0.Final ./ejb3/src/main/java/org/jboss/as/ejb3/component/messagedriven/MessageDrivenComponentCreateService.java calls activationSpec.setResourceAdapter(ra). This is incorrect, since it is done by the JCA SPI. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2525) Server Group VM settings switches back to "default"

by Heiko Braun (Created) (JIRA)

Server Group VM settings switches back to "default" --------------------------------------------------- Key: AS7-2525 URL: https://issues.jboss.org/browse/AS7-2525 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 1.) new server group 2.) add jam setting: "staging", 64m, 64m 3.) after "save" the jam setting "default" is loaded -- 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, 3 months

6
6
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 January 2012