October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4516) The transaction project needs moving out jboss-head since it is obsolete

by Adrian Brock (JIRA)

The transaction project needs moving out jboss-head since it is obsolete ------------------------------------------------------------------------ Key: JBAS-4516 URL: http://jira.jboss.com/jira/browse/JBAS-4516 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA The transaction project in jboss-head is obsolete now that it uses JBossTM. The subtasks of this task describe what needs doing to complete that. -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4517) Remove the old JMSContainerInvoker and ServerSessionPool

by Adrian Brock (JIRA)

Remove the old JMSContainerInvoker and ServerSessionPool -------------------------------------------------------- Key: JBAS-4517 URL: http://jira.jboss.com/jira/browse/JBAS-4517 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA The old EJB2.0 JMSContainerInvoker and supporting classes needs removing from the server module. With one exception (start/stopDelivery) all the features (+many others) are now supported in the jca inbound jms rar. This will remove a dependency on the XIDFactory from the old transaction project which shouldn't even be there. -- 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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4520) Remove testsuite dependency on old transaction manager

by Adrian Brock (JIRA)

Remove testsuite dependency on old transaction manager ------------------------------------------------------ Key: JBAS-4520 URL: http://jira.jboss.com/jira/browse/JBAS-4520 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA The parts of the testsuite that depend upon the old transaction manager need removing. They should either be replaced with JBossTM as an in-memory transaction manager (this could be done by changing the TransactionManagerLocator in the jboss-integration project) or the tests need moving to run inside the appserver. -- 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

17 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4518) EJB3 should not have a dependency on the XID factory

by Adrian Brock (JIRA)

EJB3 should not have a dependency on the XID factory ---------------------------------------------------- Key: JBAS-4518 URL: http://jira.jboss.com/jira/browse/JBAS-4518 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Adrian Brock Assigned To: Carlo de Wolf Fix For: JBossAS-5.0.0.GA The EJB3 dependency on the XIDFactory should not be there. EJB3 should be using the JCA inbound resource adapter. -- 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

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4519) The IIOP dependency on the old transaction needs removing

by Adrian Brock (JIRA)

The IIOP dependency on the old transaction needs removing --------------------------------------------------------- Key: JBAS-4519 URL: http://jira.jboss.com/jira/browse/JBAS-4519 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: IIOP service Reporter: Adrian Brock Assigned To: Francisco Reverbel Fix For: JBossAS-5.0.0.GA The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project. -- 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence

by Jeff Mesnil (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Jeff Mesnil updated JBMESSAGING-381: ------------------------------------ Attachment: patch-JBMESSAGING-381.txt tentative patch. corresponding test case is: export TARGET_CLASS=org.jboss.test.messaging.jms.PersistenceTest export TARGET_TEST=testQueueWithDisabledPersistence test case is: * deploy a queue with disabled persistence * send a few messages with DeliveryMode.PERSISTENT * restart the server * redeploy the same queue * check that the queue is empty (the opposing test is PersistenceTest.testQueuePersistence() which checks that the messages are still in the queue after restart) - Persistent is true by default for destinations. - It can be set only before the destination is started (at deployment time) - a "not persistent" destination corresponds to a MessagingQueue w/o a PersistenceManager and flagged as non recoverable I did not check passing null as a PersistenceManager in ChannelSupport is acceptable... it may generate unexpected NPE... > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: patch-JBMESSAGING-381.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4609) Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1

by stefan lotties (JIRA)

Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1 ------------------------------------------------------------------------------------------------------------------------------------ Key: JBAS-4609 URL: http://jira.jboss.com/jira/browse/JBAS-4609 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Environment: RHeL Reporter: stefan lotties Sometimes in the log the following stacktrace appears while someone is surfing in an application: 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1 at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav a:1018) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056) at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261) at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso r.java:237) at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor. java:300) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java: 469) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator. java:316) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2 44) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java: 156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja va:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. -- 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

17 years, 3 months

5
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1196) Option cacheModeLocal value gets changed during PESSIMISTIC calls

by Brian Stansberry (JIRA)

Option cacheModeLocal value gets changed during PESSIMISTIC calls ----------------------------------------------------------------- Key: JBCACHE-1196 URL: http://jira.jboss.com/jira/browse/JBCACHE-1196 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 2.1.0.BETA1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.1.0.CR1 In org.jboss.cache.options.ForceCacheModeTest I unthinkingly used the same instance of an Option for two invocations. Option.cacheModeLocal meant to be true. Found that with PESSIMISTIC locking enabled, cacheModeLocal would be set to false when the first request returned. This led to intermittent failures in the tests, as the initial state of the system was not as expected. Need to determine why the Option value is being changed. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1069) Include common-io and common-fileupload in the ear configuration

by Fady Matar (JIRA)

Include common-io and common-fileupload in the ear configuration ---------------------------------------------------------------- Key: JBPM-1069 URL: http://jira.jboss.com/jira/browse/JBPM-1069 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Fady Matar Assigned To: Tom Baeyens Priority: Trivial Fix For: jBPM 3.3 Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file) The ear files can be appended to the JBoss AS configuration or can be packaged within the ear -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1269) Import DRL to update existing assets

by Michael Neale (JIRA)

Import DRL to update existing assets ------------------------------------ Key: JBRULES-1269 URL: http://jira.jboss.com/jira/browse/JBRULES-1269 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.1.0 -- 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

17 years, 3 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007