[JBoss JIRA] Created: (JBAS-3919) CLONE -JMS PersistenceManager: Could not resolve uncommited transactions using MS SQL Server
by Aladdin El-Nattar (JIRA)
CLONE -JMS PersistenceManager: Could not resolve uncommited transactions using MS SQL Server
--------------------------------------------------------------------------------------------
Key: JBAS-3919
URL: http://jira.jboss.com/jira/browse/JBAS-3919
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Reporter: Aladdin El-Nattar
Assigned To: Luc Texier
Fix For: JBossAS-4.0.4.CR2
using mssql-jdbc2-service.xml from /examples/jms this warn is logged during a restart
2006-02-23 16:14:40,528 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager
org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Line 1: Incorrect syntax near ')'.)
at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:442)
--
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, 9 months
[JBoss JIRA] Created: (EJBTHREE-801) No way to provide external configuration for @Service beans
by james ahlborn (JIRA)
No way to provide external configuration for @Service beans
-----------------------------------------------------------
Key: EJBTHREE-801
URL: http://jira.jboss.com/jira/browse/EJBTHREE-801
Project: EJB 3.0
Issue Type: Feature Request
Components: EJB3 Extensions
Affects Versions: EJB 3.0 RC9 - FD
Reporter: james ahlborn
The @Service bean is a great extension. However, it does not seem to provide any functionality for external configuration. Jboss mbeans can be configured in service.xml files using attribute elements. EJB3 stateless session beans can be configured using env-entry elements in the ejb-jar.xml. The @Service bean is a hybrid of these two components, but has no facility for external configuration. The jboss.xml file has elements for service bean instantiation, but provides no env-entry nor attribute style elements for configuring said bean.
I've attempted to use a stateless entry in the ejb-jar.xml referencing the @Service bean with env-entry elements. This does not cause any errors on deployment, but it also does not do anything.
--
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, 9 months
[JBoss JIRA] Commented: (JBRULES-339) 'from' support for reasoning over facts not in the working memory
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-339?page=comments#action_12348118 ]
Edson Tirelli commented on JBRULES-339:
---------------------------------------
$ svn log -r 8048 -v
------------------------------------------------------------------------
r8048 | tirelli | 2006-12-04 10:44:51 -0300 (Mon, 04 Dec 2006) | 1 line
Changed paths:
M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLLexer.java
M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLParser.java
M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/descr/AccessorDescr.java
M /labs/jbossrules/trunk/drools-compiler/src/main/resources/org/drools/lang/DRL.g
M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/RuleParserTest.java
A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/lang/test_ComplexChainedCallWithFrom.drl
JBRULES-339: adding support to chaining the result of a function call
------------------------------------------------------------------------
> 'from' support for reasoning over facts not in the working memory
> -----------------------------------------------------------------
>
> Key: JBRULES-339
> URL: http://jira.jboss.com/jira/browse/JBRULES-339
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Mark Proctor
> Assigned To: Mark Proctor
> Fix For: 3.1-m1
>
>
> It should be possible to bind and then reason over facts not in the working memory for the current rule. Its important to remember that the derived facts should be time constant.
--
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, 9 months
[JBoss JIRA] Updated: (JBAS-2844) JMS PersistenceManager: Could not resolve uncommited transactions using MS SQL Server
by Adrian Brock (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2844?page=all ]
Adrian Brock updated JBAS-2844:
-------------------------------
Comment: was deleted
> JMS PersistenceManager: Could not resolve uncommited transactions using MS SQL Server
> -------------------------------------------------------------------------------------
>
> Key: JBAS-2844
> URL: http://jira.jboss.com/jira/browse/JBAS-2844
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMS service
> Reporter: Luc Texier
> Assigned To: Luc Texier
> Fix For: JBossAS-4.0.4.CR2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> using mssql-jdbc2-service.xml from /examples/jms this warn is logged during a restart
> 2006-02-23 16:14:40,528 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager
> org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Line 1: Incorrect syntax near ')'.)
> at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:442)
--
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, 9 months
[JBoss JIRA] Created: (JBMESSAGING-667) Clustered ConnectionFactory binding mechanism broken for a single-node cluster (and possibly for multi-node cluster)
by Ovidiu Feodorov (JIRA)
Clustered ConnectionFactory binding mechanism broken for a single-node cluster (and possibly for multi-node cluster)
--------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-667
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-667
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.2.0.Beta1
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta1
The current code that binds clustered ConnectionFactories in JNDI couldn't possibly run. Reasons:
* ConnectionFactoryJNDIMapper creates a "local" ClientConnectionFactoryDelegate, and then replicates it around the cluster. Because ConnectionFactoryJNDIMapper is a listener to its own replicant instance, it gets its own replication request and tries to add the ClientConnectionFactoryDelegate to a ClusteredConnectionFactoryDelegate that is not yet bound in the "factories" map. Hence, IllegalStateException("Cannot find connection factory " + uniqueName + " to update").
* Mixup between ClientConnectionFactoryDelegates and JBossConnectionFactories while adding to internal "factories" map.
* ConnectionFactoryJNDIMapper.setFailoverDelegates() indexes are messed up (the i index used instead of j in for (int j = 0; j < s; j++))
* etc.
Before commenting on the above assertions, try running the simplest JMSTest in clustered mode.
--
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, 9 months
[JBoss JIRA] Commented: (JBMICROCONT-71) JMX Decorator for POJOs
by David Ward (JIRA)
[ http://jira.jboss.com/jira/browse/JBMICROCONT-71?page=comments#action_123... ]
David Ward commented on JBMICROCONT-71:
---------------------------------------
I took a look at the forum reference, which had an example like this:
<bean name="Bean1" ...>
<annotation name="org.jboss.jndi.Binding">
<attribute name="JndiName">whatever</attribute>
</annotation/>
</bean>
And I was thinkin'... Wouldn't decorating Microcontainer POJOs as MBeans, or making them available in JNDI be such a desirable, common thing for people to want to do, that the above syntax should be made easier? Maybe a shorthand, like this:
<bean
name="Bean1"
jmx-name="jboss.foobar:service=Bean1"
jndi-name="java:/foobar/Bean1"
class="com.foobar.Bean1" />
Thanks!
David
> JMX Decorator for POJOs
> -----------------------
>
> Key: JBMICROCONT-71
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-71
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: General
> Reporter: Adrian Brock
> Assigned To: Adrian Brock
> Fix For: JBossMC_2_0_0_CR1
>
>
> Complete the prototype JMX Decorator for POJOs
> This needs to include links into JSR77 not just JMX
--
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, 9 months