January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3395) org.osgi.util.tracker.* classes duplicated in several bundles.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3395: --------------------------------- Summary: org.osgi.util.tracker.* classes duplicated in several bundles. Key: AS7-3395 URL: https://issues.jboss.org/browse/AS7-3395 Project: Application Server 7 Issue Type: Quality Risk Reporter: Ondrej Zizka -- 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

2
2
0 / 0

[JBoss JIRA] (AS7-3215) EJB remote client context does not survive server restart

by Ivo Studensky (Created) (JIRA)

EJB remote client context does not survive server restart --------------------------------------------------------- Key: AS7-3215 URL: https://issues.jboss.org/browse/AS7-3215 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.0.CR1b Reporter: Ivo Studensky Assignee: Stuart Douglas Let's say we have an AS7 server with a stateless bean deployed at it and a client application which: 1. calls remotely the stateless bean 2. restarts the server 3. and calls the stateless bean again The first invocation of the stateless bean instantiates some static fields in EJBInvocationHandler, EJBClientContext, etc. like a new remote connection, an ejb receiver and so on, and returns a proxy for the bean and does the remote call successfully. But after the server is restarted, the second invocation of the stateless bean does not re-create/re-instantiate any new remote connection or other ejb client utils and fails with IllegalStateException: No EJB receiver available for handling ... combination. Note that EJBClientContext#ejbReceiverAssociations is empty at that time. See the following stacktrace snippet: {noformat} java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:crash,distinctname:] combination at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:344) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:92) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:83) at $Proxy22.test(Unknown Source) at org.jboss.as.test.jbossts.ejbclienttest.EJBClientCrashTestCase.testCrashOnClient(EJBClientCrashTestCase.java:103) {noformat} Test-case for this issue can be found here: https://github.com/istudens/jboss-as/compare/crash_rec_tests#diff-36 More detailed info how to reproduce the bug has been attached to 'Steps to Reproduce' of this jira. -- 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

8
9
0 / 0

[JBoss JIRA] Created: (AS7-1734) Console Usability: error windows cannot be maximized

by Radoslav Husar (JIRA)

Console Usability: error windows cannot be maximized ---------------------------------------------------- Key: AS7-1734 URL: https://issues.jboss.org/browse/AS7-1734 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Radoslav Husar Assignee: Heiko Braun See the screenshot what is the maximum size I can get. Really cripples the large screens. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1456) Messages stuck in being-delivered state in cluster

by Justin Bertram (JIRA)

Messages stuck in being-delivered state in cluster -------------------------------------------------- Key: JBMESSAGING-1456 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1456 Project: JBoss Messaging Issue Type: Bug Reporter: Justin Bertram Assignee: Tim Fox Priority: Critical Messages become "stuck" in being-delivered state when clients use a clustered XA connection factory in a cluster of at least 2 nodes. JBoss setup: -2 nodes of JBoss EAP 4.3 CP02 -commented out "ClusterPullConnectionFactory" in messaging-service.xml to prevent message redistribution and eliminate the "message suckers" as the potential culprit -MySQL backend using the default mysql-persistence-service.xml (from <JBOSS_HOME>/docs/examples/jms) Client setup: -both nodes have a client which is a separate process (i.e. not inside JBoss) -clients are Spring based -one client produces and consumes, the other client just consumes -both clients use the ClusteredXAConnectionFactory from the default connection-factories-service.xml -both clients publish to and consume from "queue/testDistributedQueue" -clients are configured to send persistent messages, use AUTO_ACKNOWLEDGE, and transacted sessions Symptoms of the issue: -when running the clients I watch the JMX-Console for the "queue/testDistributedQueue" -as the consumers pull messages off the queue I can see the MessageCount and DeliveringCount go to 0 every so often -after a period of time (usually a few hours) the MessageCount and DeliveringCount never go back to 0 -I "kill" the clients and wait for the DeliveringCount to go to 0, but it never does -after the clients are killed the ConsumerCount for the queue will drop, but never to 0 when messages are "stuck" -a thread dump reveals at least one JBM server session that is apparently stuck (it never goes away) - ostensibly this is the consumer that is showing in the JMX-Console for "queue/testDistributedQueue" -a "killall -3 java" doesn't produce anything from the clients so I know their dead -nothing is in any DLQ or expiry queue -the database contains as many rows in the JBM_MSG and JBM_MSG_REF tables as the DeliveringCount in the JMX-Console -rebooting the node with the stuck messages frees the messages to be consumed (i.e. un-sticks them) Other notes: -nothing else is happening on either node but running the client and running JBoss -this only appears to happen when a clustered connection factory is used. I tested using a normal connection factory and after 24 hours couldn't reproduce a stuck message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

11
102
0 / 0

[JBoss JIRA] (AS7-3285) Annotated classes excluded in module import are still processed during deployment.

by Peter Skopek (JIRA)

Peter Skopek created AS7-3285: --------------------------------- Summary: Annotated classes excluded in module import are still processed during deployment. Key: AS7-3285 URL: https://issues.jboss.org/browse/AS7-3285 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.CR1b Reporter: Peter Skopek Assignee: Jason Greene Fix For: 7.1.0.Final Annotation attribute works, but import filter is not taken into account and all annotations found in dependant module are processed. See in following server log snippet that @WebServiceProvider at class org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP is processed despite the class was ordered to not be imported in jboss-deployment-structure.xml. 11:15:08,018 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "picketlink-sts.war" 11:22:31,125 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service id=PicketLinkSTS address=http://localhost:8080/picketlink-sts implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort wsdlLocation=null mtomEnabled=false 11:22:31,126 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service id=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP address=http://localhost:8080/picketlink-sts/SOAPSAMLXACMLPDP implementor=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPDP portName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPort wsdlLocation=null mtomEnabled=false Content of my jboss-deployment-structure.xml {noformat} <jboss-deployment-structure> <deployment>  <dependencies> <module name="org.picketlink" annotations="true"> <imports> <exclude path="org/picketlink/identity/federation/core/pdp/**"/> </imports> </module> </dependencies> </deployment> </jboss-deployment-structure> {noformat} -- 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
9
0 / 0

[JBoss JIRA] Created: (JBAS-9206) Filter Apache CXF and dependencies

by Alessio Soldano (JIRA)

Filter Apache CXF and dependencies ---------------------------------- Key: JBAS-9206 URL: https://issues.jboss.org/browse/JBAS-9206 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano 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

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8988) Filter log4j, add dep on org.apache.log4j

by David Lloyd (JIRA)

Filter log4j, add dep on org.apache.log4j ----------------------------------------- Key: JBAS-8988 URL: https://issues.jboss.org/browse/JBAS-8988 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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

12 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8986) Filter apache commons-logging, add dep on org.apache.commons.logging

by David Lloyd (JIRA)

Filter apache commons-logging, add dep on org.apache.commons.logging -------------------------------------------------------------------- Key: JBAS-8986 URL: https://issues.jboss.org/browse/JBAS-8986 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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

12 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8987) Filter SLF4J (including impl classes), add dep on org.slf4j and/or org.slf4j.ext

by David Lloyd (JIRA)

Filter SLF4J (including impl classes), add dep on org.slf4j and/or org.slf4j.ext -------------------------------------------------------------------------------- Key: JBAS-8987 URL: https://issues.jboss.org/browse/JBAS-8987 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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

12 years, 8 months

7
9
0 / 0

[JBoss JIRA] Created: (AS7-1947) Startup options jboss.domain.base.dir / jboss.domain.config.dir are ignored

by Michael Voegele (JIRA)

Startup options jboss.domain.base.dir / jboss.domain.config.dir are ignored --------------------------------------------------------------------------- Key: AS7-1947 URL: https://issues.jboss.org/browse/AS7-1947 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.1.Final Reporter: Michael Voegele Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Starting JBoss using _jboss_install/bin/domain.bat -Djboss.home.dir=C:\eplatform\jboss\AS-7.0-Test\_jboss_install -Djboss.domain.base.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain -Djboss.domain.config.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain\configuration leads to Unable to read the logging configuration from 'file:C:\eplatform\jboss\AS-7.0-Test\_jboss_install/domain/configuration/logging.properties' Options jboss.domain.base.dir / jboss.domain.config.dir are ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
12
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