June 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-683) Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo

by Manik Surtani (JIRA)

Proxy to https://s3.amazonaws.com/maven.springframework.org/milestone under public repo --------------------------------------------------------------------------------------- Key: JBBUILD-683 URL: https://issues.jboss.org/browse/JBBUILD-683 Project: JBoss Build System Issue Type: Feature Request Components: Sonatype Reporter: Manik Surtani Assignee: Paul Gier Can we add this repo to the Nexus proxy so I don't have to hardcode it in my project POMs? This is for milestone releases of Spring artefacts that don't go to central. https://s3.amazonaws.com/maven.springframework.org/milestone -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBJCA-594) Can't use a managed connection during interposed synchronization beforeCompletion callback

by Carlo de Wolf (JIRA)

Can't use a managed connection during interposed synchronization beforeCompletion callback ------------------------------------------------------------------------------------------ Key: JBJCA-594 URL: https://issues.jboss.org/browse/JBJCA-594 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.0.Beta6 Reporter: Carlo de Wolf Assignee: Jesper Pedersen {noformat} java.lang.IllegalStateException: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344) at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.getRegisteredSynchronizer(TransactionSynchronizer.java:198) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:210) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:407) ... 104 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
16
0 / 0

[JBoss JIRA] Created: (AS7-978) Seam3 remoting module throws UnsatisfiedResolutionException on @Inject-ing from Remoting Servlet on AS7

by Marek Schmidt (JIRA)

Seam3 remoting module throws UnsatisfiedResolutionException on @Inject-ing from Remoting Servlet on AS7 ------------------------------------------------------------------------------------------------------- Key: AS7-978 URL: https://issues.jboss.org/browse/AS7-978 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Environment: AS7 jboss-7.0.0.Beta4-SNAPSHOT build 1169 Reporter: Marek Schmidt Attachments: remoting-helloworld.war, server.log Seam3 Remoting module doesn't work on AS7, The Remoting class is a HttpServlet, and injects the ExecutionHandler using {code} @Inject Instance<ExecutionHandler> executionHandlerInstance; {code} https://github.com/seam/remoting/blob/master/impl/src/main/java/org/jboss... The application contains the seam-remoting.jar in the WEB-INF/lib Both the Remoting class and the ExecutionHandler are in the seam-remoting.jar The Remoting servlet is declared in META-INF/web-fragment.xml in the seam-remoting.jar beans.xml is located in seam-remoting.jar/META-INF {quote} 13:20:40,561 ERROR [org.jboss.seam.remoting.Remoting] (http-dhcp-26-127.brq.redhat.com-127.0.0.1-8080-2) Error: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [class org.jboss.seam.remoting.ExecutionHandler]; Bindings: [@javax.enterprise.inject.Default()] at org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:809) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:108) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.jboss.seam.remoting.Remoting.getExecutionHandler(Remoting.java:253) [seam-remoting-3.0.0.Final.jar:] at org.jboss.seam.remoting.Remoting.service(Remoting.java:288) [seam-remoting-3.0.0.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:658) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] {quote} the same .war works fine on AS6.1-snapshot with the same version of Weld1.1.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (AS7-980) OSGi WebApp support leaks TCCL

by Thomas Diesler (JIRA)

OSGi WebApp support leaks TCCL ------------------------------ Key: AS7-980 URL: https://issues.jboss.org/browse/AS7-980 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.CR1 when running all osgi integration tests like this $ mvn -DskipTests=false -Dtest=osgi/**/*TestCase test I see the ServletIntegrationTestCase fail due to {code} 15:57:51,063 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "web-osgi-client.war" 15:57:51,071 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."web-osgi-client.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."web-osgi-client.war".PARSE: Failed to process phase PARSE of deployment "web-osgi-client.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: javax.xml.stream.FactoryFinder$ConfigurationError: Provider __redirected.__XMLInputFactory could not be instantiated: java.lang.IllegalStateException: Bundle uninstalled: interceptor-endpoint:0.0.0 at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:158) [:1.6.0_21] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:186) [:1.6.0_21] at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:123) [:1.6.0_21] at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:62) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 4 more {code} The FactoryFinder seems to access an invalid classloader -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (AS7-837) Web parsing may fail due to XMLInputFactory could not be instantiated

by Thomas Diesler (JIRA)

Web parsing may fail due to XMLInputFactory could not be instantiated --------------------------------------------------------------------- Key: AS7-837 URL: https://issues.jboss.org/browse/AS7-837 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.0.0.CR1 when running all osgi integration tests like this $ mvn -DskipTests=false -Dtest=osgi/**/*TestCase test I see the ServletIntegrationTestCase fail due to 15:57:51,063 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "web-osgi-client.war" 15:57:51,071 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."web-osgi-client.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."web-osgi-client.war".PARSE: Failed to process phase PARSE of deployment "web-osgi-client.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: javax.xml.stream.FactoryFinder$ConfigurationError: Provider __redirected.__XMLInputFactory could not be instantiated: java.lang.IllegalStateException: Bundle uninstalled: interceptor-endpoint:0.0.0 at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:158) [:1.6.0_21] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:186) [:1.6.0_21] at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:123) [:1.6.0_21] at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:62) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 4 more The FactoryFinder seems to access an invalid classloader -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
20
0 / 0

[JBoss JIRA] Created: (AS7-976) Restore OSGi example tests

by Thomas Diesler (JIRA)

Restore OSGi example tests -------------------------- Key: AS7-976 URL: https://issues.jboss.org/browse/AS7-976 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-599) Ensure all Negotiation Toolkit Dependencies have Scope Provided

by Darran Lofthouse (JIRA)

Ensure all Negotiation Toolkit Dependencies have Scope Provided --------------------------------------------------------------- Key: SECURITY-599 URL: https://issues.jboss.org/browse/SECURITY-599 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.2.0 All toolkit dependencies need to have scope as provided to ensure they are not bundles in the war. (Also add comment to the pom to ensure this is retained) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1875) SELECT_COUNTER SQL statement in db2-persistence-service.xml is not correct

by Yong Hao Gao (JIRA)

SELECT_COUNTER SQL statement in db2-persistence-service.xml is not correct -------------------------------------------------------------------------- Key: JBMESSAGING-1875 URL: https://issues.jboss.org/browse/JBMESSAGING-1875 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 SELECT_COUNTER statement should acquire proper lock to prevent concurrent read before transaction committed. This is required in JBM updating the JBM_COUNTER table. Current: SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER HOLDLOCK WHERE NAME=? The HOLDLOCK doesn't have any effect on locking. The correct one: SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER WHERE NAME=? WITH RS USE AND KEEP EXCLUSIVE LOCKS -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (AS7-973) CommonXml.parseSchemaLocations fails if there is non-space whitespace in the list such as tabs

by Stuart Douglas (JIRA)

CommonXml.parseSchemaLocations fails if there is non-space whitespace in the list such as tabs ---------------------------------------------------------------------------------------------- Key: AS7-973 URL: https://issues.jboss.org/browse/AS7-973 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-584) Support for multiple mcfs in code generator when JCA >= 1.5

by Jeff Zhang (JIRA)

Support for multiple mcfs in code generator when JCA >= 1.5 ----------------------------------------------------------- Key: JBJCA-584 URL: https://issues.jboss.org/browse/JBJCA-584 Project: IronJacamar Issue Type: Task Components: Code Generator Affects Versions: 1.0.0.Beta6 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
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 June 2011