April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-779) MDB doesn't rebind after JBOSS MQ recover

by Ramil Israfilov (JIRA)

MDB doesn't rebind after JBOSS MQ recover ------------------------------------------ Key: EJBTHREE-779 URL: http://jira.jboss.com/jira/browse/EJBTHREE-779 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - FD Environment: Solarisx86, JDK1.5_06 Reporter: Ramil Israfilov Priority: Critical Fix For: EJB 3.0 RC10 - FD I have an MDB which is described using annotations: @Depends("jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider") @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/certione/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "dLQMaxResent", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }, messageListenerInterface=MessageListener.class) public class EJBExecutorMDB implements MessageListener { ... } I deploy it in clustered environment with HAJNDI and clustered JBOSS MQ. So far so good. Then cluster node on which JBOSS MQ is running crashed MDB is not rebind. >From log file I see that JBOSS MQ successfully restarted on second node. And all permamnet queue destinations (defined in config files) are available, but destinations which are defined in annotations don't exist. And in log file I see that server constantly tries bind MDB, but got alway the same error: javax.naming.NameNotFoundException: queue/certione/ExecutorQueue at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy249.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.util.naming.Util.lookup(Util.java:215) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:399) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:306) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:250) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.onException(AbstractDLQHandler.java:94) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348) at java.lang.Thread.run(Thread.java:595) -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-395) drools-repository API

by Michael Neale (JIRA)

drools-repository API --------------------- Key: JBRULES-395 URL: http://jira.jboss.com/jira/browse/JBRULES-395 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the parent task for the drools-repository module and API. This covers the back end storage, using JCR, and the API over it (not the front end). All specific tasks should be sub tasks of this. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-936) sql server clustered configuration needs sql field escaping

by pkorros (JIRA)

sql server clustered configuration needs sql field escaping ----------------------------------------------------------- Key: JBMESSAGING-936 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-936 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.2.0.SP1 Environment: JBoss 4.0.5, MS SQLServer 2005 SP2 Reporter: pkorros Assigned To: Clebert Suconic The clustered-mssql-persistence-service.xml file contains sql statements that are invalid for MS SQL Server 2005. The 'clustered' field is a reserved word for this server so it needs escaping. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-850) Start connection factories from LocalTestServer.startServerPeer() as they used to be

by Ovidiu Feodorov (JIRA)

Start connection factories from LocalTestServer.startServerPeer() as they used to be ------------------------------------------------------------------------------------ Key: JBMESSAGING-850 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-850 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Priority: Minor Fix For: 1.2.1 Ovidiu wrote: Your latest changes broke this convention, you deploy/start ConnectionFactories outside startServerPeer(). Specifically, you deploy stuff specified in "server/default/deploy/connection-factories-service.xml" in ServiceContainer.startDatasource() (I renamed it temporarily startConnectionFactories()). Clebert wrote: I considered ConnectionFactory as part of the services started, and as ServerPeer would be also a Service I thought about making the refactoring. Ovidiu wrote: ConnectionFactory are services, that is true, but it doesn't make any sense to deploy and start a connection factory unless you have a messaging server running. ServerPeer is also a service, and all of them are happily deployed together in startServerPeer(). Or at least they used to. Clebert wrote: Besides, the parameter to start the HTTPConnectionFactory is set on ServiceContainer (boolean httpConnectionFactory), as this is cross-referenced with the start of Remoting. Ovidiu wrote: Fine. Use a variable and pass that variable to startServerPeer(). Clebert wrote: If you like I could refactor the method back to LocalServer. Ovidiu wrote: Yes, please -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-708) Full MVEL integration

by Mark Proctor (JIRA)

Full MVEL integration --------------------- Key: JBRULES-708 URL: http://jira.jboss.com/jira/browse/JBRULES-708 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 MVEL needs full integration for all code expressions and blocks. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-662) Make the TMS optional

by Mark Proctor (JIRA)

Make the TMS optional --------------------- Key: JBRULES-662 URL: http://jira.jboss.com/jira/browse/JBRULES-662 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Make the TMS optional, but by default on. This should help reduce memory usage on lage systems. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4334) port JBAS-4103 to JBoss 5

by Aleksandar Kostadinov (JIRA)

port JBAS-4103 to JBoss 5 ------------------------- Key: JBAS-4334 URL: http://jira.jboss.com/jira/browse/JBAS-4334 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Aleksandar Kostadinov Assigned To: Jaroslaw Kijanowski Fix For: JBossAS-5.0.0.Beta3 This is duplicate of JBQA-751 I think it's not done for JBoss AS 5. I create it so it can be tracked by JBoss AS team and don't miss the fix version (or waived for future version). -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBRULES-585) syntax sugar for binding to a field on a bound fact

by Michael Neale (JIRA)

syntax sugar for binding to a field on a bound fact --------------------------------------------------- Key: JBRULES-585 URL: http://jira.jboss.com/jira/browse/JBRULES-585 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Mark Proctor Fix For: 3.1-m3 For example: c: Customer($id: id) p: Person(customerId == $id.....) could become: c: Customer() p: Person(customerId == c.id) much more OO looking. Can use an extractor (if possible). -- 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, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-456) Nested field accessor - contributions from Patrick Niemeyer

by Michael Neale (JIRA)

Nested field accessor - contributions from Patrick Niemeyer ----------------------------------------------------------- Key: JBRULES-456 URL: http://jira.jboss.com/jira/browse/JBRULES-456 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Mark Proctor Priority: Critical Fix For: 3.1-m3 Attachments: jboss-nested-asm.jar This is from Patrick Niemeyer <pat(a)pat.net>. Provides Foo(a.b.c etc). We are hoping for some more enhancements that can also do map/array access like javascript. -- 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, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (HIBERNATE-59) @OneToMany collection is not filled when it should when the PK is of uniqueidentifier

by Tobias Bergman (JIRA)

@OneToMany collection is not filled when it should when the PK is of uniqueidentifier ------------------------------------------------------------------------------------- Key: HIBERNATE-59 URL: http://jira.jboss.com/jira/browse/HIBERNATE-59 Project: Hibernate Issue Type: Bug Environment: Windows XP SP2 JBoss 4.2 CR1 SQL Server 2000 Reporter: Tobias Bergman Assigned To: Steve Ebersole I have found a problem when using uniqueidentifier as PK and FK. A collection which should have entires are empty. The same code will have a non-empty collections when tested on glassfish. Source code is supplied in the forum post. -- 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, 1 month

1
1
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 April 2007