July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-635) Wrong classloader used for plugins

by Jesper Pedersen (JIRA)

Wrong classloader used for plugins ---------------------------------- Key: JBJCA-635 URL: https://issues.jboss.org/browse/JBJCA-635 Project: IronJacamar Issue Type: Bug Components: JDBC Affects Versions: 1.0.0.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.1.Final, 1.1.0.Alpha1 The wrong classloader is used to load plugins for the JDBC resource adapter -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1380) EJB component annotation scanning deployers should ignore component declaring annotations on interfaces

by jaikiran pai (JIRA)

EJB component annotation scanning deployers should ignore component declaring annotations on interfaces ------------------------------------------------------------------------------------------------------- Key: AS7-1380 URL: https://issues.jboss.org/browse/AS7-1380 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.0.0.Final Reporter: jaikiran pai Assignee: jaikiran pai Consider this interface: {code} @Stateless public interface IAmAnInterface { .. {code} We should not be picking up this interface as a component. We should only pickup these annotations from a class. We can just log a WARN about this incorrect annotation and skip its processing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1167) Implement PLAIN SASL mechanism

by Darran Lofthouse (JIRA)

Implement PLAIN SASL mechanism ------------------------------ Key: AS7-1167 URL: https://issues.jboss.org/browse/AS7-1167 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Ales Justin commented on JBAS-8297: ----------------------------------- >> A web build from the AS 7 branch is not going to be directly compatible. How much effort is to port the changes / patch? > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Remy Maucherat > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JGRP-193) RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-193?page=com.atlassian.jira.plugin.s... ] Bela Ban commented on JGRP-193: ------------------------------- This was finally done in 3.0 ! > RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature > ---------------------------------------------------------------------------- > > Key: JGRP-193 > URL: https://issues.jboss.org/browse/JGRP-193 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.2.9.1, 2.3, 2.4, 2.5, 3.x > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.0 > > > This will requirec code changes to callers of these methods, so this will make it not API compatible with previous versions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1232) :test-connection-in-pool is "useless"

by Heiko Rupp (JIRA)

:test-connection-in-pool is "useless" ------------------------------------- Key: AS7-1232 URL: https://issues.jboss.org/browse/AS7-1232 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp I have defined a datasource like this: [domain@localhost:9999 data-source=postresDS] :read-resource { "outcome" => "success", "result" => { "connection-url" => "jdbc:yadayada", "driver-name" => "postgresql-9.0-801.jdbc4.jar", So obviously with an invalid driver. But still I get [domain@localhost:9999 data-source=postresDS] :test-connection-in-pool { "outcome" => "success", "result" => undefined } which makes imho no sense. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Remy Maucherat commented on JBAS-8297: -------------------------------------- A web build from the AS 7 branch is not going to be directly compatible. > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Remy Maucherat > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-203) Segfault if not enought threads

by Dmitry Murashenkov (JIRA)

Segfault if not enought threads ------------------------------- Key: JBWEB-203 URL: https://issues.jboss.org/browse/JBWEB-203 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Environment: JBoss 6, Debian 6.0.1, JBoss native APR connector 2.0.9 Reporter: Dmitry Murashenkov Assignee: Remy Maucherat Attachments: hs_err_pid13822.log If number of requests to server is larger than the max number of worker threads - segmentation fault is raised very often. This bug was originally reported against tomcat native library, but is present in jboss native connector too: https://issues.apache.org/bugzilla/show_bug.cgi?id=49595 TC: 1. Setup ARP. In case of debian we tried: libs (libtcnative and its dependencies) that are available in debian repository, jboss native 2.0.9 linux binary package, tried compiling 2.0.9 package from source. In all cases we validated that neccessary lib is used via ldd and pmap. 2. Setup few worker threads in http connector: <Connector ... maxThreads="1"/> 3. Start sending http requests to server in parallel. In our case load client is sending requests in 40 parallel threads. So it tries to open new connection and send request to maintain parallel sending rate, often get Connection reset by peer exception and tries again. After 15-25 seconds of such load jboss crashes with segmentation fault. In our case the bug is reproduced in 100% cases in this period of time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1347) RA property representation is incompatible with DMR model

by Heiko Braun (JIRA)

RA property representation is incompatible with DMR model --------------------------------------------------------- Key: AS7-1347 URL: https://issues.jboss.org/browse/AS7-1347 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Jesper Pedersen Priority: Critical Fix For: 7.1.0.Alpha1 They way the resource adapter properties are currently represented they cannot be described in a DMR operation and thus not be added/created. Take a look at xa-data-source properties to see how it should be done. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1346) Adding RA fails

by Heiko Braun (JIRA)

Adding RA fails --------------- Key: AS7-1346 URL: https://issues.jboss.org/browse/AS7-1346 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Jesper Pedersen Fix For: 7.1.0.Alpha1 Adding a new RA fails: {noformat} Request: [INFO] { [INFO] "operation" => "add", [INFO] "address" => [ [INFO] ("subsystem" => "resource-adapters"), [INFO] ("resource-adapter" => "xmpp") [INFO] ], [INFO] "archive" => "xmpp-ra.rar", [INFO] "transaction-support" => "NoTransaction", [INFO] "connection-definitions" => [{ [INFO] "class-name" => "com.ramphastos.xmpp.XmppConnectionFactory", [INFO] "jndi-name" => "eis/xmpp2", [INFO] "pool-name" => "xmpp_Pool" [INFO] }] [INFO] } Server Log: 11:11:43,826 ERROR [org.jboss.as.controller] (pool-2-thread-2) Operation ("remove") failed - address: ([ ("subsystem" => "resource-adapters"), ("resource-adapter" => "xmpp") ]): java.util.NoSuchElementException: "resource-adapter" => "xmpp" at org.jboss.as.controller.registry.BasicResource.requireChild(BasicResource.java:95) at org.jboss.as.controller.OperationContextImpl.readModel(OperationContextImpl.java:697) at org.jboss.as.connector.subsystems.resourceadapters.RaRemove.execute(RaRemove.java:51) at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351) at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011