Paging problem with stopping the server right after Batch ACKs are called.
--------------------------------------------------------------------------
Key: JBMESSAGING-1450
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1450
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assignee: Clebert Suconic
Fix For: 2.0.0 Beta
Attachments: diff.patch
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Upgrade to jboss-server-manager 0.1.2.GA and jboss-test 1.1.2.GA
----------------------------------------------------------------
Key: JBAS-6141
URL: https://jira.jboss.org/jira/browse/JBAS-6141
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
Assignee: Shelly McGowan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
SecurityContextAssociation needs to have permission checks
----------------------------------------------------------
Key: SECURITY-323
URL: https://jira.jboss.org/jira/browse/SECURITY-323
Project: JBoss Security and Identity Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security SPI
Affects Versions: 2.0.2.GA
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Fix For: 2.0.2.SP1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Problem with DSL if there is no RHS
-----------------------------------
Key: JBRULES-1839
URL: https://jira.jboss.org/jira/browse/JBRULES-1839
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.0.0.M2
Reporter: Toni Rikkola
Assignee: Edson Tirelli
DSL doesn't work if there is no RHS. It connects the "then" and "end" to "thenend".
There is a unit test for this: DSLMappingFileTest.FIXMEtestNoRHS()
For example:
rule "DateDslRule"
dialect "mvel"
when
When the applicant dates is after 20-Oct-2008
then
end
=====>
rule "DateDslRule"
dialect "mvel"
when
applicant:Applicant(applicationDate>"20-Oct-2008")
thenend
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Simplify JavaEE Authorization Helper methods
--------------------------------------------
Key: SECURITY-320
URL: https://jira.jboss.org/jira/browse/SECURITY-320
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX, Security SPI
Affects Versions: 2.0.2.GA
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Fix For: 2.0.2.SP1
Must have been something bad. Need to simplify the api such that the method parameters are not too many.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JGroups appears to ignore the multicast address when more than one jgoup application is running on the same machine.
--------------------------------------------------------------------------------------------------------------------
Key: JGRP-862
URL: https://jira.jboss.org/jira/browse/JGRP-862
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.6
Environment: Linxu AS4, Jgroups-2.6.6 , Java version "1.5.0_10"
Reporter: Brendan Doherty
Assignee: Bela Ban
Using the multicast send/receiver test application, all on the same physical machine with the following parameters -Djava.net.preferIPv4Stack=true -mcast_addr <AS BELOW> -bind_addr <LAN IP address>
Create one sender on 239.197.0.1
Create one receiver on 239.198.0.1
Create a second receiver on 239.199.0.1
Send a message, as expected neither of the receivers observe the message.
Create a third receiver on 239.197.0.1
Send a message, all three senders now receive the message
Is this the expected behaviour?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
jboss.entity.manager.factory.jndi.name doesn't work in JBoss 5.0.0.CR2
----------------------------------------------------------------------
Key: EJBTHREE-1526
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1526
Project: EJB 3.0
Issue Type: Bug
Reporter: Pete Muir
Assignee: Carlo de Wolf
Exposing the EMF in JNDI was disabled for some reason.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Exposing the EMF in JNDI via jboss.entity.manager.factory.jndi.name doesn't work in JBoss 5.0.0.CR2
---------------------------------------------------------------------------------------------------
Key: JBAS-6093
URL: https://jira.jboss.org/jira/browse/JBAS-6093
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Pete Muir
Priority: Critical
Fix For: JBossAS-5.0.0.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create an abstract test case which checks whether a deployment succeeded
------------------------------------------------------------------------
Key: EJBTHREE-1557
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1557
Project: EJB 3.0
Issue Type: Task
Components: testsuite
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: 1.0.0-Beta6
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
The wrong ejbCreate is called when constructing a 2.1 bean via the local home
-----------------------------------------------------------------------------
Key: EJBTHREE-1585
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1585
Project: EJB 3.0
Issue Type: Bug
Affects Versions: 1.0.0-Beta6
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 1.0.0-Beta7
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira