June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-844) Create bridge smoke test

by Tim Fox (JIRA)

Create bridge smoke test ------------------------ Key: JBMESSAGING-844 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-844 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA We should create a smoke test that starts 3 nodes, and deploys a bridge on one of them, then bridges messages from one node to another. -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-809) Pojo-style configuration for use by Microcontainer

by Brian Stansberry (JIRA)

Pojo-style configuration for use by Microcontainer -------------------------------------------------- Key: JBCACHE-809 URL: http://jira.jboss.com/jira/browse/JBCACHE-809 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Fix For: 2.0.0 Need to be able construct a 2.0 Cache using the MC. We need Pojo configuration classes for all configuration elements except JGroups protocol stack. MC-style configuration should not rely on injecting a DOM element or a Properties object into any config object. Old style configuration still needs to be supported though. -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1013) Document configuration for the microcontainer

by Brian Stansberry (JIRA)

Document configuration for the microcontainer --------------------------------------------- Key: JBCACHE-1013 URL: http://jira.jboss.com/jira/browse/JBCACHE-1013 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.CR1 -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1469) Portlet window name can not be UTF8

by Dave Chen (JIRA)

Portlet window name can not be UTF8 ----------------------------------- Key: JBPORTAL-1469 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1469 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Environment: JBOSS, IE, MyFaces Reporter: Dave Chen In portal management page, adding a Portlet into a page with a window name in UTF8, the window name was not displayed correctly. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-700) add ability to add descriptions to jmx operations in Service beans

by William DeCoste (JIRA)

add ability to add descriptions to jmx operations in Service beans ------------------------------------------------------------------ Key: EJBTHREE-700 URL: http://jira.jboss.com/jira/browse/EJBTHREE-700 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC8 - FD Reporter: William DeCoste Assigned To: William DeCoste -- 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

16 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-978) NullPointerException within DefaultClusteredPostOffice.handleMessagePullResult()

by Ray Ploski (JIRA)

NullPointerException within DefaultClusteredPostOffice.handleMessagePullResult() -------------------------------------------------------------------------------- Key: JBMESSAGING-978 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-978 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.2.0.SP1 Environment: CentOS 4, JBoss AS 4.0.5, Sun JDK 1.5.07, MySQL 5.x for persistence. Six node cluster. Reporter: Ray Ploski Assigned To: Tim Fox After sending about 10,000 messages through a clustered JMS deployment we received the following error, locking up the topic. I worked around it by adding a null check to the condition within handleMessagePullResult(). Fix is for line 968 of org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice is listed at the end of the description. 2007-05-31 11:41:39,130 ERROR @IncomingMessageHandler (channel=DefaultPostOffice) [DefaultClusteredPostOffice] Caught Exception in Receiver java.lang.NullPointerException at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.handleMessagePullResult(DefaultClusteredPostOffice.java:968) at org.jboss.messaging.core.plugin.postoffice.cluster.PullMessageResultRequest.execute(PullMessageResultRequest.java:105) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$DataReceiver.receive(DefaultClusteredPostOffice.java:2461) at org.jgroups.JChannel.up(JChannel.java:1102) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377) at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:771) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:791) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:154) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.FRAG.up(FRAG.java:168) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:476) at org.jgroups.protocols.UNICAST.up(UNICAST.java:206) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) FIX: if (remoteQueue == null || remoteNodeId != remoteQueue.getNodeId() ) -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-974) concurrent job acquirement fails

by Alexander Schlett (JIRA)

concurrent job acquirement fails -------------------------------- Key: JBPM-974 URL: http://jira.jboss.com/jira/browse/JBPM-974 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Alexander Schlett Assigned To: Tom Baeyens when more than 1 job executor thread is configured and concurrent async nodes are to be executed, it results in hibernate exceptions. reason: job acquirement is not synchronized well, resulting in multiple threads trying to work on the same job. -- 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

16 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-976) The setting "resource.mail.properties" is never used.

by luka kama (JIRA)

The setting "resource.mail.properties" is never used. ----------------------------------------------------- Key: JBPM-976 URL: http://jira.jboss.com/jira/browse/JBPM-976 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2 Reporter: luka kama Assigned To: Tom Baeyens The property "resource.mail.properties" should be used if the property "jbpm.mail.smtp.host" is not defined. The proplem is that "jbpm.mail.smtp.host" is set in the default configuration, so it will be always defined, preventing the "resource.mail.properties" to be used. Maybe the check should be reversed? (check before "resource.mail.properties" and if not set use "jbpm.mail.smtp.host") -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-968) Update documentation with new deployment procedures (clustered/nonclustered)

by Clebert Suconic (JIRA)

Update documentation with new deployment procedures (clustered/nonclustered) ---------------------------------------------------------------------------- Key: JBMESSAGING-968 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-968 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2 -- 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

16 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-973) Implement a DbPersistenceService that delegates to transaction handling to Hibernate

by Matt Read (JIRA)

Implement a DbPersistenceService that delegates to transaction handling to Hibernate ------------------------------------------------------------------------------------ Key: JBPM-973 URL: http://jira.jboss.com/jira/browse/JBPM-973 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Matt Read Assigned To: Tom Baeyens Priority: Minor Attachments: HibernateDbPersistenceServiceFactory.java Rather than use the JtaDbPersistenceService we wanted to delegate all transaction handling to Hibernate. The file attached to this issue needs the following jbpm.cfg.xml: <service name="persistence" factory="com.catlin.workflow.engine.persistence.HibernateDbPersistenceServiceFactory" /> and appropriate session context management in hibernate.cfg.xml: <property name="current_session_context_class">jta</property> or <property name="current_session_context_class">thread</property> -- 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

16 years, 11 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007