July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1462) Message expiration is not correctly managed

by Ivan (JIRA)

Message expiration is not correctly managed ------------------------------------------- Key: JBMESSAGING-1462 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1462 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.1.GA Environment: JBAS 5.0GA, JBM 1.4.1GA, persistence on Oracle 10i Reporter: Ivan Assignee: Tim Fox 1) A topic is created 2) A durable subscriber is created fro the topic 3) A message is sent on the topic 4) The durable subscriber pulls the message from the topic ( receive() ) but don't ack 5) The durable subscriber is closed, subscriber session.unsuscribe(name) is called but an exception is thrown and then the subsciber session is closed. As result of this a message, expired, with DELIVERY_COUNT = 1 will remain on the database forever. -- 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

14 years, 10 months

4
20
0 / 0

[JBoss JIRA] Created: (AS7-1046) AS7 gives NPE when jboss-web.xml is missing from WAR

by Nathan Kopp (JIRA)

AS7 gives NPE when jboss-web.xml is missing from WAR ---------------------------------------------------- Key: AS7-1046 URL: https://issues.jboss.org/browse/AS7-1046 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: Open To Community Environment: Windows XP, JDK 1.6 Reporter: Nathan Kopp Attachments: jaxws-test.war I'm trying to deploy a simple WAR (nearly empty, with a single JAX-WS web service) using a fairly recent snapshot of JBoss AS7. If I do not include jboss-web.xml in the WEB-INF folder, I get the following NPE when deploying to standalone\deployment 12:17:25,356 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."jaxws-test.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-test.war".INSTALL: Failed to process phase INSTALL of deployment "jaxws-test.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_10] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_10] at java.lang.Thread.run(Thread.java:619) [:1.6.0_10] Caused by: java.lang.NullPointerException at org.jboss.as.webservices.util.WebMetaDataHelper.getServlets(WebMetaDataHelper.java:130) at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createServlets(WebMetaDataCreator.java:173) at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createWebAppDescriptor(WebMetaDataCreator.java:109) at org.jboss.as.webservices.tomcat.WebMetaDataCreator.create(WebMetaDataCreator.java:93) at org.jboss.as.webservices.tomcat.WebMetaDataCreatingDeploymentAspect.start(WebMetaDataCreatingDeploymentAspect.java:48) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:78) at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:42) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 4 more When I add a very simple jboss-web.xml file (containing only the context-root tag), the deployment succeeds. Attached is the WAR file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
6
0 / 0

[JBoss JIRA] Created: (AS7-1216) NonexistentConversationException when attempting to restore a long-running conversation on AS 7 CR1 and not beta3

by Drew Stockdreher (JIRA)

NonexistentConversationException when attempting to restore a long-running conversation on AS 7 CR1 and not beta3 ----------------------------------------------------------------------------------------------------------------- Key: AS7-1216 URL: https://issues.jboss.org/browse/AS7-1216 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.0.CR1 Environment: Windows XP 32 bit, JBoss AS 7 CR1 and Firefox 5 Reporter: Drew Stockdreher A simple web application which starts a long-running conversation via an <f:event type="preRenderView" listener="#{bean.startConvo}"/> tag. Selecting from a selectOneMenuList makes an ajax request which was working on the beta3 release of AS 7 is no longer working with the following stacktrace. This does however still work in IE 7 and Chrome 12 on both beta3 and CR1 releases. 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) org.jboss.weld.context.NonexistentConversationException: WELD-000321 No conversation found to restore for id 1 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:108) 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:84) 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111) 10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) 10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) 10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) 10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) 10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) 10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1392) Description in scripts to secure the api wrong

by Heiko Rupp (JIRA)

Description in scripts to secure the api wrong ---------------------------------------------- Key: AS7-1392 URL: https://issues.jboss.org/browse/AS7-1392 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry Script says to execute snert:~/downloads/jboss-as-web-7.0.0.Final hrupp$ bin/jboss-admin.sh -c --file=scripts/secure-standalone-mgmt.cli File /Users/hrupp/Downloads/jboss-as-web-7.0.0.Final/scripts/secure-standalone-mgmt.cli doesn't exist. which fails. Also the description in the file fails to mention that the server must be started for this (or alternatively to start the server, but as it a cli script, this is probably not expected). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-756) Subsystem "jms": Attributes are read-only

by Heiko Braun (JIRA)

Subsystem "jms": Attributes are read-only ----------------------------------------- Key: AS7-756 URL: https://issues.jboss.org/browse/AS7-756 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Reporter: Heiko Braun Assignee: Jason Greene changing queue and topic attributes fails, because all of them are read-only -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-759) Subsystem "messaging": security-settings and addressing settings should be subresoures

by Heiko Braun (JIRA)

Subsystem "messaging": security-settings and addressing settings should be subresoures -------------------------------------------------------------------------------------- Key: AS7-759 URL: https://issues.jboss.org/browse/AS7-759 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Jason Greene otherwise it's not possible to update these settings. If they would be subresources then the generic #add() and #remove() operations would apply. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1273) Applications (or their libraries) containing persistence units with the connection defined inline via properties case deployment failure.

by Justin Wyer (JIRA)

Applications (or their libraries) containing persistence units with the connection defined inline via properties case deployment failure. ----------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-1273 URL: https://issues.jboss.org/browse/AS7-1273 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Reporter: Justin Wyer Assignee: Scott Marlow Persistence units defined as follows https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/src/main/r... causes deployment to fail due to the fact that no <jta-data-source> or <non-jta-data-source> is present, but none should be present as the datasource has been defined via the properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1287) Use of reserved word as bound variable in a pattern results as NPE

by Justin Wick (JIRA)

Use of reserved word as bound variable in a pattern results as NPE ------------------------------------------------------------------ Key: JBRULES-1287 URL: http://jira.jboss.com/jira/browse/JBRULES-1287 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Eclipse IDE Affects Versions: 4.0.2 Environment: Eclipse 3.2, Windows XP Reporter: Justin Wick Assigned To: Mark Proctor example: rule "This generates an NPE" when result : ReservedWordNPEFact(data < 15) then result.setData(new Integer(1)); end At least in the eclipse IDE, this generates an NPE. Change result to something like: rule "This generates an NPE" when f: ReservedWordNPEFact(data < 15) then f.setData(new Integer(1)); end and it goes away. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBRULES-552) Outline problems in DRL editor

by Dirk Bergstrom (JIRA)

Outline problems in DRL editor ------------------------------ Key: JBRULES-552 URL: http://jira.jboss.com/jira/browse/JBRULES-552 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-1331) Digest: remove low seqno

by Bela Ban (JIRA)

Digest: remove low seqno ------------------------ Key: JGRP-1331 URL: https://issues.jboss.org/browse/JGRP-1331 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.1 We don't need Digest.Entry.low_seqno for NakReceiverWindow anymore. We only need it for the Retransmitter implementations. If we can remove that last dependency, e.g. by storing the last seqno removed from a retransmitter, we can remove low_seqno from a digest. This is significant, for example if we have 100 nodes, a digest includes 300 longs:(low+highest_received+highest_delivered) * 100. If we remove low_seqno, we only have 200 longs. (These will still be further compressed in a different JIRA). This is important for large clusters, to reduce the size of STABLE messages and views. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
11
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 July 2011