August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBTM-27) Integrate Web Services transactions component with JBoss 4

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-27?page=all ] Mark Little updated JBTM-27: ---------------------------- Fix Version/s: (was: 4.2.1) 4.2.2 Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial]) > Integrate Web Services transactions component with JBoss 4 > ---------------------------------------------------------- > > Key: JBTM-27 > URL: http://jira.jboss.com/jira/browse/JBTM-27 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2.2 > > -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-488) org.jboss.test.messaging.jms.MessageConsumerTest testRedel1() gets stuck occasionally

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-488?page=all ] Ovidiu Feodorov deleted JBMESSAGING-488: ---------------------------------------- > org.jboss.test.messaging.jms.MessageConsumerTest testRedel1() gets stuck occasionally > -------------------------------------------------------------------------------------- > > Key: JBMESSAGING-488 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-488 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-491) Deadlock among ServerConsumerEndpoint.lock and RoundRobinPointToPointRouter.receiver's locks

by Ovidiu Feodorov (JIRA)

Deadlock among ServerConsumerEndpoint.lock and RoundRobinPointToPointRouter.receiver's locks -------------------------------------------------------------------------------------------- Key: JBMESSAGING-491 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-491 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.0.1.CR4 @Thread 3 has 'RoundRobinPointToPointRouter.receivers' and it's waiting for 'ServerConsumerEndpoint.lock' @main has 'ServerConsumerEndpoint.lock' but is waiting for 'RoundRobinPointToPointRouter.receivers' 2006-08-04 10:05:24,065 23390 TRACE [org.jboss.jms.client.delegate.DelegateSupport] (main:) invoking close on server 2006-08-04 10:05:24,065 23390 TRACE [org.jboss.jms.server.container.ServerLogInterceptor] (main:) invoking ConsumerAdvised->ConsumerEndpoint[-2147483430].close() 2006-08-04 10:05:24,065 23390 TRACE [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] (Thread-3:) ConsumerEndpoint[-2147483430] receives reference 3585 for delivery A successful run: 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] @Thread-3 ConsumerEndpoint[-2147483632] receives reference Reference[1]:RELIABLE for delivery 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.jms.client.container.ClientLogInterceptor] @main ConsumerDelegate[-2147483632].closing() OK 2006-08-04 19:49:29,315 3828 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] @Thread-3 ConsumerEndpoint[-2147483632] NOT started yet! 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.jms.client.container.ClientLogInterceptor] @main invoking ConsumerDelegate[-2147483632].close() 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.messaging.core.local.RoundRobinPointToPointRouter] @Thread-3 receiver ConsumerEndpoint[-2147483632] handled Reference[1]:RELIABLE and returned null 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.jms.client.delegate.DelegateSupport] @main invoking close on server 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.jms.server.container.ServerLogInterceptor] @main invoking ConsumerAdvised->ConsumerEndpoint[-2147483632].close() 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.messaging.core.ChannelSupport] @Thread-3 CoreQueue[1]: no delivery returned for messageReference[1]:RELIABLE so no receiver got the message 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.messaging.core.ChannelSupport] @main CoreQueue[1] removed ConsumerEndpoint[-2147483632] 2006-08-04 19:49:29,315 3828 TRACE [org.jboss.messaging.core.ChannelSupport] @Thread-3 Delivery is now complete -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-490) Race condition on ServerConsumerEndpoint creation

by Ovidiu Feodorov (JIRA)

Race condition on ServerConsumerEndpoint creation ------------------------------------------------- Key: JBMESSAGING-490 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-490 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.0.1.CR4 Because "started" is not declared volatile, there's a minor race condition between the construction of the the ServerConsumerEndpoint on a started connection, and delivery request. Test fragment: conn.start(); Session sess = conn.createSession(true, Session.SESSION_TRANSACTED); .... MessageConsumer cons1 = sess.createConsumer(queue); Trace: 2006-08-04 10:05:24,050 23375 DEBUG [org.jboss.jms.server.endpoint.ServerSessionEndpoint] (main:) creating consumer for JBossQueue[Queue], selector null, subscription null 2006-08-04 10:05:24,050 23375 TRACE [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] (main:) creating consumer endpoint -2147483430 2006-08-04 10:05:24,050 23375 TRACE [org.jboss.messaging.core.ChannelSupport] (main:) CoreQueue[1] attempting to add receiver ConsumerEndpoint[-2147483430] 2006-08-04 10:05:24,050 23375 TRACE [org.jboss.messaging.core.ChannelSupport] (main:) receiver ConsumerEndpoint[-2147483430] added 2006-08-04 10:05:24,050 23375 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] (main:) ConsumerEndpoint[-2147483430] created 2006-08-04 10:05:24,050 23375 TRACE [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] (Thread-3:) ConsumerEndpoint[-2147483439] receives reference 3584 for delivery 2006-08-04 10:05:24,050 23375 TRACE [org.jboss.jms.server.endpoint.ServerSessionEndpoint] (main:) SessionEndpoint[-2147483431] caching consumer -2147483430 2006-08-04 10:05:24,050 23375 DEBUG [org.jboss.jms.server.endpoint.ServerConsumerEndpoint] (Thread-3:) ConsumerEndpoint[-2147483439] NOT started yet! -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (BPEL-174) resume process execution after system restart

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-174?page=comments#action_12340695 ] Alejandro Guizar commented on BPEL-174: --------------------------------------- Designed the queries to retrieve unfinished Receive and Pick activities. > resume process execution after system restart > --------------------------------------------- > > Key: BPEL-174 > URL: http://jira.jboss.com/jira/browse/BPEL-174 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > Right now the relation servlet only opens message listeners for activities that create process instances. It must also load existing tokens pointing to inbound message activities and open their corresponding request listeners. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3479) JBoss AS - J2EE Tutorial example/document errors

by Wenbo Zhu (JIRA)

JBoss AS - J2EE Tutorial example/document errors ------------------------------------------------ Key: JBAS-3479 URL: http://jira.jboss.com/jira/browse/JBAS-3479 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Environment: JDK 5, client on windows 2000, and server on RHEL 4. Gone through the complete j2ee (jboss) tutorial with distributed client and server. Reporter: Wenbo Zhu A few errors exist in the current version of JBoss App. Server J2EE tutorial - http://docs.jboss.org/jbossas/getting_started/v5/html/ 1. .\j2eetutorial14\examples\bank\jboss-build.xml - target: app-client.jar requires 4 different classes <jar jarfile="jar/app-client.jar"> <metainf dir="dd/client" includes="*.xml"/> <fileset dir="${build.dir}"> <include name="com/sun/ebank/appclient/**"/> <include name="com/sun/ebank/ejb/exception/**"/> <include name="com/sun/ebank/util/**"/>  <include name="com/sun/ebank/ejb/customer/CustomerControllerHome.class"/> <include name="com/sun/ebank/ejb/customer/CustomerController.class"/> <include name="com/sun/ebank/ejb/account/AccountControllerHome.class"/> <include name="com/sun/ebank/ejb/account/AccountController.class"/> </fileset> </jar> 2. .\j2eetutorial14\examples\bank\jboss-build.xml - client class path misses certain jars to run all the examples <path id="client.classpath"> <pathelement location="${build.dir}"/> <fileset dir="${jboss.home}/client"> <include name="**/*.jar"/> </fileset>  <fileset dir="${jboss.home}/lib/endorsed"> <include name="**/*.jar"/> </fileset> </path> 3. doc error: http://docs.jboss.org/jbossas/getting_started/v5/html/ws.html#d0e1370 (section 5.2) http://localhost:8080/bankws-ejb/TellerService?wsdl. == should be => http://localhost:8080/bankws-ejb/TellerBean?wsdl. 4. .\j2eetutorial14\examples\ejb\simplemessage\jboss-build.xml, and a few others (a suggestion for client app targets in general)  <target name="run-mdb"> <java classname="SimpleMessageClient" fork="yes"> <classpath>  <pathelement path="dd"/> <pathelement path="jar/mdb-app-client.jar"/> <path refid="client.classpath"/> <pathelement path="${java.class.path}"/> </classpath> </java> </target> There're also some minor issues with mySQL and Oracle examples, but I guess it's out of the jboss AS scope anyway. Thanks, Wenbo -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340693 ] Remy Maucherat commented on JBAS-3242: -------------------------------------- Thanks. > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBSEAM-151) Create debug page for remoting framework

by Shane Bryzak (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-151?page=all ] Shane Bryzak reassigned JBSEAM-151: ----------------------------------- Assignee: Shane Bryzak > Create debug page for remoting framework > ---------------------------------------- > > Key: JBSEAM-151 > URL: http://jira.jboss.com/jira/browse/JBSEAM-151 > Project: JBoss Seam > Issue Type: Task > Components: Remoting > Affects Versions: 1.0 beta 2 > Reporter: Shane Bryzak > Assigned To: Shane Bryzak > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > The remoting framework should provide a debug page that allows a user to conveniently make remoting calls to test their components. It should be accessible via a url such as /<app>/seam/remoting/debug/<componentName>. The page should list all of the remotable methods of the component, and provide an easy way of invoking each method and viewing its result. It should also allow additional context parameters (such as conversation ID) to be set for an invocation. For methods that accept complex types, collections or maps as parameters there should be an easy way for the user to specify these values. > The availability of the debug page should be controlled via a "debug" parameter in the remoting servlet configuration in web.xml, and be turned off by default. This would allow the application to be deployed in a production environment without the debug pages. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBSEAM-280) Integrate the page context with Seam Remoting

by Shane Bryzak (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-280?page=all ] Shane Bryzak reassigned JBSEAM-280: ----------------------------------- Assignee: Shane Bryzak > Integrate the page context with Seam Remoting > --------------------------------------------- > > Key: JBSEAM-280 > URL: http://jira.jboss.com/jira/browse/JBSEAM-280 > Project: JBoss Seam > Issue Type: Feature Request > Components: Remoting > Reporter: Shane Bryzak > Assigned To: Shane Bryzak > Fix For: 1.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Support the propogation of Seam's Page Context between remoting requests. > Functional Requirements: > * The page context should be stored client-side in the global js variable Seam.pageContext. > * The page context should be included in any Seam Remoting requests in the packet header, i.e.: > <page-context><variable name="foo"><ref id="0"/></variable>...</page-context> > * The page context should be returned by all remoting requests and replace the local copy > * The client web page should be able to manipulate the page context, changing values, adding new values, etc via Seam.pageContext, e.g. Seam.pageContext.foo = bar; > Non functional requirements: > * Add a server-side convenience method to convert an object to serialized XML > * Add a client-side convenience method to deserialize XML into an object > * Create a <pageContext/> JSF tag that will embed a <script> block into the web page that initializes the page context when the page is first loaded > * Modify the client-side remoting framework to support the dynamic discovery of object types. Use the __type field (or something similar) to identify the object type. This will mean that type stubs will not need to be explicitly imported. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBSEAM-281) Use seam configuration api for settable things

by Shane Bryzak (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-281?page=all ] Shane Bryzak reassigned JBSEAM-281: ----------------------------------- Assignee: Shane Bryzak > Use seam configuration api for settable things > ---------------------------------------------- > > Key: JBSEAM-281 > URL: http://jira.jboss.com/jira/browse/JBSEAM-281 > Project: JBoss Seam > Issue Type: Feature Request > Components: Remoting > Reporter: Gavin King > Assigned To: Shane Bryzak > > these things should all be doable via components.xml or seam.properties: > Seam.Remoting.setPollTimeout(2); // 10 seconds > Seam.Remoting.setPollInterval(1); // 1 second > Seam.Remoting.setDebug(true); -- 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

19 years, 11 months

1
0
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 August 2006