January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3261) Update thread pool property modifications

by Heiko Braun (Created) (JIRA)

Update thread pool property modifications ----------------------------------------- Key: AS7-3261 URL: https://issues.jboss.org/browse/AS7-3261 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun 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

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (AS7-3437) JMS clients - Remote JNDI lookup does not work in EAP6/AS7

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran moved JBPAPP-7989 to AS7-3437: ------------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3437 (was: JBPAPP-7989) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 DR 5) Component/s: (was: System) (was: HornetQ) Security: (was: Public) Fix Version/s: 7.1.0.Final (was: TBD EAP 6) Docs QE Status: (was: NEW) > JMS clients - Remote JNDI lookup does not work in EAP6/AS7 > ---------------------------------------------------------- > > Key: AS7-3437 > URL: https://issues.jboss.org/browse/AS7-3437 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: David Lloyd > Priority: Blocker > Labels: eap6_prd_req > Fix For: 7.1.0.Final > > > EAP6/AS7 have not yet implemented remote jndi lookups. This feature is important for standalone jms clients to work and also ensure backward compatibility with EAP5/AS6 applications. Following piece of code should work without change: > Properties properties = new Properties(); > properties.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); > properties.setProperty("java.naming.provider.url", "jnp://server_hostname:1099"); > properties.setProperty("java.naming.factory.url.pkgs", "org.jnp.interfaces.NamingContextFactory"); > context = new InitialContext(properties); > ConnectionFactory cf = (ConnectionFactory) context.lookup("RemoteConnectionFactory"); > con = cf.createConnection(); > session = con.createSession(false, Session.CLIENT_ACKNOWLEDGE); > Queue queue = (Queue) context.lookup("/queue/test"); > For now there is a workaround but it's not suitable for us. Example code: > https://github.com/jbossas/jboss-as/tree/master/demos/legacy/src/main/jav... > There are AS7 jiras related to this missing feature which are closed as rejected/duplicated. In AS7-1338 J. Green explains that some kind of remote jndi functionality will be in AS 7.1 (as part of the EE full profile). Unfortunately AS 7.1 is still missing this feature. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-3128 at 1/24/12 7:09 PM: ------------------------------------------------------------ Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. I suggest something like {code:xml} <waitForPorts>5050 9990</waitForPorts> {code} was (Author: ozizka): Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-1820) CLONE - CLI - provide description for "add-jms-cf " command with examples

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-1820?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-1820: ------------------------------------ Fix Version/s: 7.1.1.Final (was: 7.1.0.Final) > CLONE - CLI - provide description for "add-jms-cf " command with examples > ------------------------------------------------------------------------- > > Key: AS7-1820 > URL: https://issues.jboss.org/browse/AS7-1820 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.1.Final > > > Command "add-jms-cf" is missing description for all attributes. Could it be improved, please? Also examples of usages would be very helpful. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3128: ----------------------------------- Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3089) Netty Acceptor incorrectly build -- version expression not replaced

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-3089?page=com.atlassian.jira.plugin.s... ] Paul Gier resolved AS7-3089. ---------------------------- Resolution: Out of Date I wasn't able to reproduce this with the latest AS7 master, I think it was fixed with a hornetq upgrade. > Netty Acceptor incorrectly build -- version expression not replaced > ------------------------------------------------------------------- > > Key: AS7-3089 > URL: https://issues.jboss.org/browse/AS7-3089 > Project: Application Server 7 > Issue Type: Bug > Components: Build System > Affects Versions: 7.1.0.Beta1b > Reporter: Radoslav Husar > Assignee: Paul Gier > Fix For: 7.1.0.Final > > > See the server log: > {code}[Server:server-two] 15:11:34,393 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost.localdomain:5605 for CORE protocol{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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3115) Immediate EL syntax does not work with JSF 1.2

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-3115?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran closed AS7-3115. ----------------------------------- Fix Version/s: No Release (was: 7.1.0.Final) Resolution: Rejected EL 2.2 parser included in JBossWeb correctly figures out that "the dot part" (new) is a Java keyword and thus throws the exception. This check is not performed by default in implementation provided by EWS1 and EAP5, thus the exception. Note: For Tomcat 6, the check can be enforced by specifying following property: One has to set org.apache.el.parser.SKIP_IDENTIFIER_CHECK property to "false". Closed as not a bug. > Immediate EL syntax does not work with JSF 1.2 > ---------------------------------------------- > > Key: AS7-3115 > URL: https://issues.jboss.org/browse/AS7-3115 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.0.Beta1b > Reporter: Karel Piwko > Assignee: Remy Maucherat > Fix For: No Release > > Attachments: petclinic-hibernate4.zip > > > Following code is broken for AS7, however it works on Tomcat 5 and Tomcat 6: > {code:xml} > <h2><c:if test="${owner.new}">New </c:if>Owner:</h2> > {code} > where Owner is a POJO/Hibernate Entity and isNew() boolean is available on its ancestor. > Failure: > {code} > org.apache.jasper.JasperException: /WEB-INF/jsp/ownerForm.jsp(4,4) "${owner.new}" contains invalid expression(s): javax.el.ELException: Failed to parse the expression [${owner.new}] > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:198) > org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1216) > org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:862) > org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530) > org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) > org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2427) > org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2433) > org.apache.jasper.compiler.Node$Root.accept(Node.java:495) > org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) > org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1793) > org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:211) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:360) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) > javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238) > org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:262) > org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1157) > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:927) > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827) > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778) > javax.servlet.http.HttpServlet.service(HttpServlet.java:734) > javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > {code} > Note that deferred syntax #{owner.new} works correctly there. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3436) CLONE - Missing server profiles in AS7

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/AS7-3436?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on AS7-3436: ------------------------------------- Changes on this branch, pull request to be sent after addditional review: https://github.com/smcgowan/jboss-as/commit/d6777cdf1f21ea2477a4cea5b8ee0... > CLONE - Missing server profiles in AS7 > -------------------------------------- > > Key: AS7-3436 > URL: https://issues.jboss.org/browse/AS7-3436 > Project: Application Server 7 > Issue Type: Bug > Reporter: Rajesh Rajasekaran > Assignee: Shelly McGowan > Priority: Critical > Fix For: 7.1.0.Final > > > EAP6 is missing the following server profiles from the earlier builds. There was an original requirement to ship these profiles. > Standalone (Web profile/HA) > Domain (Web profile/non-HA) > Domain (Web profile/HA) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3436) CLONE - Missing server profiles in AS7

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-3436?page=com.atlassian.jira.plugin.s... ] Paul Gier moved JBPAPP-7988 to AS7-3436: ---------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3436 (was: JBPAPP-7988) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 DR 8) Component/s: (was: Build) Security: (was: Public) Fix Version/s: 7.1.0.Final (was: EAP 6.0.0 ER 1) Docs QE Status: (was: NEW) > CLONE - Missing server profiles in AS7 > -------------------------------------- > > Key: AS7-3436 > URL: https://issues.jboss.org/browse/AS7-3436 > Project: Application Server 7 > Issue Type: Bug > Reporter: Rajesh Rajasekaran > Assignee: Shelly McGowan > Priority: Critical > Fix For: 7.1.0.Final > > > EAP6 is missing the following server profiles from the earlier builds. There was an original requirement to ship these profiles. > Standalone (Web profile/HA) > Domain (Web profile/non-HA) > Domain (Web profile/HA) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-3199: ------------------------------------ Fix Version/s: 7.1.0.Final Priority: Critical (was: Blocker) Labels: eap6_prd_req (was: ) Assignee: Stuart Douglas (was: Weinan Li) This item in the spec is obviously not covered in the JAX-RS tck, and we are focusing on integration tests that target all SPEC requirements. > RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present > --------------------------------------------------------------------------------------------- > > Key: AS7-3199 > URL: https://issues.jboss.org/browse/AS7-3199 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stuart Douglas > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.0.Final > > Attachments: ExampleJAXRS.war > > > If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed." > This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for > more than one application to be deployed +at the same effective servlet mapping+". > If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+. -- 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

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012