April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6555) JSR-356 Web Socket Support

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6555?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6555. --------------------------------- Resolution: Done > JSR-356 Web Socket Support > -------------------------- > > Key: AS7-6555 > URL: https://issues.jboss.org/browse/AS7-6555 > Project: Application Server 7 > Issue Type: Sub-task > Components: Web > Reporter: David Lloyd > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Implement JSR-356 web sockets as per Java EE 7 specification. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6652) Add ability to customise timer SQL based on database type

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6652?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6652. --------------------------------- Resolution: Done > Add ability to customise timer SQL based on database type > --------------------------------------------------------- > > Key: AS7-6652 > URL: https://issues.jboss.org/browse/AS7-6652 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6560) JSR-340 Servlet 3.1 API support

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6560?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6560. --------------------------------- Resolution: Done > JSR-340 Servlet 3.1 API support > ------------------------------- > > Key: AS7-6560 > URL: https://issues.jboss.org/browse/AS7-6560 > Project: Application Server 7 > Issue Type: Sub-task > Components: Web > Reporter: David Lloyd > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Implement Servlet 3.1 API as per Java EE 7 specification. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-124) Java API for WebSocket (JSR-356)

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/JBEE-124?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved JBEE-124. --------------------------------- Resolution: Done > Java API for WebSocket (JSR-356) > --------------------------------- > > Key: JBEE-124 > URL: https://issues.jboss.org/browse/JBEE-124 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-websocket-api > Reporter: Shelly McGowan > Assignee: Stuart Douglas > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > These APIs are required as part of our Java EE 7 implementation. > They should be added to the org.jboss.spec project: > {code} > <dependency> > <groupId>org.jboss.spec.javax.websocket</groupId> > <artifactId>jboss-websocket-api_1.0_spec</artifactId> > <version>1.0.0.Final-SNAPSHOT</version> > </dependency> > {code} > Project can be created in http://github.com/jboss/jboss-websocket-api_spec -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6821) Installed library not available to an EAR deployment

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6821?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6821. --------------------------------- Resolution: Done > Installed library not available to an EAR deployment > ---------------------------------------------------- > > Key: AS7-6821 > URL: https://issues.jboss.org/browse/AS7-6821 > Project: Application Server 7 > Issue Type: Bug > Components: EE > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Jozef Hartinger > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > {quote}The referenced libraries must be made available to all components contained within the referencing file, including any components contained within other JAR format files within the referencing file. For example, if a .ear file references an installed library, the library must be made available to all components in all .war files, EJB .jar files, application .jar files, and resource adapter .rar files within the .ear file.{quote} > A referenced installed library seems to only be made available to some (not all) components in an EAR. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6450) Missing <recovery> element. XA recovery disabled for: java:/JmsXA

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6450?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6450: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=907901, https://bugzilla.redhat.com/show_bug.cgi?id=953298 (was: https://bugzilla.redhat.com/show_bug.cgi?id=907901) > Missing <recovery> element. XA recovery disabled for: java:/JmsXA > ----------------------------------------------------------------- > > Key: AS7-6450 > URL: https://issues.jboss.org/browse/AS7-6450 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > With latest version of HornetQ and IronJacamar, when AS7 is started with the standalone-full.xml, it logs a WARN message: > {noformat} > 11:23:11,152 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingpaging) > 11:23:11,154 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221008: Waiting to obtain live lock > 11:23:11,175 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221017: Using NIO Journal > 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221039: Waiting to obtain live lock > 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221040: Live Server Obtained live lock > 11:23:11,489 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol > 11:23:11,490 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol > 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221009: Server is now live > 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [0ac0dcd4-6f7e-11e2-9c21-f566250843f7] > 11:23:11,507 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 11:23:11,508 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 11:23:11,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA > 11:23:11,545 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA > 11:23:11,568 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started > 11:23:11,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra > 11:23:11,570 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > {noformat} > This WARN was not present in AS7 7.1.2.Final -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6935) Deploying dynamic VDB with invalid XML will cause incomprehensible error

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6935?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6935: --------------------------------------- The scanner tries to guard against deploying partially copied files by doing a trivial parse to confirm well-formed xml [1]. It's unlikely there would be any Teiid related logs, as the deployment scanner doesn't even try to execute a management operation to deploy the file if it doesn't pass this check. If you enable DEBUG logging of log category org.jboss.as.server.deployment.scanner you may get some more details. [1] https://github.com/jbossas/jboss-as/blob/master/deployment-scanner/src/ma... > Deploying dynamic VDB with invalid XML will cause incomprehensible error > ------------------------------------------------------------------------ > > Key: AS7-6935 > URL: https://issues.jboss.org/browse/AS7-6935 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Filip Nguyen > Priority: Trivial > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6828) Cannot add empty messaging subsystem using CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6828?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6828: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 947779|https://bugzilla.redhat.com/show_bug.cgi?id=947779] from MODIFIED to ON_QA > Cannot add empty messaging subsystem using CLI > ---------------------------------------------- > > Key: AS7-6828 > URL: https://issues.jboss.org/browse/AS7-6828 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > It's not possible to add empty messaging subsystem using CLI: > [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=backup:add() > { > "outcome" => "failed", > "failure-description" => "JBAS011679: No connectors definition present.", > "rolled-back" => true > } -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6782) JAX-RS does not work with EJB's with a non-default name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6782?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6782: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 927021|https://bugzilla.redhat.com/show_bug.cgi?id=927021] from MODIFIED to ON_QA > JAX-RS does not work with EJB's with a non-default name > ------------------------------------------------------- > > Key: AS7-6782 > URL: https://issues.jboss.org/browse/AS7-6782 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6840) Backup can't start after fallback and another failover

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6840?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6840: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 948247|https://bugzilla.redhat.com/show_bug.cgi?id=948247] from MODIFIED to ON_QA > Backup can't start after fallback and another failover > ------------------------------------------------------ > > Key: AS7-6840 > URL: https://issues.jboss.org/browse/AS7-6840 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > 1. start AS7 + HornetQ configured as backup + allow-tailback > 2. start AS7 + HornetQ configured as live > 3. Shutdown AS7 + HornetQ live > => AS7 + HornetQ backup becomes active > 4. Restart AS7 + HornetQ live > => AS7 + HornetQ backup fails back > => AS7 + HornetQ live becomes active > 3. Shutdown AS7 + HornetQ live again > => AS7 + HornetQ backup does not failover properly: > {noformat} > 18:15:03,296 ERROR [org.hornetq.core.server] (HQ119000: Activation for server > HornetQServerImpl::serverUUID=7c2c4c70-9c79-11e2-abd5-538a3c182844) HQ224000: Failure in initialisation: java.lang.IllegalStateEx > ception: ServiceBuilder is already installed > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:302) > at org.jboss.as.messaging.jms.JMSService$1.activated(JMSService.java:89) [jboss-as-messaging-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4] > at org.hornetq.core.server.impl.HornetQServerImpl.callActivateCallbacks(HornetQServerImpl.java:1358) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1] > at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1581) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1] > at org.hornetq.core.server.impl.HornetQServerImpl.access$1300(HornetQServerImpl.java:169) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1] > at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation.run(HornetQServerImpl.java:2117) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] > {noformat} -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013